Faster terms aggregation and field names retrieval #43
Conversation
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
If the exact counts aren't important, we can use a random sample to get a decent estimate of fields and their usage but significantly faster. The default leaves the behaviour as before (no sampling).
Tests field ranking over a larger number of random records.
Avoids having to constantly rebuild containers when developing and running tests repeatedly.
Useful for very quickly retrieving a basic list of all fields from the latest index. Returns field type information, but type counts are all set to 1.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added options to iter_terms for random sampling, which can be used when the exact counts aren't important. By default the sampling is off and everything works as before.
Also adds a manager method to get a list of field names and types from the mapping, which should be significantly faster than using
get_parsed_fieldsorget_data_fieldsif counts and rankings don't matter at all.