Kibana version: master
Elasticsearch version: master
Original install method (e.g. download page, yum, from source, etc.): source
Description of the problem including expected versus actual behavior: The user in the discuss form pasted below is trying to do a partial matching using kibana filters. Currently there is no way to do a wildcard query or have a contain
field in the Add filter dialog box. This is not possible in the editor UI at the moment. Hence this enhancement request for the same :
https://discuss.elastic.co/t/kibanas-filter-partial-matching/98494/8
@rasroh thank you for creating issue)
I'm no ES expert, so this is just an opinion/view on UX implementation details
Since ElasticSearch uses prefix-based inverted-index for strings, I suppose letting the user apply a query that supports * is better than just using "contains"? With the former there is a possibility of a cheaper search - thisText* as opposed to contains which _has_ to mean *thisText*, right?
Community PR for this issue https://github.com/elastic/kibana/pull/16357
Needs review from Kibana team
Can we get some traction on this and PR #16357? Almost two years now.
Pinging @elastic/kibana-app-arch (Team:AppArch)
Hello Kibana team, can i search for a pattern ending with or exact match? I have a parameter name 'request' which contains request url and I am interested to search for a exact match to be able to confirm if I can deprecate it based on the usage, but the search results give a huge list in which my pattern word is in between, which is not useful. As I am interested in exact match.
Most helpful comment
Can we get some traction on this and PR #16357? Almost two years now.