Skip to content
New issue

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

Searching saved objects should match anywhere in object name #32776

Open
cchaos opened this issue Mar 8, 2019 · 4 comments
Open

Searching saved objects should match anywhere in object name #32776

cchaos opened this issue Mar 8, 2019 · 4 comments
Labels
Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@cchaos
Copy link
Contributor

cchaos commented Mar 8, 2019

Adding to #14729, when searching saved objects, whether in the "Add panel" flyout in dashboards, or the "Select source" of a new visualization, should be able to match user's input to any where within the object's name not just the beginning.

Example: I'm trying to search for all my eCommerce objects, so I just type com but I get 0 results. I would have assumed it should match 'eCommerce'.

cc @flash1293

@timroes timroes added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Mar 11, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@timroes timroes removed the v7.2.0 label Mar 11, 2019
@timroes
Copy link
Contributor

timroes commented Mar 11, 2019

@elastic/kibana-platform this is due to the way we currently using the standard analyzer for that field, and such an underscore won't cause us into terms splitting. Also we're only using suffix wildcards for search, so there is no chance you'll find that unless searching for something like kibana (which would automatically be kibana*). I am not sure what would be the recommended solution here. Should we use a non default analyzer splitting on all non character and exclude the _ for that, since it might be a character more often used for separating your name? Should be allow wildcard prefix (potentially slow)? Should we just keep this as it currently is, since it's the way the standard analyzer works?

@flash1293
Copy link
Contributor

We could add a field with a reversed token filter for title and description https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-reverse-tokenfilter.html, this should give us the equivalent of wildcard prefixes without performance cost, right? I’m not sure how much performance matters in this case, because the searched document count doesn’t exceed a few thousand in normal use cases

@Leaf-Lin
Copy link
Contributor

Leaf-Lin commented Apr 1, 2020

I'm facing this issue as well.
Is it underscore or the standard analyzer causing words to break up unexpectedly?

When I was trying to add new visualization into the dashboard, searching for ess only gives me somehow unexpected object hits:

Screen Shot 2020-03-31 at 5 45 40 pm

I'm expecting the following hits:
Screen Shot 2020-03-31 at 5 45 29 pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

5 participants