-
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
Aggregator result equality easy to break #111757
Labels
:Analytics/Aggregations
Aggregations
>enhancement
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Comments
nik9000
added
>enhancement
:Analytics/Aggregations
Aggregations
needs:triage
Requires assignment of a team area label
labels
Aug 9, 2024
elasticsearchmachine
added
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
and removed
needs:triage
Requires assignment of a team area label
labels
Aug 9, 2024
Pinging @elastic/es-analytical-engine (Team:Analytics) |
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
Aug 9, 2024
This reverts elastic#110261 which we can't land until elastic#111757 - we need to be sure that the `equals` implementations on subclasses of `InternalAggregations` is correct before this optimization is safe.
This was referenced Aug 9, 2024
elasticsearchmachine
pushed a commit
that referenced
this issue
Aug 9, 2024
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
Aug 9, 2024
This reverts elastic#110261 which we can't land until elastic#111757 - we need to be sure that the `equals` implementations on subclasses of `InternalAggregations` is correct before this optimization is safe. Closes elastic#111679
elasticsearchmachine
pushed a commit
that referenced
this issue
Aug 9, 2024
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Sep 4, 2024
This reverts elastic#110261 which we can't land until elastic#111757 - we need to be sure that the `equals` implementations on subclasses of `InternalAggregations` is correct before this optimization is safe. Closes elastic#111679
davidkyle
pushed a commit
to davidkyle/elasticsearch
that referenced
this issue
Sep 5, 2024
This reverts elastic#110261 which we can't land until elastic#111757 - we need to be sure that the `equals` implementations on subclasses of `InternalAggregations` is correct before this optimization is safe. Closes elastic#111679
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/Aggregations
Aggregations
>enhancement
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
Description
We'd like to make some optimizations that are gated behind the
equals
method on subclasses ofInternalAggregation
working perfectly. But at the moment it's quite easy implementequals
incorrectly - our default equals implementation checks a few things but doesn't force subclasses to override it with their extra data. Many do, but not all. We should make not overridingequals
here a compile time failure. Generally we do this by adding anabstract boolean doEquals
method and calling it inequals
. That's a bit tricky here because of all the layers of subclasses, but we can do it.The text was updated successfully, but these errors were encountered: