A Superset upgrade has one property that shapes everything else: the metadata database migration runs
forward and there is no supported migration backward.
Once the schema is at 4.x, a 3.x image cannot start against it.
Every other risk in an upgrade is recoverable by redeploying the old image. This one is recoverable only by restoring the database.
The playbook below is built around that fact.It is written for the 3.x to 4.x jump on a self-hosted deployment (Docker, Kubernetes or VMs) and applies with small changes to any major version.
The specifics of what changed in 4.0 are from the release’s UPDATING.md; read it for your exact source and target versions rather than relying on this summary.
No comments:
Post a Comment