Upgrade Prod Superset instance to version 4.0.1

[himeshr]

Acceptance Criteria

• Upgrade our current prod superset to version 4.0.1. https://github.com/apache/superset/releases/tag/4.0.1
  • The metadata is currently stored on the ec2 instance itself, therefore, we'll need to ensure that we take a manual backup before we start with the upgradation work.
• Also, setup automatic storage backups for the prod superset ec2 instance for recovery purposes
• Configure the system to use required features
  • TAGGING_SYSTEM
  • Drill-By
  • Full CSV export Discuss with implementation team and update this section.

Fixing issue with existing report after upgradation

1. Analyse report.
2. If report broken then Categorise into type of issues .
3. Document recovery steps for each issue.
4. Apply fix in all broken reports.

Validation

• All existing reports should not be broken, make changes in reports via sql commands or so to fix large scale modifications required

Tech details

• Create a replica of prod superset ec2 instance
• Upgrade to latest 4.1 version of superset
• No Containers switch
• No DB upgrade
• Configure the system to use all new features
  • TAGGING_SYSTEM
  • Drill-By
  • Full CSV export
• Compare the old and new systems and give it out for UAT to implementation team
• After successful UAT, perform the similar upgradation on Prod Superset
• Bring down the temp infra which is no longer required (Routes and EC2 instances)

Reference doc

https://preset.io/blog/apache-superset-4-0-release-notes/ https://preset.io/blog/superset-3-0-release-notes/

[vedfordev]

Created Documentation For Update File

Issues and Workaround Sheet

[vedfordev]

blocked by https://github.com/apache/superset/issues/28020

Moving card to on hold

[vedfordev]

move card to qa ready. implementation team will do sanity test. @himeshr @pkundu