Open stratoula opened 2 years ago
Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)
Pinging @elastic/kibana-app-services (Team:AppServicesSv)
Does it make sense to do this feature more general and not to be applied only to Discover?
Absolutely.
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)
When considered in the context of field caps performance and mapping explosions, this is potentially a valuable feature - the mapping explosion field could be specified by wildcard and ignored.
Request for field caps to support negation wildcards on field names - https://github.com/elastic/elasticsearch/issues/99450
Describe the feature: This is mostly created for discussion.
Currently, on the dataviews management page you can filter out fields.
This is very useful as there are dataviews with many fields that the users don't want to use so it makes the exploration of the data easier. Atm, this is only applied on Discover and the saved searches.
This creates some confusion because for example I can see these fields on the unified search filter bar. Why can I filter with these fields while I have excluded them?
Same applies for the visualization editors. I expect to not see these fields on Lens for example, as I don't see them on Discover.
Does it make sense to do this feature more general and not to be applied only to Discover?
Discuss post https://discuss.elastic.co/t/apply-index-pattern-field-filters-to-the-add-filter-drop-down-selection/307054