-
Notifications
You must be signed in to change notification settings - Fork 297
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
Failure to parse query with special characters via Elasticsearch search endpoints #5089
Comments
fixed in quickwit-oss/tantivy#2416, we still have to update the tantivy used in quickwit |
Thank you! |
hum, actually there might be a 2nd issue, but I'm not entirely sure. Is that the result you expect? |
No, elastic definitely returns the results matching only the query. in elastic, we have |
oh okay. that field uses the raw tokenizer, then not tokenizing is what should happen indeed |
The documents have a field like this "program": "vector::sources::kafka" |
Describe the bug
In a json string, the escape character also has to be escaped for it to be transmitted correctly, but this creates a parsing error.
Steps to reproduce the behavior:
Query Payload
Response Payload
Expected behavior
The query should be parsed as an escaped colon
:
as described in the docs for escaping special charactersvector\:\:sources\:\:kafka*
The text was updated successfully, but these errors were encountered: