-
Notifications
You must be signed in to change notification settings - Fork 1.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
[CI/CD] Test failure in GeoHashGridIT#testMultivaluedGeoPointsAggregation #7101
Comments
/cc @navneet1v |
@nknize will look into this. This is really interesting to see GeoPoints Aggregation Tests getting failed. Will see if there were some changes in the tests that lead to this failure. because these tests are written when OS got forked from ES. |
@nknize I found out the issue and will be raising the PR soon. The issue was happening mainly because of the way we encode the GeoPoint and error that comes in the precision due to that encoding. The error was happening for a tile: 13/1627/7465 The idea to fix this is simple enough, while generating the expected buckets for geo-points I will encode and decode the lat-lon values. This will make sure that the precision loss comes in during the Tile creation, as showed in the below snippet. I just have 1 question, should I do this for GeoHex also? I think I should, but need your input here. Code ref: Lines 160 to 166 in 9386cde
|
On doing some more deep-dive what I can see is this encoding of geo points to long values is already happening as part of creating Geohash for a geo-point. Hence the issue will not happen for Geohash buckets and not required for GeoHashAggregationIT. Code reference:
OpenSearch/libs/geo/src/main/java/org/opensearch/geometry/utils/Geohash.java Lines 376 to 381 in 8394f54
OpenSearch/libs/geo/src/main/java/org/opensearch/geometry/utils/Geohash.java Lines 384 to 389 in 8394f54
Encoding of geo-points in lucene just before storing the points: |
…tsAggregation test case. The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
…tsAggregation test case. The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
…tsAggregation test case. The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
…tsAggregation test case. The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
… case. (#7166) The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
PR is merged. Resolving the issue. |
…tsAggregation test case. (opensearch-project#7166) The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
…tsAggregation test case. (opensearch-project#7166) The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
…tsAggregation test case. (opensearch-project#7166) The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]>
* Add GeoTile and GeoHash Grid aggregations on GeoShapes. (#5589) Src files for GeoTile and GeoHash Aggregations on GeoShape with integration tests. Signed-off-by: Navneet Verma <[email protected]> * [opensearch-project/geospatial#212] Fixing the IT for GeoTilesAggrega… (#6120) Fixing the IT for GeoTilesAggregation. Signed-off-by: Navneet Verma <[email protected]> * [#6187, #6222] Fixing the GeoShapes GeoHash and GeoTile Aggregations Integration tests. (#6242) Changes done: * Fixed the ArrayIndexOutOfBoundsException. * Reduced the precision for GeoShapes Aggregation IT testing. Signed-off-by: Navneet Verma <[email protected]> * [#7101] Fixing the GeoTileIT#testMultivaluedGeoPointsAggregation test case. (#7166) The issue was happening because we encode the GeoPoint as long and error comes in the precision due to that encoding. The error was not taken care while generating the exepected tiles count for execpected output. Signed-off-by: Navneet Verma <[email protected]> --------- Signed-off-by: Navneet Verma <[email protected]> Signed-off-by: Heemin Kim <[email protected]> Co-authored-by: Navneet Verma <[email protected]>
Describe the bug
Caught on PR #7094
GeoHashGridIT#testMultivaluedGeoPointsAggregation
reproducibly fails.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Passing test
The text was updated successfully, but these errors were encountered: