Wildcard field - added case insensitive search option #53814
Closed
Conversation
This file contains 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
…multi field with “._case_insensitive” suffix is automatically made available at not extra storage cost which performs case insensitive searches
markharwood
added
>enhancement
:Search Foundations/Mapping
|
Pinging @elastic/es-search (:Search/Mapping) |
|
Some quick benchmarks based on an index where case-sensitive and case-insensitive searches matched equal numbers of docs.
The new case-insensitive search option requires more work to normalize-on-the-fly the binary doc values read from disk. However this is an overhead that might be worth paying as it halves the disk space otherwise required to have case sensitive and insensitive search (something you might want if your logging system captures both Windows and Unix events) |
|
Closing in favour of #53851 |
38 tasks
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.
Generally in elasticsearch, the case sensitivity or not of searches is normally dictated by the choice of field a user searches. In keeping with this practice this change automatically creates a multi-field for wildcard fields so that a wildcard field called
fooalso has afoo._case_insensitivevariant.However, unlike other fields this comes at no extra storage cost. The
.case_insensitivefield type just uses the same data structures as the case sensitive one - it just relaxes the matching logic in the verification phase. The ngram index used for the approximation query is lower-cased and therefore may produce more false positives for case-sensitive searches but these are expected to be low in number (how many docs differ only by case?).