Open jughosta opened 2 years ago
cc @stratoula
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)
One more thing we might consider: Allowing also to search by id. While for the generated one this makes no sense, but we also allow to provide custom ids
Pinging @elastic/kibana-app-services (Team:AppServicesUx)
Another reason why we need to do this. When we allow ad-hoc data views, once the user enters a text into the search box, we need to be sure that all possible matches of data view for the given pattern are displayed.
in the current state, when the user would enter indexName
and indexName
would have a custom name Index Name
, nothing would be found and given we search the name of indices that would match, we would suggest to use the entered name for an ad-hoc data view.
This is easily done with EuiSelectable, we just need to pass a secondary field to search.
Check https://elastic.github.io/eui/#/forms/selectable --> Custom content
I'd prefer to hear this request from our users. I think this might be a desire to use new functionality in an older way of working. If our users need to identify data views by their underlying index pattern then they can just use the index pattern as the name. I guess I'm skeptical of the need to reference data views in that drop down by BOTH the verbose name and the index pattern.
I see your point here @mattkime and I don't have a strong opinion. I am jus thinking a scenario like:
It could be useful I think! I am fine on waiting the users' feedback too! cc @ghudgins
In case it's still the plan to allow the user to quickly create a ad-hoc data view, if no matching entry can be found, how would this work without allowing the search for the index pattern?
test-*
. TEST
. Just wondering how it works without the ability to search by index pattern too ... btw a while ago I saw an old issue requesting a user to search for an id ... because back in the days we had ids like test-*
, I'm quite sure the search by index pattern will be requested.
Pinging @elastic/kibana-visualizations (Team:Visualizations)
wanted to icebox this, but we don't own this area of the code, reassigning. It could be a good issue for somebody starting ... or something to icebox
Kibana version: main
Description of the problem including expected versus actual behavior: Current
DataViewPicker
allows to filter data views by their name (custom name if provided or index pattern as a fallback). Users might want to be able to search by index pattern field of data views too even if that data view has a custom name.Steps to reproduce:
DataViewsList