search

opensearch-project / OpenSearch-Dashboards

📊 Open source visualization dashboards for OpenSearch.
https://opensearch.org/docs/latest/dashboards/index/
Apache License 2.0
1.69k stars 896 forks source link

Viz & Discovery Page Autocomplete #1176

Open Hagaygur opened 2 years ago

Hagaygur commented 2 years ago

I am copying the original issue , as it has since gotten no traction or issues in the OpenSearch GitHub, but seems to make life really painful for quite a whole lot of users (sorry for the formatting,trying to preserve the original issue's format while working):

Kibana OSS 6.0 - 6.3 included autocomplete, but it was removed from Kibana OSS as of 6.4.

We should consider our own implementation (presumably as a new plugin) to improve the day-to-day user experience: Autocomplete on discovery tab not working https://discuss.opendistrocommunity.dev/t/kibana-autocomplete/1779 End of copy.

The issue is CRIPPLING in comparison to Kibana, especially with long and nested field names.

It really deters users, especially with the current filter tab not properly showing field names.

As a stoogap, making the filter show long field names would be nice, but is only a stopgap.

jkowall commented 2 years ago

Are you going to work on this @Hagaygur or are you just making a suggestion (which you have made before based on the other threads). I believe it's pretty obvious that this is a good feature to add, but it also introduces performance issues. Someone needs to sign up for doing the work.

Hagaygur commented 2 years ago

We've unfortunately hit a legal wall as far as contributions ATM - we have an interior patch for the filter window in our deployment, but it appears we're prevented from actually adding any code for now.

Hagaygur commented 2 years ago

The change is also relevant to Autocomplete on the Visualizations Tab, is the change for Discovery Page intended?

seanneumann commented 1 year ago

This feels like an important but not urgent capability. We definitely need it, but let's keep it on the backlog for now as we tackle some of our higher prioritized work (e.g. security, tech debt, revamping ux).

AMoo-Miki commented 1 year ago

@Hagaygur to help the contributors understand the scope of the feature request and the depth of user pain, may i suggest a screenshot or video?

GN93 commented 11 months ago

Are there any updates regarding this feature or is there any workaround? Our company is migrating from Kibana to OpenSearch and I suppose that lack of autocomplete feature might be painful for the users. Thank you in advance for reply!

tr0k commented 11 months ago

We would be interested in having this feature as for some of our users it seems to be very critical. Thank you for any updates on this.

shanilpa commented 11 months ago

@wbeckler @ashwin-pc @dagneyb can we prioritize this for the next release or the one following? - looks like it has been requested for over a year and since we've addressed security, tech debt in prior releases we might be able to fold this in.

We can make use of OUI suggest: https://oui.opensearch.org/1.3/#/forms/suggest Looks like it is built for this specific use case. We can implement with it, run a POC and make UX enhancements based on the findings if needed.

shanilpa commented 11 months ago

@Hagaygur, @GN93, @tr0k are there any specific use cases or workflows you can share with us so we can implement a solution that meets your needs?

tr0k commented 11 months ago

Hi @shanilpa, we have in mind the same as in Kibana. Please check the attached screenshot. image (1)

Hagaygur commented 11 months ago

@Hagaygur, @GN93, @tr0k are there any specific use cases or workflows you can share with us so we can implement a solution that meets your needs?

Hi, there are two major use cases:

  1. Many of the users don't know the exact field names by heart, or the fields can be quite long to type out. The ability to have them suggested really helps to type them correctly and avoid boilerplate.
  2. KQL (ODQL?) is hard for beginners (and even for me sometimes!). The autocomplete suggestions make it much easier to understand.

Edit: misclicked the close issue while on mobile and destroyed all the previous tags. @shanilpa can you reassign?

Tabis1983 commented 6 months ago

Please add this feature. It is too difficult for the users to always guess the fieldnames and therefore really destroys the user expierience in Discover / Visualization / Dashboard.

himanshur04 commented 3 months ago

This feature is very important esp for the cases where we have 100s of indices with each index having more than 50 fields. Any update on the timeline for this feature ?

evilpanda009 commented 5 days ago

This feature would be a huge enhancement to the end user experience. Is this under progress or stuck?