-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
deterministic score tiebreaker #1608
base: master
Are you sure you want to change the base?
Conversation
Huh, fun. Looks like this actually fails because loading the
|
Wow ok, problem with using |
I'd be interested to know which query caused that, I assumed sort was after hits are pruned |
Or at least the second sort criteria was only a secondary sorting based on the top $size hits of the first criteria |
|
reference for
It seems that since So there's a couple options if we'd like to pursue this:
[edit] reversing the fields to have the less common terms first would be preferable! |
My personal preference would be either 3. abandon this and move on /or 2. use |
Yeah, using |
Seems we can probably use only |
Maybe we want to try a different approach then? What if we re-sorted results in the API after retrieving them from Elasticsearch? Sort first by score, then by If sorting by |
Yeah I had a similar thought, the concern there is if the top n 'hits' returned from ES to the API were non-deterministic then it wouldn't really solve the core issue |
Ahh, good point. It would probably handle most cases but definitely not every case. So lets try a build with If it's really bad maybe we do it API-side for now and work on introducing more scoring differentiators into the queries in the future? |
partner PR for pelias/query#130