-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Lens] Show 'No data for this field' for empty field in accordion #73772
[Lens] Show 'No data for this field' for empty field in accordion #73772
Conversation
Pinging @elastic/kibana-app (Team:KibanaApp) |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested, works as expected. LGTM
Blocked by: #73226 |
b758ca5
to
ea914d7
Compare
The "system fields" Also, @wylieconlon do you know why it's showing 95%? Pretty sure the |
The shard size we use for the sampler aggregation is 5000, and this data appears to be on a single shard. So |
The behavior looks good to me. @KOTungseth I think we could use some help with the copy. Basically these empty fields can still be applied to their configurations, but the charts won't populate with data from it most likely because their current time range doesn't contain data for this field.
|
@flash1293 issue added here: #75632 |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested again and I'm fine with this state. It's now showing the "This field is empty because it doesn’t exist in the 500 sampled documents" popover for rollup fields as well, but I can address this separately on the rollup PR once this one is merged.
Thanks @flash1293 for checking. I'll talk to @KOTungseth about the copy and merge it asap! |
This is a great change! I have one small tweak: Can we move the noun to the front of the message? For example: This field doesn't have data. Drag and drop to visualize. |
x-pack/plugins/lens/public/indexpattern_datasource/field_item.tsx
Outdated
Show resolved
Hide resolved
x-pack/plugins/lens/public/indexpattern_datasource/field_item.tsx
Outdated
Show resolved
Hide resolved
💚 Build SucceededBuild metricspage load bundle size
History
To update your PR or re-run it, just comment with: |
* master: (71 commits) [Lens] Show 'No data for this field' for empty field in accordion (elastic#73772) Skip failing lens test Configure ScopedHistory consistenty regardless of URL used to mount app (elastic#75074) Fix returned payload by "search" usage collector (elastic#75340) [Security Solution] Fix missing key error (elastic#75576) Upgrade EUI to v27.4.1 (elastic#75240) Update datasets UI copy to data streams (elastic#75618) [Lens] Register saved object references (elastic#74523) [DOCS] Update links to Beats documentation (elastic#70380) [Enterprise Search] Convert our `public_url` route to `config_data` and collect initialAppData (elastic#75616) [Usage Collection Schemas] Remove Legacy entries (elastic#75652) [Dashboard First] Lens Originating App Breadcrumb (elastic#75470) Improve login UI error message. (elastic#75642) [Security Solution] modify circular deps checker to output images of circular deps graphs (elastic#75579) [Data Telemetry] Add index pattern to identify "meow" attacks (elastic#75163) Migrate CSP usage collector to `kibana_usage_collection` plugin (elastic#75536) [Console] Get ES Config from core (elastic#75406) [Uptime] Add delay in telemetry test (elastic#75162) [Lens] Use index pattern service instead saved object client (elastic#74654) Embeddable input (elastic#73033) ...
…3772) (#75687) Co-authored-by: Elastic Machine <[email protected]>
Summary
Fixes #72517
Fixes the bug of showing wrong message for empty fields as there no field preview available. Current behavior is buggy, the 'no data to display' popup doesn't show up:
That was the behavior before:
After speaking to @cchaos, we've decided going with the following design:
@cchaos, can you confirm the design change is correct?