You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "zitou54 (via GitHub)" <gi...@apache.org> on 2025/03/18 17:13:52 UTC
[D] Migration from 1.X to 4.X [superset]
GitHub user zitou54 created a discussion: Migration from 1.X to 4.X
### Bug description
Dear All,
I have migrated my Superset from version 1.4 to 4.1 (we have a new feature, and itโs great ^^). However, I am facing a major issue with my charts. I can see them in my dashboard, but when I try to edit them, the chart information appears empty (e.g., database, metric field, etc.).
Could you please advise on how I can fix this issue? Do I need to recreate all my charts from scratch?
zi
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
GitHub link: https://github.com/apache/superset/discussions/32725
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Migration from 1.X to 4.X [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Migration from 1.X to 4.X
<!-- Answer -->
The issue you're experiencing with charts appearing empty after migrating from Superset 1.4 to 4.1 might be related to changes in the chart data model and how chart parameters are handled in the newer version. Superset 4.1 includes significant refactoring and restructuring of the chart data model, which could affect how existing charts are displayed and edited.
To address this issue, you can try the following steps:
1. **Check Migration Scripts**: Ensure that any migration scripts provided by Superset have been executed. These scripts are designed to update chart parameters to be compatible with the new version. Specifically, look for scripts that handle time comparison parameters, as these have been updated in version 4.1 <sup>[[1]](https://github.com/apache/superset/blob/master/tests/integration_tests/migrations/f84fde59123a_update_charts_with_old_time_comparison__test.py)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/superset/migrations/versions/2024-05-10_18-02_f84fde59123a_update_charts_with_old_time_comparison.py)</sup>.
2. **Review Chart Parameters**: Manually inspect the parameters of the affected charts. There might be discrepancies in how parameters like `time_comparison` are now handled as `time_compare`, along with other changes in parameter names and structures.
3. **Recreate Charts**: If the above steps do not resolve the issue, you may need to recreate the charts. This can ensure that all parameters are correctly set according to the new data model.
Unfortunately, there isn't a specific script mentioned in the available information that directly addresses this issue. However, ensuring that all migration steps are followed and parameters are correctly updated should help in resolving the problem.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/103732ce-016a-4141-b664-aa695695af8e?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/32725#discussioncomment-12541783
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Migration from 1.X to 4.X [superset]
Posted by "zitou54 (via GitHub)" <gi...@apache.org>.
GitHub user zitou54 added a comment to the discussion: Migration from 1.X to 4.X
Thanks robot but I'm looking for a script or something.
GitHub link: https://github.com/apache/superset/discussions/32725#discussioncomment-12541732
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Migration from 1.X to 4.X [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Migration from 1.X to 4.X
<!-- Greeting -->
Hello @zitou54! ๐ I'm here to assist you with any bugs, questions, or contributions you have for Superset. I'm an expert bot and I'm here to help while you wait for a human maintainer.
<!-- Answer -->
The issue you're experiencing with charts appearing empty after migrating from Superset 1.4 to 4.1 might be related to changes in the data model and chart configurations between these versions. Specifically, there have been significant changes in how certain chart types are handled, such as the migration of `dist_bar` to `echarts_timeseries_bar` and `bubble` to `bubble_v2`, which involve renaming keys, removing certain keys, and setting default values <sup>[[1]](https://github.com/apache/superset/blob/master/superset/migrations/shared/migrate_viz/processors.py)</sup>.
To address this issue, you might need to:
1. **Check Chart Configurations:** Review the configurations of your charts to ensure they align with the new data model. Pay attention to any renamed or removed keys and update them accordingly.
2. **Migration Scripts:** Although I couldn't find specific migration scripts or tools in the repository, it's worth checking if there are any available in the Superset documentation or community resources that could assist with the transition.
3. **Manual Adjustments:** If automatic migration tools are not available, you may need to manually adjust the chart configurations to match the new version's requirements.
Recreating all charts from scratch might not be necessary if you can adjust the existing configurations to fit the new model. However, if the changes are extensive and manual adjustments are not feasible, recreating the charts could be a more straightforward solution.
<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d7497281-663f-460f-82bf-76a2939077cf?feedback_type=other)</sup>
GitHub link: https://github.com/apache/superset/discussions/32725#discussioncomment-12541730
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Migration from 1.X to 4.X [superset]
Posted by "sadpandajoe (via GitHub)" <gi...@apache.org>.
GitHub user sadpandajoe added a comment to the discussion: Migration from 1.X to 4.X
Going to convert this to a discussion to see if someone is able to help you out unless if you have some kind of logs that we can see if there is a bug with the migration.
GitHub link: https://github.com/apache/superset/discussions/32725#discussioncomment-12541733
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org