BUGFIX: Use multi_match instead of query_string #311
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By using
multi_match
instead ofquery_string
within our searchquery, we prevent the accidental injection of Lucene search query
strings. Currently an exception is thrown when adding
"
to your search query.Using
multi_match
instead should lead to the same quality of resultsand is less prone to user errors, because in 99% of cases the search is
used for classic search terms and no end user is expected to know the
compact Lucene query string syntax.
see: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/query-dsl-multi-match-query.html
see: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/query-dsl-query-string-query.html
see: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/query-dsl-query-string-query.html#query-string-syntax