GitHub user sword141992 added a comment to the discussion: Critical Display Issues After Upgrading Superset from 4.0.1 to 6.0.0
Hi! Unfortunately, the migration attempts didn't help—the issue with broken dashboards remains. The team has agreed on the following plan: 0) Freeze the current Superset instance for writing, leaving it read-only (no new data, but business can still view dashboards). 1) Create a dump of the old Superset version database. 2) In PostgreSQL, create a new database for Superset v6. 3) Connect to the new database. 4) Load the dump: `pg_restore -h pg_host -p 5432 -U superset -d superset-6 -v postgres_superset.dump` 5) Start the new Superset instance and verify the migration was successful. 6) The entire BI and analytics team will proceed to fix dashboards, charts, etc. 7) After fixes, decommission the old Superset and update the domain to point to the corrected instance. The work has been scheduled, and the total migration time is estimated at 3–5 days(for our data volume). I really hope future version migrations will go smoother—unless, of course, there are major frontend changes again. GitHub link: https://github.com/apache/superset/discussions/37145#discussioncomment-15678954 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
