[ESRTEST-31237] Add 'sort' parameter to TopHits aggregation - #78
Open
sergio-bobillier wants to merge 1 commit into
Conversation
The parameter allows the user to determine the order the documents are put into to determine what documents are the "top hits". By default, they are ordered by the score of the main query, however, that is not always what one might want. This parameter allows possibilities like sorting the top hits in chronological order or by price in ascending order, etc. These are things that cannot be reflected by the score of the main query even if it includes a "corresponding" sort clause.
sergio-bobillier
force-pushed
the
sb-ESRTEST-31237-add-sort-parameter-to-top-hits-agrregation
branch
from
August 31, 2026 09:01
f117aae to
a1b1208
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The parameter allows the user to determine the order the documents are put into to determine what documents are the "top hits". By default, they are ordered by the score of the main query, however, that is not always what one might want.
This parameter allows possibilities like sorting the top hits in chronological order or by price in ascending order, etc. These are things that cannot be reflected by the score of the main query even if it includes a "corresponding"
sortclause.