-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Incorrect result order for autocomplete #1279
Comments
Hey @Joxit, I think this is more caused by Here's the parser output:
It's therefore trying to use /v1/autocomplete?text=160 avenue aristide briand, bagneux I'd rather not go down the re-sorting path for autocomplete, but I do think it's time for revisiting what parsing logic (if any) the autocomplete endpoint uses so that we can fix this case |
In fact, this works well in our production server (result here) which is in v3.53.0.
👍 for the parsing logic 😄 |
Connects pelias/schema#301 Connects pelias/api#1268 Connects pelias/api#1279
This is (finally) fixed as of #1287 and the new Pelias parser!! 🎉 |
I found an inconsistent result for autocomplete (I think it's since 3.58.0).
When I search
160 avenue aristide briand bagneux
, the exact match is on second position instead of the first one.It works well for 3.57.0
Should we re sort results before sending them ?
The text was updated successfully, but these errors were encountered: