Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GH-4978 Index geosparql points using geo field #4979

Merged
merged 1 commit into from
May 31, 2024

Conversation

ate47
Copy link
Contributor

@ate47 ate47 commented May 16, 2024

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):

  • my pull request is self-contained
  • I've added tests for the changes I made
  • I've applied code formatting (you can use mvn process-resources to format from the command line)
  • I've squashed my commits where necessary
  • every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

@ate47 ate47 force-pushed the GH-4978-lucene-geo-points branch from b4abff8 to 2082613 Compare May 17, 2024 08:53
@ate47 ate47 marked this pull request as ready for review May 17, 2024 09:16
@ate47
Copy link
Contributor Author

ate47 commented May 17, 2024

I want to mention that this PR is only fixing the Q1 case in #4978.

@hmottestad hmottestad merged commit 192b4ea into eclipse-rdf4j:main May 31, 2024
9 checks passed
@hmottestad
Copy link
Contributor

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Geo sparql issues with Lucene
2 participants