[CI] org.elasticsearch.search.geo.GeoShapeQueryTests. testQueryRandomGeoCollection failure

[iverase]

I noticed some failures in the test above. For example:

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.6+multijob-unix-compatibility/os=fedora/46/console

It can be reproduced without adding the method name:

./gradlew :server:unitTest
-Dtests.seed=506AA3004455CABB
-Dtests.class=org.elasticsearch.search.geo.GeoShapeQueryTests
-Dtests.method="testQueryRandomGeoCollection"
-Dtests.security.manager=true
-Dtests.locale=it
-Dtests.timezone=Asia/Vladivostok
-Dcompiler.java=11
-Druntime.java=8

I had a look into it and I could reproduce the issue at Lucene level.

The problem is that we are generating degenerated polygons in one dimension, for example:

polygon ((1.401298464324817E-45 22.0, 1.401298464324817E-45 69.0, 4.8202184588118395E-40 69.0, 4.8202184588118395E-40 22.0, 1.401298464324817E-45 22.0))

Then when indexing this polygon and perform an intersect query using the same one, they do not match. This is probably due to the encoding Lucene is using.

[elasticmachine]

Pinging @elastic/es-analytics-geo

[iverase]

I have opened https://issues.apache.org/jira/browse/LUCENE-8634

[jkakavas]

I muted the test as it failed again today on
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-unix-compatibility/os=oraclelinux/185/console

[imotov]

@jkakavas did you mute it only in 6.x? I think it should be failing in all branches, I opened #37579 that should ignore the failing part of the test if a tiny polygon is generated,

[imotov]

I unmuted the test and added assumeTrue to ignore tests with random polygons that are causing issues because of LUCENE-8634. The changes are merged into 6.6, 6.x and 7.x.

[nknize]

I've added some feedback on this issue at https://issues.apache.org/jira/browse/LUCENE-8634

tldr; subcentimeter polygons are not supported w/ the encoding we use in the WGS84 projection. Polygons this small should be reserved for an alternate projection (e.g., mercator, UTM). This will eventually be supported with a new XYShape / geometry field type (probably ES 8.0).