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
Description of the problem including expected versus actual behavior:
When I include a geo distance query into the should clause of my master bool query and use this query to search for results, it would produce a java.io.IOException: Unknown GeoDistance ordinal [2] Expected: search to return with correct results. Actual: search produces an IOException.
Notes & Observations:
The master bool query also contains other queries in its other clauses. However, the search with the same parameters works when the geo distance query is excluded.
The search is successful if I manually copy the master bool query string and paste it into my ElasticSearch Head browser plugin (and also curl I'm assuming).
It looks like we accidently broke backward compatibility here. Unfortunately, I cannot think of any temporary workaround besides using a client and a server with the same major version.
imotov
added a commit
to imotov/elasticsearch
that referenced
this issue
Mar 31, 2018
Restores backward compatibility in GeoDistanceQueryBuilder serialization
between 6.x and 5.6 after removal of optimize_bbox parameter.
Closeselastic#29301
Elasticsearch server version:
{"number": "5.6.6","lucene_version": "6.6.1"}
Elasticsearch client version:
6.2.1
Plugins installed:
[{ "name": "x-pack", "version": "5.6.6", "description": "Elasticsearch Expanded Pack Plugin", "classname": "org.elasticsearch.xpack.XPackPlugin", "has_native_controller": true }]
JVM version:
1.8.0_151
OS version: Linux ubuntu 4.4.0-116-generic
Description of the problem including expected versus actual behavior:
When I include a geo distance query into the should clause of my master bool query and use this query to search for results, it would produce a
java.io.IOException: Unknown GeoDistance ordinal [2]
Expected: search to return with correct results. Actual: search produces an IOException.
Notes & Observations:
Steps to reproduce:
Stack trace:
java.io.IOException Unknown GeoDistance ordinal [2].txt
The text was updated successfully, but these errors were encountered: