Use contains relation for geo_point intersection over geo_point field (#75272)#75321
Merged
iverase merged 1 commit intoelastic:7.xfrom Jul 14, 2021
Merged
Use contains relation for geo_point intersection over geo_point field (#75272)#75321iverase merged 1 commit intoelastic:7.xfrom
iverase merged 1 commit intoelastic:7.xfrom
Conversation
…elastic#75272) Lucene does not match points that are encoded to Integer.MAX_VALUE for intersects.
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
1 participant
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.
For point queries and intersects, lucene does not match points that are encoded to Integer.MAX_VALUE due to the use of predicates. Use contains instead that returns the expected results.
backport #75272