You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think sorting on avg score doesn't make much sense and I wonder where the example in the readme is coming for. I think sort[_score]=desc should work though, so perhaps we should just update the readme for that?
In the case described in the design above, we search over positions based on the person's firstname and/or lastname, and then we group these positions in the frontend based on the person's id linked to it. a person can have multiple position.
Since we group them in a map of person=>positions in the frontend, we lose the sorting and thus, if we had the score, it would be much easier to sort them back in the frontend.
Let me know if it's unclear. A possible workaround would be to index the person, search on the persons, then search again on the position, and somehow merge both in the grouping i mentioned before. but this seem a bit more work for the frontend & more data to index / keep in sync
it would be very handy to have information about the search results from elastic in the response (e.g in the meta object or something like this).
In this example, we would need the
max_score
to show it as the first row, then order the other hits by the_score
(desc):also, I've tried to sort data based on the score (
sort[:avg:score]=desc
) and that doesn't seem to work.The text was updated successfully, but these errors were encountered: