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
Bugs with encoding multiple levels of geo precision #7369
Conversation
@@ -34,6 +34,12 @@ setup: | |||
"location": | |||
"type" : "geo" | |||
"precision" : "5km" | |||
"suggest_geo_multi_level": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we have a java test for this instead? The REST test are not here to test functionality :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I started down that route but the Java API looked to be missing the "context" part of the suggest API - I can roll a change for that into this PR if you want.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
odd isn't ContextSuggestSearchTests
using the API?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was looking in the wrong place, thanks
1) One issue reported by a user is due to the truncation of the geohash string. Added Junit test for this scenario 2) Another suspect piece of code was the “toAutomaton” method that only merged the first of possibly many precisions into the result. Closes #7368 Added Java test
LGTM |
Committed in c0aef4a |
Closes #7368