-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
fix(dash import): Ensure old datasource ids are not referenced in imported charts #23582
fix(dash import): Ensure old datasource ids are not referenced in imported charts #23582
Conversation
Codecov Report
@@ Coverage Diff @@
## master #23582 +/- ##
=======================================
Coverage 67.71% 67.72%
=======================================
Files 1916 1916
Lines 74014 74019 +5
Branches 8039 8039
=======================================
+ Hits 50122 50126 +4
- Misses 21843 21844 +1
Partials 2049 2049
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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 but @betodealmeida may be more familiar with this code.
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.
Looks great, thanks for fixing this!
Thanks! I was exactly looking for this. So If I import any dashboard from let say 1.5.1 to 2.1.1, it should not produce the false alarm. |
…orted charts (apache#23582) (cherry picked from commit 7034401)
…orted charts (apache#23582) (cherry picked from commit 7034401)
SUMMARY
Currently, charts imported via a dashboard import contain references to the chart's old datasource id from when it was exported within their
params
andquery_context
. This didn't result in any functionality breaking, but it would result in the following "false alarm" error message when loading the dashboard:There is precedent for this fix in the individual chart import, see here: https://github.com/apache/superset/blob/master/superset/charts/commands/importers/v1/__init__.py#L96
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION