-
Notifications
You must be signed in to change notification settings - Fork 25.3k
More pipeline aggregation cleanup #54298
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.
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
Conversation
This replaces the last bit of validation that pipeline aggregations performed on the data nodes with explicit checks in a few `PipelineAggregationBuilders`. We were *already* catching these validation errors for pipeline aggregations that require that their parent be squentially ordered. This just adds validation for pipelines that require *any* parent like `bucket_selector` and `bucket_sort`.
Pinging @elastic/es-analytics-geo (:Analytics/Aggregations) |
@elasticmachine run elasticsearch-ci/packaging-sample-matrix-unix |
@elasticmachine run elasticsearch-ci/packaging-sample-unix and run elasticsearch-ci/packaging-sample-matrix-unix |
@elasticmachine, test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And there was much rejoicing. 🎉
Thanks @polyfractal! |
This replaces the last bit of validation that pipeline aggregations performed on the data nodes with explicit checks in a few `PipelineAggregationBuilders`. We were *already* catching these validation errors for pipeline aggregations that require that their parent be squentially ordered. This just adds validation for pipelines that require *any* parent like `bucket_selector` and `bucket_sort`.
This replaces the last bit of validation that pipeline aggregations performed on the data nodes with explicit checks in a few `PipelineAggregationBuilders`. We were *already* catching these validation errors for pipeline aggregations that require that their parent be squentially ordered. This just adds validation for pipelines that require *any* parent like `bucket_selector` and `bucket_sort`.
We can run these tests again 7.8.0 now that it has the fix.
This replaces the last bit of validation that pipeline aggregations
performed on the data nodes with explicit checks in a few
PipelineAggregationBuilders
. We were already catching thesevalidation errors for pipeline aggregations that require that their
parent be sequentially ordered. This just adds validation for pipelines
that require any parent like
bucket_selector
andbucket_sort
.