-
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
Dashboard migration issue from 6.1 dashboards #42519
Labels
bug
Fixes for quality problems that affect the customer experience
Comments
stacey-gammon
added
the
bug
Fixes for quality problems that affect the customer experience
label
Aug 2, 2019
rudolf
added a commit
to rudolf/kibana
that referenced
this issue
Aug 2, 2019
rudolf
added a commit
that referenced
this issue
Aug 6, 2019
rudolf
added a commit
to rudolf/kibana
that referenced
this issue
Aug 6, 2019
* Fixes elastic#42519 dashboard migration bug * Tests * Dashboard migration errors: log stack and dashboard document
rudolf
added a commit
to rudolf/kibana
that referenced
this issue
Aug 6, 2019
* Fixes elastic#42519 dashboard migration bug * Tests * Dashboard migration errors: log stack and dashboard document
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have a dashboard created in 6.1 that contains a saved search that has been saved with column or sort overrides on the panel, you will not be able to upgrade to 7.3. (Caveat - this is more theory from looking at the code and knowing the problem than actually tested, but I'm relatively confident).
The issue is, in
migrate610PanelToLatest
:When
uiState
is an empty object,embeddableConfig
is undefined.Luckily, the (almost) same code in
migratePre61PanelToLatest
doesn't have this issue:so it's only explicitly for 6.1.
Another good point to mention is that this is the start of the bug, but what really kills it is because the document doesn't get updated by the uiStateJSON being removed because it bails early, and the mappings were changed. I could have waited till a major to update the mapping to be more careful.
cc @rudolf @timroes
JSON that will hit the error if imported (created from 6.1)
The text was updated successfully, but these errors were encountered: