-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Error with geo_shape relation CONTAINS #17866
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
Comments
@glascaleia can you please post the query you're running that's giving you this error? |
{ |
This fails for me on 2.3.0, but works on master. Full recreation:
|
@glascaleia what version of ES? @clintongormley can you confirm the following exception? "reason": "Failed to find geo_shape field [mountainNowArea.location]", Can you confirm success when explicitly searching the GET t/_search This failure is unrelated to the original IAE issue. So it sounds to me like there are 2 separate issues. |
Fixed by 26b078f |
Hi all.
I have the following error trying to execute a spatial query with a ShapeRelation Contain.
aused by: java.lang.IllegalArgumentException:
at org.elasticsearch.index.query.GeoShapeQueryParser.getArgs(GeoShapeQueryParser.java:192)
at org.elasticsearch.index.query.GeoShapeQueryParser.parse(GeoShapeQueryParser.java:169)
at org.elasticsearch.index.query.QueryParseContext.parseInnerQuery(QueryParseContext.java:250)
at org.elasticsearch.index.query.QueryParseContext.parseInnerFilter(QueryParseContext.java:263)
at org.elasticsearch.index.query.IndexQueryParserService.parseInnerFilter(IndexQueryParserService.java:220)
at org.elasticsearch.search.query.PostFilterParseElement.parse(PostFilterParseElement.java:33)
at org.elasticsearch.search.SearchService.parseSource(SearchService.java:838)
at org.elasticsearch.search.SearchService.createContext(SearchService.java:654)
at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:620)
at org.elasticsearch.search.SearchService.executeQueryPhase(SearchService.java:371)
Regards
The text was updated successfully, but these errors were encountered: