[7.17] fix: missing fields in range aggregation response for date fields (#82732) #82757
Conversation
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
…astic#82732) When running a range aggregation on a date field both `fromAsStr` and `toAsStr` need to be parsed to extract the correct range boundaries. Not doing so results in +/- infinite values in `to`, `from`, `originalTo` and `originalFrom` which in turn result in: * incorrect key values (wildcard character used for infinite values); * missing fields in the response (to, from, to_as_string, from_as_string) due to checks for initite values in the serialization logic; (cherry picked from commit 1186e90) # Conflicts: # rest-api-spec/src/yamlRestTest/resources/rest-api-spec/test/search.aggregation/40_range.yml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Backport
This is an automatic backport to
7.17of:This is a fix for #82688