[XY Chart] Fix "No data to display" error when using IP range aggregation to split series#93024
Conversation
This reverts commit f2b088e.
|
Pinging @elastic/kibana-app (Team:KibanaApp) |
stratoula
left a comment
There was a problem hiding this comment.
LGTM, tested it locally, now the ip range works either with split series or as an aggregation on the x-axis
|
@elasticmachine run elasticsearch-ci/docs |
|
|
||
| export const isRangeAggType = (type: string | null) => | ||
| type === BUCKET_TYPES.DATE_RANGE || type === BUCKET_TYPES.RANGE; | ||
| type === BUCKET_TYPES.DATE_RANGE || type === BUCKET_TYPES.RANGE || type === BUCKET_TYPES.IP_RANGE; |
wylieconlon
left a comment
There was a problem hiding this comment.
Can you add some tests for this?
wylieconlon
left a comment
There was a problem hiding this comment.
Marking as change requested for three reasons:
- No tests
- The title of the PR does not meet our release note standards. If this title appeared in our release notes, users might think that you've removed the IP range split. Instead, the title should answer the question "what can I do now that was broken before?"
- The PR labels indicate that this is for 7.12.1, which is only true if you merge this after we release 7.12- anything merged before 7.12 is released onto the 7.12 branch will be 7.12.0
|
@wylieconlon thank you for your review. I agree, it is a great opportunity to add tests, I also missed the label, I changed it. We plan to merge it for 7.12.0. As this is a bug introduced with the new xy plugin that will be released on 7.12.0 too, this PR won't appear on the release notes as the bug "never existed". Nevertheless, the title is confusing and needs to be changed 👍 |
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
|
@elasticmachine run elasticsearch-ci/docs |
wylieconlon
left a comment
There was a problem hiding this comment.
Thanks, LGTM! Please add the 7.13.0 tag as well.
…tion to split series (elastic#93024) * Visualize: Can't use ip range to split series in xy chart * Refactor accessors.tsx * Revert "Refactor accessors.tsx" This reverts commit f2b088e. * Add accessors.test to cover getComplexAccessor function
…tion to split series (elastic#93024) * Visualize: Can't use ip range to split series in xy chart * Refactor accessors.tsx * Revert "Refactor accessors.tsx" This reverts commit f2b088e. * Add accessors.test to cover getComplexAccessor function
* master: (45 commits) Add outcome of node scripts/build_api_docs (elastic#93399) [Lens] fix long field name on field stats panel doesn't wrap (elastic#93279) [Bug] Fix filter creation for numeric scripted fields in Discover (elastic#93224) [uptime] Fix anomaly alert edit (elastic#93025) Consolidate @babel/* packages and use latest compatible version (elastic#93264) [Search Embeddable] Add highlighting when searching (elastic#93178) [APM] Add missing bottom border to header (elastic#93179) [CI] No longer collect APM span stack traces (elastic#93263) [XY Chart] Fix "No data to display" error when using IP range aggregation to split series (elastic#93024) update generated public api docs API DOCS Step 3/3 (elastic#92929) chore(NA): look for bazel packages on npm_module folder during distributable build (elastic#93262) rename advanced setting ml:fileDataVisualizerMaxFileSize to fileUpload:maxFileSize and increase max geojson upload size to 1GB (elastic#92620) [kbn/optimizer] allow customizing the limits path from the script (elastic#93153) [Alerting][Docs] Adding template for documenting alert and action types (elastic#92830) [jenkins] convert baseline capture job to use tasks (elastic#93288) removing the linked issue in comments from PR (elastic#93303) chore(NA): do not include fs within a storybook build (elastic#93294) [Maps] Update Map extent queries to use bounding box logic for both point and shape queries (elastic#93156) Add searchDuration to EQL and Threshold rules (elastic#93149) ...
Closes #92835
Summary
Fix "No data to display" error for XY chart.
For IP range aggregation

visDatacontains data with range object instead of simple string or number, so series should have complex accessors in this case.Added an IP range for aggregation range types check.
For maintainers