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
Using version 0.90.5.
Supplying a string in a match query against a boolean type field with its value set to 'true' will return a hit if the query is a non-empty string.
In the following example, the first query returns a result, the second does not.
PUT /test/test/1 { "hello" : true } POST /test/_search { "query": { "bool": { "minimum_number_should_match": 1, "should": [ {"match": { "hello": "foo" }} ] } } } POST /test/_search { "query": { "bool": { "minimum_number_should_match": 1, "should": [ {"match": { "hello": "" }} ] } } }
Obviously this is a really dumb query 😄 .We are fixing our client to not build queries like this. This does seem like odd behavior though.
The text was updated successfully, but these errors were encountered:
Currently null, "", "F", "false", "0", "off" and "no" is parsed as False. Everything else is True.
null
""
"F"
"false"
"0"
"off"
"no"
Sorry, something went wrong.
Thank you Igor.
b723ee0
[DOCS] Update boolean mapping docs with a full list of values that ar…
3b495f6
…e treated as false Closes #5337
No branches or pull requests
Using version 0.90.5.
Supplying a string in a match query against a boolean type field with its value set to 'true' will return a hit if the query is a non-empty string.
In the following example, the first query returns a result, the second does not.
Obviously this is a really dumb query 😄 .We are fixing our client to not build queries like this. This does seem like odd behavior though.
The text was updated successfully, but these errors were encountered: