You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Field exists" query does not work properly on fields GeoShape for existing indexes after the upgrade from 2.8.0 version to 2.11.1
I suspect it is related to #10958 somehow
FieldExistsQuery requires that the field indexes doc values, norms or vectors, but field 'my_geometry' exists and indexes neither of these data structures
The expected result is that the filter works properly and only returns the following document :
{
"name" : "Without geometry"
}
If we re-create a fresh new index on this 2.11.1 version following the same steps as before, then the filter works fine.
Additional Details
Host/Environment :
Initially had the issue with :
Index initially created on version 1.3.5
OpenSearch version before upgrade 2.8.0
OpenSearch version after upgrade 2.11.1
=> result: I did not have any error message with this setup, but the responses were wrong, and the filter was not applying (ignored?)
Reproduced locally (dockerized) with :
Index Initially created on version 2.8.0
OpenSearch version before upgrade 2.8.0
OpenSearch version after upgrade 2.11.1
=> result: a 500 error, with the message above
The text was updated successfully, but these errors were encountered:
Describe the bug
"Field exists" query does not work properly on fields GeoShape for existing indexes after the upgrade from 2.8.0 version to 2.11.1
I suspect it is related to #10958 somehow
Related component
Search:Query Capabilities
To Reproduce
geo_shape
fieldUpgrade the OpenSearch server to version 2.11.1
Do the same search as before
Expected behavior
The current result is the following failure :
FieldExistsQuery requires that the field indexes doc values, norms or vectors, but field 'my_geometry' exists and indexes neither of these data structures
The expected result is that the filter works properly and only returns the following document :
If we re-create a fresh new index on this
2.11.1
version following the same steps as before, then the filter works fine.Additional Details
Host/Environment :
Initially had the issue with :
1.3.5
2.8.0
2.11.1
=> result: I did not have any error message with this setup, but the responses were wrong, and the filter was not applying (ignored?)
Reproduced locally (dockerized) with :
2.8.0
2.8.0
2.11.1
=> result: a 500 error, with the message above
The text was updated successfully, but these errors were encountered: