We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Example of a request that should return a 400 error:
{"term": {"actor.id": {"value": "95077794"}}}
This is converted into a match all query.
The correct query is:
{"query": {"term": {"actor.id": "95077794"}}}
The text was updated successfully, but these errors were encountered:
{ "query": { "term": { "actor.id": { "value": "95077794" } } } }
BTW, this is also a valid DSL format
Sorry, something went wrong.
Yes ! and we accept both. https://github.com/quickwit-oss/quickwit/blob/main/quickwit/rest-api-tests/scenarii/es_compatibility/0006-term_query.yaml
I think @fmassot's point is that the doc should probably give the full payload (starting from "query")
We could add deny_unknown_fields to the search body struct.
deny_unknown_fields
@fulmicoton I'm wondering if you did not use it deliberately, can you confirm?
It was not deliberate. We should definitely add it!
Thank you @etolbakov !
etolbakov
No branches or pull requests
Example of a request that should return a 400 error:
This is converted into a match all query.
The correct query is:
The text was updated successfully, but these errors were encountered: