Give significance lookups their own home#57903
Merged
nik9000 merged 3 commits intoelastic:masterfrom Jun 10, 2020
Merged
Conversation
This moves the code to look up significance heuristics information like background frequency and superset size out of `SignificantTermsAggregatorFactory` and into its own home so that it is easier to pass around. This will: 1. Make us feel better about ourselves for not passing around the factory, which is really *supposed* to be a throw away thing. 2. Abstract the significance lookup logic so we can reuse it for the `significant_text` aggregation. 3. Make if very simple to cache the background frequencies which should speed up when the agg is a sub-agg. We had done this for numerics but not string-shaped significant terms.
Collaborator
|
Pinging @elastic/es-analytics-geo (:Analytics/Aggregations) |
16 tasks
Member
Author
Member
Author
not-napoleon
approved these changes
Jun 10, 2020
| } | ||
|
|
||
| /** | ||
| * Get the background frequency of a {@link BytesRef} term. |
Member
There was a problem hiding this comment.
Is this javadoc correct? Looks like it's operating on a long term below.
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this pull request
Jun 10, 2020
This moves the code to look up significance heuristics information like background frequency and superset size out of `SignificantTermsAggregatorFactory` and into its own home so that it is easier to pass around. This will: 1. Make us feel better about ourselves for not passing around the factory, which is really *supposed* to be a throw away thing. 2. Abstract the significance lookup logic so we can reuse it for the `significant_text` aggregation. 3. Make if very simple to cache the background frequencies which should speed up when the agg is a sub-agg. We had done this for numerics but not string-shaped significant terms.
nik9000
added a commit
that referenced
this pull request
Jun 12, 2020
This moves the code to look up significance heuristics information like background frequency and superset size out of `SignificantTermsAggregatorFactory` and into its own home so that it is easier to pass around. This will: 1. Make us feel better about ourselves for not passing around the factory, which is really *supposed* to be a throw away thing. 2. Abstract the significance lookup logic so we can reuse it for the `significant_text` aggregation. 3. Make if very simple to cache the background frequencies which should speed up when the agg is a sub-agg. We had done this for numerics but not string-shaped significant terms.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This moves the code to look up significance heuristics information like
background frequency and superset size out of
SignificantTermsAggregatorFactoryand into its own home so that it iseasier to pass around. This will:
factory, which is really supposed to be a throw away thing.
significant_textaggregation.speed up when the agg is a sub-agg. We had done this for numerics
but not string-shaped significant terms.