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
Boolean queries with indexed geoshapes break on Elastic Search 6.0 #28456
Comments
Hi @INRIX-Trang-Nguyen, thank you for your report. We would appreciate if you can format your issue according to the template and offer clear steps for reproduction, as this would allow us to better triage this and offer a solution if necessary. |
This change fixes a possible AIOOB during the parsing of the document that contains the indexed shape. This change ensures that the parsing does not continue when the field that contains the shape has been found. Closes elastic#28456
This is a bug introduced in 6.0 that appears when more than one |
This change fixes a possible AIOOB during the parsing of the document that contains the indexed shape. This change ensures that the parsing does not continue when the field that contains the shape has been found. Closes #28456
This change fixes a possible AIOOB during the parsing of the document that contains the indexed shape. This change ensures that the parsing does not continue when the field that contains the shape has been found. Closes #28456
Awesome, thanks for the quick response and fix! Will this make it into ES 6.3? |
Yes it will. |
Hi, guys! Also, can you please advise what are the ways to get all points in shapes / shapes in shapes with Geo query geo_shape (multiple pre-indexed shape) on big geo-spatial data in ElasticSearch? When you have some time, please, I put this question to StackOverflow and also to ElasticSearch discuss forum. Thank you in advance! |
For repro steps, please see:
https://discuss.elastic.co/t/error-using-multiple-geospan-queries-as-bool-should-clauses/113945
The http 500 error occur sporadically under high concurrency (ES queries run as part of an EMR Spark job).
The same job without code changes run in ES 5.5 without issues.
The text was updated successfully, but these errors were encountered: