Skip to content

Conversation

@pquentin
Copy link
Member

While it's required most of the time, it's optional when in a sub-aggregation inside a time_series aggregation, as mentioned in the comment.

Sources:

Not backporting to 9.2 as it's a breaking change, but still backporting to 8.19 as it's not that bad for most clients.

Relates #3122

While it's required most of the time, it's optional when in a sub-aggregation
inside a time_series aggregation, as mentioned in the comment.
@github-actions
Copy link
Contributor

Following you can find the validation changes against the target branch for the API.

API Status Request Response
search 🔴 2593/2615 → 2594/2615 2615/2615

You can validate this API yourself by using the make validate target.

@pquentin pquentin requested review from flobernd and l-trotta October 28, 2025 12:34
@pquentin pquentin merged commit c5e3b91 into main Oct 28, 2025
10 checks passed
@pquentin pquentin deleted the geo_line_optional_sort branch October 28, 2025 13:01
github-actions bot pushed a commit that referenced this pull request Oct 28, 2025
While it's required most of the time, it's optional when in a sub-aggregation
inside a time_series aggregation, as mentioned in the comment.

(cherry picked from commit c5e3b91)
pquentin added a commit that referenced this pull request Oct 28, 2025
While it's required most of the time, it's optional when in a sub-aggregation
inside a time_series aggregation, as mentioned in the comment.

(cherry picked from commit c5e3b91)

Co-authored-by: Quentin Pradet <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants