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

Truncate long fields in Discover server-side #98497

Closed
Tracked by #166068
timroes opened this issue Apr 27, 2021 · 2 comments
Closed
Tracked by #166068

Truncate long fields in Discover server-side #98497

timroes opened this issue Apr 27, 2021 · 2 comments
Labels
blocked enhancement New value added to drive a business result Feature:Discover Discover Application impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@timroes
Copy link
Contributor

timroes commented Apr 27, 2021

Currenty Discover loads all fields not filtered via the index pattern field filters. This can become problematic if some fields contain very large data that users are not (yet) aware of, thus they might not have had a chance to filter it out via the index patter field filters. Also there might be the case where just some documents contain really large field values. I think we should try to get to a way where we by default will have Elasticsearch truncate long values for us by default (at a reasonably high length) and then show the truncated value and only load the full value of a field once the user explicitly states she wants (i.e. we have "view full field" besides those truncated values).

This would save potentially a lot of bandwidth for documents containing longer values and much more important, makes Kibana faster, since even when not showing those values (i.e. we would truncate them client side) we still need to parse the response and do some level of postprocessing/transformation in our querying highlight.

Related issues: #11457

Blocked on elastic/elasticsearch#72453

@timroes timroes added Feature:Discover Discover Application enhancement New value added to drive a business result Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Apr 27, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@timroes timroes added Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Aug 31, 2021
@davismcphee davismcphee added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated labels Sep 8, 2023
@kertal
Copy link
Member

kertal commented Oct 19, 2023

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. We're always interested in hearing our users opinions, especially if they are Tim Roes ❤️!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked enhancement New value added to drive a business result Feature:Discover Discover Application impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:needs-research This issue requires some research before it can be worked on or estimated 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

4 participants