Skip to content

Conversation

flobernd
Copy link
Member

As titled. Also marks CompositeAggregationSource as a container since the aggregations are mutually exclusive.

This fix as well greatly improves the quality of the generated code for the .NET client (see #8704).

Server code:
https://github.com/elastic/elasticsearch/blob/a59c182f9f7e9d1bf3d6eecbc0e44f24ff91d053/server/src/main/java/org/elasticsearch/search/aggregations/bucket/composite/CompositeValuesSourceParserHelper.java#L78

No backport, since this is a breaking change for statically typed languages.

@flobernd flobernd requested review from pquentin, l-trotta and a team September 24, 2025 11:20
@flobernd flobernd added the skip-backport This pull request should not be backported label Sep 24, 2025
Copy link
Contributor

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

No changes detected.

You can validate these APIs yourself by using the make validate target.

Copy link
Member

@pquentin pquentin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, great catch! In addition to the server code, this is nicely documented and there's a YAML test for that.

LGTM.

@flobernd flobernd merged commit 1f00453 into main Sep 24, 2025
10 checks passed
@flobernd flobernd deleted the fix-composite-sources branch September 24, 2025 12:40
@ianschmaltz
Copy link

Thanks @flobernd and team for the clarification and fix.

We were exactly hitting this bug while migrating from NEST to Elastic.Clients.Elasticsearch (v9.1.7) and really appreciate the fast response. We'll keep testing with the suggested workaround until the next client release includes this fix officially.

Thanks again for the support and transparency!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-backport This pull request should not be backported specification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants