Skip to content
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

Make parent and child aggregator more obvious #57490

Merged
merged 3 commits into from
Jun 2, 2020

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Jun 1, 2020

Pulls the way that the ParentJoinAggregator collects global ordinals
into a strategy object so it is a little simpler to reason about and
it'll be simpler to save memory by removing asMultiBucketAggregator in
the future.

Relates to #56487

Pulls the way that the `ParentJoinAggregator` collects global ordinals
into a strategy object so it is a little simpler to reason about and
it'll be simpler to save memory by removing `asMultiBucketAggregator` in
the future.

Relates to elastic#56487
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (:Analytics/Aggregations)

@elasticmachine elasticmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Jun 1, 2020
Copy link
Contributor

@talevy talevy left a comment

Choose a reason for hiding this comment

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

super minor copy-paste nit in a doc, but otherwise. I like the clearer cleanup!

*/
protected class DenseCollectionStrategy implements CollectionStrategy {
/**
* Otherwise we use a dense bit array to record the global ordinals.
Copy link
Contributor

Choose a reason for hiding this comment

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

needs updating?

@nik9000 nik9000 merged commit 9479ec1 into elastic:master Jun 2, 2020
nik9000 added a commit to nik9000/elasticsearch that referenced this pull request Jun 2, 2020
Pulls the way that the `ParentJoinAggregator` collects global ordinals
into a strategy object so it is a little simpler to reason about and
it'll be simpler to save memory by removing `asMultiBucketAggregator` in
the future.

Relates to elastic#56487
nik9000 added a commit that referenced this pull request Jun 2, 2020
Pulls the way that the `ParentJoinAggregator` collects global ordinals
into a strategy object so it is a little simpler to reason about and
it'll be simpler to save memory by removing `asMultiBucketAggregator` in
the future.

Relates to #56487
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Aggregations Aggregations >non-issue Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v7.9.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants