-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[Transform] geo_bounds aggregation failed with NPE error #71874
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
Labels
Comments
Pinging @elastic/es-analytics-geo (Team:Analytics) |
Pinging @elastic/ml-core (Team:ML) |
I debugged this, it fails in the indexing step Repro:
fails for fields of type "geo_shape" |
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Apr 21, 2021
… adding debug logging of index requests send by transform relates elastic#71874
romseygeek
added a commit
to romseygeek/elasticsearch
that referenced
this issue
Apr 21, 2021
elastic#71696 introduced a regression to the various shape field mappers, where they would no longer handle null values. This commit fixes that regression and adds a testNullValues method to MapperTestCase to ensure that all field mappers correctly handle nulls. Fixes elastic#71874
elasticmachine
added a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Apr 22, 2021
hendrikmuhs
pushed a commit
that referenced
this issue
Apr 22, 2021
use sparse data for geobounds agg, verifies the fix of #71874, adding debug logging of index requests send by transform
hendrikmuhs
pushed a commit
that referenced
this issue
Apr 22, 2021
use sparse data for geobounds agg, verifies the fix of #71874, adding debug logging of index requests send by transform
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
After #71696 was merged, one of our
transform:geo_bounds
test failed with this error: Cannot invoke "org.elasticsearch.geometry.Geometry.visit(org.elasticsearch.geometry.GeometryVisitor)" because "geometry" is null]The better error handling is expected because the real failure was caused by non-existent
geo.location
field.Build:
Latest 8.0.0 and 7.13.0 build on Apr 19
8.0.0 build hash:
Step to reproduce in dev console
Error:
Expected:
Better error handling about the non-existent field:
geo.location
.The text was updated successfully, but these errors were encountered: