Skip to content

GeoBoundsAggregate.bounds should be optional #383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
swallez opened this issue Aug 22, 2022 · 0 comments · Fixed by #384
Closed

GeoBoundsAggregate.bounds should be optional #383

swallez opened this issue Aug 22, 2022 · 0 comments · Fixed by #384
Labels
Area: Specification Related to the API spec used to generate client code

Comments

@swallez
Copy link
Member

swallez commented Aug 22, 2022 •
edited
Loading

Found in https://discuss.elastic.co/t/new-java-client-bug-in-geocentroidaggregation/312612

When no documents match the query, an empty object is returned by the geo-bounds aggregation. This means that its single field, bounds, should be optional.
@swallez swallez added the Area: Specification Related to the API spec used to generate client code label Aug 22, 2022
@swallez swallez changed the title GeoBoundsAggregate.bound should be optional GeoBoundsAggregate.bounds should be optional Aug 22, 2022
This was referenced Aug 23, 2022
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Specification Related to the API spec used to generate client code
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update to latest API spec, update ES test server to use SSL elastic/elasticsearch-java
1 participant
@swallez