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
I have a document in an index such that the following request returns a match, with the matched_queries element containing query1:
matched_queries
query1
curl -XPOST 'http://localhost:9200/index/_search' –d ' { "query": { "match": { "stuff": { "_name": "query1", "query": "blah" } } } } '
However, if that query is wrapped in a wrapper query, then the name does not appear in the list of matched_queries:
curl -XPOST 'http://localhost:9200/index/_search' –d ' { "query": { "wrapper": { "query": "eyJtYXRjaCI6IHsic3R1ZmYiOiB7Il9uYW1lIjogInF1ZXJ5MSIsICJxdWVyeSI6ICJibGFoIn19fQ==" } } } '
I am using the java api and the WrapperQueryBuilder, but the effect is the same whether using the java api or the rest interface.
WrapperQueryBuilder
(gist with set-up steps in case it's useful: https://gist.github.com/tstibbs/645e01c5dcdfa9d2a193)
The text was updated successfully, but these errors were encountered:
Made sure that named filters and queries defined in a wrapped query a…
be933e0
…nd filter are not lost. Closes #6871
93cf485
687be70
5fb3a54
b6416ae
…nd filter are not lost. Closes elastic#6871
7347042
martijnvg
No branches or pull requests
I have a document in an index such that the following request returns a match, with the
matched_queries
element containingquery1
:However, if that query is wrapped in a wrapper query, then the name does not appear in the list of
matched_queries
:I am using the java api and the
WrapperQueryBuilder
, but the effect is the same whether using the java api or the rest interface.(gist with set-up steps in case it's useful: https://gist.github.com/tstibbs/645e01c5dcdfa9d2a193)
The text was updated successfully, but these errors were encountered: