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
Fix bug when creating empty geo_lines #97509
Conversation
Hi @iverase, I've created a changelog YAML for you. |
Pinging @elastic/es-analytics-geo (Team:Analytics) |
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.
Fascinating! I did not consider this edge case! An alternative implementation would be to change InternalGeoLine.reduce
to not make the decision on non-overlapping based on it's own state, but on the state of all geo-lines being merged. We should only merge as non-overlapping if all geo-lines are non-overlapping. That would be a change to a single method.
This reverts commit 530e121.
17d631b
to
eac9de2
Compare
I am fine with your proposed fix and thanks for the test. |
💚 Backport successful
|
During reduce, only merge as non-overlapping if all geo-lines are non-overlapping. --------- Co-authored-by: Craig Taverner <craig@amanzi.com>
During reduce, only merge as non-overlapping if all geo-lines are non-overlapping. --------- Co-authored-by: Craig Taverner <craig@amanzi.com>
We are currently creating empty geo_line with the flag non_overlapping equal to true which is causing issues when the driving geo_line for merging is this empty object. This PR make sure that empty geo_lines are created with the right flag.
fixes #97311