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.

Sign up for GitHub

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

Jump to bottom

[Dataviews] Field filters filter out fields only on Discover #134305

Open
Tracked by #166175
stratoula opened this issue Jun 14, 2022 · 5 comments
Open
Tracked by #166175

[Dataviews] Field filters filter out fields only on Discover #134305

stratoula opened this issue Jun 14, 2022 · 5 comments
Labels
enhancement New value added to drive a business result Feature:Data Views Data Views code and UI - index patterns before 8.0 impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@stratoula
Copy link
Contributor

stratoula commented Jun 14, 2022 •
edited
Loading

Describe the feature:
This is mostly created for discussion.

Currently, on the dataviews management page you can filter out fields.
image

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
@stratoula stratoula added discuss enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure Team:AppServicesSv labels Jun 14, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

@mattkime
Copy link
Contributor

Does it make sense to do this feature more general and not to be applied only to Discover?

Absolutely.

@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jul 21, 2022
@exalate-issue-sync exalate-issue-sync bot added the loe:small Small Level of Effort label Sep 26, 2022
@jughosta jughosta mentioned this issue Oct 24, 2022
Closed
31 tasks
@petrklapka petrklapka added Feature:Data Views Data Views code and UI - index patterns before 8.0 Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Team:AppServicesSv labels Nov 28, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@stratoula stratoula added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. discuss labels Jun 1, 2023
@davismcphee davismcphee added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Sep 8, 2023
@mattkime
Copy link
Contributor

mattkime commented Sep 11, 2023 •
edited
Loading

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 - elastic/elasticsearch#99450

@kertal kertal mentioned this issue Sep 24, 2024
Open
@kertal kertal added the Icebox label Sep 24, 2024
@kertal kertal removed the Icebox label Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:Data Views Data Views code and UI - index patterns before 8.0 impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mattkime @kertal @elasticmachine @stratoula @davismcphee @petrklapka