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
"Cannot parse" Exception #812
Comments
I have this error too. |
The query syntax parser is strict and is part of lucene - out of our control. Remove the comma and it parses correctly |
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
the ip is now `76.132.96.42` Approved-by: Gabi Davar
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This commit fixes issues with supporting Elasticsearch 7.x This handles the removal of the '_routing' field name and '_retry_on_conflict' update action aliases in place of 'routing' and 'retry_on_conflict' respectively in Elasticsearch 7.x. Also fixes integration tests to handle these changes and the renaming of doc type from 'doc' to '_doc' and the mapping name change from `_default_` to '_doc'. Fixes elastic#812
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
Remove unrelated comment from ci/run.sh Test against 6.0.0 to ensure name changes are correct. Fixes elastic#812
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
_retry_on_conflict is required for 6.0, allowed for other 6.x, and forbidden on 7.0 retry_on_conflict is forbidden for 6.0, alllowed for other 6.x, required for 7.0 Fixes elastic#812
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was stumbling my way through querying and ran in to the following exception. I understand that I have no idea what I'm doing here, and was giving it invalid input, but I guess I wasn't expecting an exception.
The query i was using is below
Note the comma in the q= string is, what I believe, causes it to throw the exception.
The text was updated successfully, but these errors were encountered: