-
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
missing value not considered in min/max aggregations #48905
Comments
Pinging @elastic/es-analytics-geo (:Analytics/Aggregations) |
Which version of elasticsearch did you test it on. I just tried it on 7.4.2 and I am getting:
What am I missing? (some pun intended) |
You are right, it is fixed on |
@imotov Actually no, issue still exists in
I actually have the above in code using |
Could you share this ESIntegTestCase? I cannot reproduce it with rest commands. |
@mattweber Thanks! I was able to reproduce it using your test and @polyfractal suggested the fix. It turned out the reproduction depends on distribution of documents in segments. That's why I wasn't able to reproduce it in kibana. I am going to open a PR soon. |
Great! Thanks for working on it! |
Fixes the issue when the missing values can be ignored in min/max due to BKD optimization. Fixes elastic#48905
Fixes the issue when the missing values can be ignored in min/max due to BKD optimization. Fixes #48905
Fixes the issue when the missing values can be ignored in min/max due to BKD optimization. Fixes #48905
Fixes the issue when the missing values can be ignored in min/max due to BKD optimization. Fixes #48905
The missing value is not considered in min/max aggreagtions in es7 as they were in previous versions and I don't see this documented as a breaking change. I believe this is due optimization of using segment min/max values.
To reproduce run the following against es6 and es7. The missing values should be returned as the min and max value of the aggregation.
The text was updated successfully, but these errors were encountered: