-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
TSVB visualizations with no timefield do not render after upgrading from 7.12.1 to 7.13.0 #102494
Conversation
…rom 7.12.1 to 7.13.0 Part of: elastic#100778
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @alexwizp |
Pinging @elastic/kibana-app (Team:KibanaApp) |
series, | ||
esQueryConfig, | ||
seriesIndex, | ||
capabilities, |
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.
Why do we add capabilities and uiSettings? They are not used anywhere in the query function.
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.
Yes, this is a disgusting part of processor implementations. This is a function that accepts a sequence of arguments. So it's important for us to keep order
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.
Do you want to add a comment? In order to not confuse us :D
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.
It happens across all request/response processors. I'll create an issue to fix that
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.
LGTM, I tested it locally by migration 7.9.3 and 7.12.1 SOs that haven't defined their timefield and it works fine. I also tested 7.13.2 saved objects.
I would appreciate it if somebody else from the team could also test it thoroughly.
cc @dziyanadzeraviankina @VladLasitsa
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.
LGTM, tested 7.13.2 saved objects.
…rom 7.12.1 to 7.13.0 (elastic#102494) * TSVB visualizations with no timefield do not render after upgrading from 7.12.1 to 7.13.0 Part of: elastic#100778 * fix CI
…rom 7.12.1 to 7.13.0 (elastic#102494) * TSVB visualizations with no timefield do not render after upgrading from 7.12.1 to 7.13.0 Part of: elastic#100778 * fix CI # Conflicts: # src/plugins/vis_type_timeseries/server/lib/vis_data/get_interval_and_timefield.ts # src/plugins/vis_type_timeseries/server/lib/vis_data/get_table_data.ts # src/plugins/vis_type_timeseries/server/lib/vis_data/request_processors/series/date_histogram.js # src/plugins/vis_type_timeseries/server/lib/vis_data/request_processors/series/date_histogram.test.js # src/plugins/vis_type_timeseries/server/lib/vis_data/request_processors/table/date_histogram.js
…ading from 7.12.1 to 7.13.0 (#102494) (#102645) * TSVB visualizations with no timefield do not render after upgrading from 7.12.1 to 7.13.0 (#102494) * TSVB visualizations with no timefield do not render after upgrading from 7.12.1 to 7.13.0 Part of: #100778 * fix CI # Conflicts: # src/plugins/vis_type_timeseries/server/lib/vis_data/get_interval_and_timefield.ts # src/plugins/vis_type_timeseries/server/lib/vis_data/get_table_data.ts # src/plugins/vis_type_timeseries/server/lib/vis_data/request_processors/series/date_histogram.js # src/plugins/vis_type_timeseries/server/lib/vis_data/request_processors/series/date_histogram.test.js # src/plugins/vis_type_timeseries/server/lib/vis_data/request_processors/table/date_histogram.js * fix CI
…-png-pdf-report-type * 'master' of github.com:elastic/kibana: (447 commits) skip flaky suite (elastic#102366) [Security Solution][Endpoint][Host Isolation] Isolation status badge from alert details (elastic#102274) Add email connector info for Elastic Cloud (elastic#91363) [Workplace Search] remove or replace xs props for text on source connect view (elastic#102663) Do not double register dashboard url generator (elastic#102599) [TSVB] Replaces EuiCodeEditor 👉 Monaco editor (elastic#100684) [Discover] Update kibana.json adding owner and description (elastic#102292) [Exploratory View] Mobile experience (elastic#99565) chore(NA): moving @kbn/ui-shared-deps into bazel (elastic#101669) [TSVB] Index pattern select field disappear in Annotation tab (elastic#102314) [Security Solution][Endpoint][Host Isolation] Fixes bug where host isolation/unisolation works from alert details (elastic#102581) TSVB visualizations with no timefield do not render after upgrading from 7.12.1 to 7.13.0 (elastic#102494) [Logs UI] Add `event.original` fallback to message reconstruction rules (elastic#102236) [ML] Remove blank job definition as it is unused and out-of-sync with Elasticsearch (elastic#102506) [Lens] Fix wrong error detection on transition to Top values operation (elastic#102384) [ML] Anomaly detection job custom_settings improvements (elastic#102099) [Cases] Route: Get all alerts attach to a case (elastic#101878) Fixes wrong list exception type when creating endpoint event filters list (elastic#102522) remove search bar that's not working yet (elastic#102550) Migrated Ingest Node Pipeline Functional Tests to use test_user (elastic#102409) ... # Conflicts: # x-pack/plugins/reporting/public/share_context_menu/register_pdf_png_reporting.tsx
Part of: #100778
Summary
This is a follow-up PR that should fix the issue where the time field is not showing after upgrading from
7.12.1
to7.13.0
. Many of our users are usingTSVB
without a configured time field. In the previous implementation, this worked because we had no separation betweenES
andKibana
indexes.After
7.13.0
we have 2 different modes forES
andKibana
indexes. The main problem here is that there is no default time field value in theES
index. As a result, the users see a message about no data.Steps to reprocude:
Expected result: some data should be displayed
Screens
Before
After