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
Prior to #6217, querying for name:ndap-home would by default generate something like:
name:ndap-home
{ "match": { "name": { "query": "ndap-home", "operator": "and" } } }
Matching only fields with both ndap and home after the query is analysed.
ndap
home
With #6217 the operator: and option is no longer specifying, and so fields with either ndap or home are now matched.
operator: and
The text was updated successfully, but these errors were encountered:
tobio
Successfully merging a pull request may close this issue.
Prior to #6217, querying for
name:ndap-home
would by default generate something like:Matching only fields with both
ndap
andhome
after the query is analysed.With #6217 the
operator: and
option is no longer specifying, and so fields with eitherndap
orhome
are now matched.The text was updated successfully, but these errors were encountered: