Add Support for analyzed wildcard queries

[german23]

Hey guys,

actually if you define an filter or an query string like "url:facebook*", kibana will make this ES query out of it:

"query": {
                  "query_string": {
                    "query": "request:(facebook.*)"
                  }
                },

due to the behavior of ES this high level query will be converted into an low-level wilcard query which wont used the defined search_analyzer for its query and so if you have an char_filter defined in your mapping that convert e.g. "." to "" at the index time, the kibana query wont find it because the query dont use the search analyzer which would convert "facebook.*" to "facebook*".

To avoid this nasty behaviour there is an option in the ES/Lucene query syntax called "analyze_wildcard".

If kibana would make this:

query": {
                  "query_string": {
                    "analyze_wildcard" : true,
                    "query": "request:(facebook.*)"
                  }
                },

out of the defined filter/querystring, the kibana query would return valid responses.

Is it possible to add such an option, like an checkbox to check when using an filter/querystring?

[rashidkpc]

Setting analyze_wildcard by default is probably a good idea. We could probably also make this an Advanced settings item to allow users to specify additional options for the default query_string behavior

[rashidkpc]

Hmm, this exists in many places. Might be a bit bit tougher than I anticipated to track them all down.

[rashidkpc]

I wonder if it makes more sense to allow query_string parameters to be set as an object since there's so many possible.