Feature/allow numeric field exact searches to use docvalues #99801
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
In UnsignedLongFieldMapper we allow the use of docValues in order to improve performances in the case where the query is combined with more restrictive filters
…arches-to-use-docvalues
…arches-to-use-docvalues
…arches-to-use-docvalues
…arches-to-use-docvalues
…arches-to-use-docvalues
…arches-to-use-docvalues
piergm
added
>enhancement
:Search/Search
|
Hi @piergm, I've created a changelog YAML for you. |
javanna
added
:Search Foundations/Mapping
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.
BKD-tree-backed field types (NumberFieldMapper and UnsignedLongFieldMapper) use index structures optimised for range querying therefore don't execute exact match queries very efficiently.
This can lead to slow queries on the id field since using a numeric field for IDs is a common anti-pattern in elasticsearch, as ids created by other databases are often numeric in form.
We want to allow numeric fields to use IndexOrDocValuesQuery in order to improve performance in the case where a numeric id field is combined with more restrictive filters.