GH-4978 Index geosparql points using geo field #4979
Merged
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
ate47
force-pushed
the
GH-4978-lucene-geo-points
branch
from
b4abff8
to
2082613
Compare
|
I want to mention that this PR is only fixing the Q1 case in #4978. |
|
I've create a duplicate issue so that we don't forget about Q2: #4996 |
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.
GitHub issue resolved: #4978
Briefly describe the changes proposed in this PR:
I added the indexing of the points using the geo prefix and not only the point prefix.
PR Author Checklist (see the contributor guidelines for more details):
mvn process-resourcesto format from the command line)