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

[data views] Field conflicts sometimes cause very large payloads for field_caps and fields_for_wildcards_requests #180332

Closed
Tracked by #166175
mattkime opened this issue Apr 9, 2024 · 2 comments
Labels
Feature:Data Views Data Views code and UI - index patterns before 8.0 Icebox impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@mattkime
Copy link
Contributor

mattkime commented Apr 9, 2024

When a data view hits a large number of indices, the field conflict data can be very large due to list of which index corresponds to which field type. This is potentially costly wherever there's network communication, from the browser receiving the file to inter node communication between ES servers to create the response.

In most cases, we're not interested in this information and its not displayed. fields_for_wildcard should accept a param that tosses the index lists. Ideally this could be passed through to field_caps as well.

default (1).json.zip

@mattkime mattkime self-assigned this Apr 9, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 9, 2024
@mattkime mattkime 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. labels Apr 9, 2024
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 9, 2024
@mattkime mattkime added loe:medium Medium Level of Effort impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Apr 11, 2024
@mattkime mattkime removed their assignment Sep 28, 2024
@kertal kertal added the Icebox label Oct 21, 2024
@kertal
Copy link
Member

kertal commented Oct 21, 2024

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.

@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Data Views Data Views code and UI - index patterns before 8.0 Icebox impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

No branches or pull requests

3 participants