-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[CI] InternalGeoBoundsTests.testFromXContentWithRandomFields failure #50505
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
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
>test-failure
Triaged test failures from CI
Comments
Pinging @elastic/es-analytics-geo (:Analytics/Geo) |
andreidan
added a commit
to andreidan/elasticsearch
that referenced
this issue
Dec 27, 2019
A geo box with a top value of Double.NEGATIVE_INFINITY will yield an empty xContent which translates to a null `geoBoundingBox`. This commit marks the field as `Nullable` and guards against null when retrieving the `topLeft` and `bottomRight` fields. Fixes elastic#50505
Another one today: |
andreidan
added a commit
that referenced
this issue
Jan 3, 2020
A geo box with a top value of Double.NEGATIVE_INFINITY will yield an empty xContent which translates to a null `geoBoundingBox`. This commit marks the field as `Nullable` and guards against null when retrieving the `topLeft` and `bottomRight` fields. Fixes #50505
andreidan
added a commit
to andreidan/elasticsearch
that referenced
this issue
Jan 3, 2020
A geo box with a top value of Double.NEGATIVE_INFINITY will yield an empty xContent which translates to a null `geoBoundingBox`. This commit marks the field as `Nullable` and guards against null when retrieving the `topLeft` and `bottomRight` fields. Fixes elastic#50505 (cherry picked from commit 051718f) Signed-off-by: Andrei Dan <[email protected]>
andreidan
added a commit
that referenced
this issue
Jan 3, 2020
A geo box with a top value of Double.NEGATIVE_INFINITY will yield an empty xContent which translates to a null `geoBoundingBox`. This commit marks the field as `Nullable` and guards against null when retrieving the `topLeft` and `bottomRight` fields. Fixes #50505 (cherry picked from commit 051718f) Signed-off-by: Andrei Dan <[email protected]>
SivagurunathanV
pushed a commit
to SivagurunathanV/elasticsearch
that referenced
this issue
Jan 23, 2020
A geo box with a top value of Double.NEGATIVE_INFINITY will yield an empty xContent which translates to a null `geoBoundingBox`. This commit marks the field as `Nullable` and guards against null when retrieving the `topLeft` and `bottomRight` fields. Fixes elastic#50505
This was referenced Feb 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
>test-failure
Triaged test failures from CI
Failure:
Branch master and 7.6.0
Reproduce with
Build scan available at https://gradle-enterprise.elastic.co/s/7x2ct6yywkw3o
This is a regression introduced by #50253
The text was updated successfully, but these errors were encountered: