-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Remove some deprecation warnings parsing aggs #53026
Conversation
With elastic#50871 aggrgations should now be parsed directly by an `ObjectParser` or `ConstructingObjectParser` without the need for the ceremonial `parse` method. This removes 10 of those `parse` methods and parses the aggregation directly from their `ObjectParser`.
Pinging @elastic/es-analytics-geo (:Analytics/Aggregations) |
@elasticmachine run elasticsearch-ci/1 (Unrelated failure tracked by #52490) |
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.
Nice cleanup!
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.
LGTM. I love a net negative lines PR. Also, I think this resolves #49801 which I see I did a terrible job of naming.
Nice! |
) With elastic#50871 aggrgations should now be parsed directly by an `ObjectParser` or `ConstructingObjectParser` without the need for the ceremonial `parse` method. This removes 10 of those `parse` methods and parses the aggregation directly from their `ObjectParser`.
With #50871 aggrgations should now be parsed directly by an
ObjectParser
orConstructingObjectParser
without the need for theceremonial
parse
method. This removes 10 of thoseparse
methods andparses the aggregation directly from their
ObjectParser
.Closes #49801.