Wildcard phrases with slop using string query

[S-Dragon0302 (s-Dragon)]

@Vladimir_Sidorenko

Elastic supports slop for simple phrases, like "quick fox"~2, but when wildcards are used in string, it doesn't work: "qui* fox"~2

I've found a workaround for this using json query dsl using span_near and match prefix: http://grokbase.com/t/gg/elasticsearch/146vmnsj7r/workaround-for-using-wild-cards-in-phrases-and-proximity-searches-elastic-search

The thing is that I must allow users to make such queries using string query. Is there any other workaround that uses just query string syntax or maybe there's some plugin that extends query string syntax for this specific use case?

Thank you

Is this kind of query still not supported.

This won't work.

"query_string": {
"fields": [
"nickname"
],
"query": "content:\"hello\" AND \"Rodan Fields?\"",
"default_operator": "AND"
}

Writing "slop" like this won't work

"query_string": {
"fields": [
"nickname"
],
"query": "content:\"hello\" AND Rodan Fields?~2",
"default_operator": "AND"
}

[Mark_Harwood1 (Mark Harwood)]

There is a query syntax and parser that can help but there has been a conscious decision to keep it out of elasticsearch for performance reasons (plugin) feature request: Add support for ComplexPhraseQueryParser · Issue #3875 · elastic/elasticsearch · GitHub