Rewritten integer sorts need to use SortedNumericSortField#139538
Merged
romseygeek merged 2 commits intoelastic:mainfrom Dec 16, 2025
Merged
Rewritten integer sorts need to use SortedNumericSortField#139538romseygeek merged 2 commits intoelastic:mainfrom
romseygeek merged 2 commits intoelastic:mainfrom
Conversation
Sorts against integer fields in pre-8.19 indexes are rewritten to use LongComparators to stay consistent with pre-written index metadata. These also need to always expect multi-valued fields. elastic#139293 incorrectly built single-valued sorts in certain circumstances, which would then throw runtime errors.
romseygeek
added
>non-issue
:Search/Search
Collaborator
|
Pinging @elastic/es-search (Team:Search) |
This was referenced Dec 15, 2025
benwtrent
approved these changes
Dec 15, 2025
romseygeek
added a commit
to romseygeek/elasticsearch
that referenced
this pull request
Dec 16, 2025
romseygeek
added a commit
that referenced
this pull request
Dec 16, 2025
romseygeek
added a commit
to romseygeek/elasticsearch
that referenced
this pull request
Dec 17, 2025
…39538) Sorts against integer fields in pre-8.19 indexes are rewritten to use LongComparators to stay consistent with pre-written index metadata. These also need to always expect multi-valued fields. elastic#139293 incorrectly built single-valued sorts in certain circumstances, which would then throw runtime errors.
romseygeek
added a commit
to romseygeek/elasticsearch
that referenced
this pull request
Dec 17, 2025
…39538) Sorts against integer fields in pre-8.19 indexes are rewritten to use LongComparators to stay consistent with pre-written index metadata. These also need to always expect multi-valued fields. elastic#139293 incorrectly built single-valued sorts in certain circumstances, which would then throw runtime errors.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Dec 17, 2025
…139700) Sorts against integer fields in pre-8.19 indexes are rewritten to use LongComparators to stay consistent with pre-written index metadata. These also need to always expect multi-valued fields. #139293 incorrectly built single-valued sorts in certain circumstances, which would then throw runtime errors.
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Jan 7, 2026
* upstream/main: Add hook for blocking termination (elastic#133555) Delegate to ES93ScalarQuantizedVectorsFormat rather than copying behaviour (elastic#139834) Refactor compound block types (elastic#140219) Flush the rate buffer when the slice index changes (elastic#138856) Log linked project connection errors at debug during shutdown (elastic#140239) Periodic FIPS 140-3 buildkite pipelines (elastic#139909) ES|QL - Remove TERM function (elastic#139953) Fix name of started time field in shutdown status (elastic#139910) Drop `project_routing` from query params (elastic#140272) Fix flaky test: AllocationDecidersTests (elastic#140271) Add List Reindex API (elastic#140184) Expose _tier metadata attribute in ESQL (elastic#139894) Tweak TSDBRestEsqlIT#testTimeSeriesQuerying(...) (elastic#140210) Fix an OOM error when creating to many chained synonym graph token filter. (elastic#140026) Suppress Azure SDK error logs (elastic#139730) Rewritten integer sorts need to use SortedNumericSortField (elastic#139538) (elastic#139700) Adjust index versions for skippers for time series (elastic#139670) Fix host.name skippers index version range (elastic#139636) Remove BWC shim for a broken commit Fix index.mapping.use_doc_values_skipper defaults in serverless (elastic#139532)
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
3 participants
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.
Sorts against integer fields in pre-8.19 indexes are rewritten to use
LongComparators to stay consistent with pre-written index metadata.
These also need to always expect multi-valued fields. #139293
incorrectly built single-valued sorts in certain circumstances, which
would then throw runtime errors.