-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Replace AggregatorParsers with namedObject #22397
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
|
@imotov or @martijnvg or @javanna, could one of you have a look at this? Another |
s1monw
left a comment
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.
left one comment LGTM otherwise
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.
can we maybe simplify this and just make PipelineAggregationBuilder a subclass of AggregationBuilder and remote that interface? that would be awesome
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.
Hmmm. I didn't look at that. I'll have a look! I'd love to not need the interface.
Removes `AggregatorParsers`, replacing all of its functionality with `XContentParser#namedObject`. This is the third bit of payoff from elastic#22003, one less thing to pass around the entire application.
|
@s1monw I had a look at making |
2b606c2 to
6c0f4c5
Compare
Removes `AggregatorParsers`, replacing all of its functionality with `XContentParser#namedObject`. This is the third bit of payoff from #22003, one less thing to pass around the entire application.
Removes
AggregatorParsers, replacing all of its functionality withXContentParser#namedObject.This is the third bit of payoff from #22003, one less thing to pass
around the entire application.