How to upgrade
From the Compute Plane:- Open Settings → Version Upgrades.
- Find the component you want to upgrade (Platform Components or Metadata Service).
- Click the version dropdown to see available versions.
- Select the target version.
- Click Upgrade.
What you can upgrade
Platform Components
The shared workspace infrastructure - console, API server, query routing, and related services. Cluster runtimes are versioned separately on each cluster. Upgrade frequency: typically every 4–6 weeks following an e6data release.Metadata Service (MDS)
The metadata catalog - schema and storage metadata for connected catalogs. Affects catalog refresh and schema-discovery behavior. Upgrade frequency: typically every 6–8 weeks, sometimes coordinated with Platform Components.During an upgrade
For most upgrades, users won’t notice anything other than the version dropdown changing.
When to upgrade vs. wait
The release notes for each version explain what’s changed. See Release notes format for what each field means.
Rolling back
If an upgrade introduces an issue, roll back by selecting the previous version from the dropdown and clicking Upgrade again. Rollback follows the same rolling pattern - no downtime, active queries unaffected. For very recent breaking changes, contact e6data support, as some rollbacks need coordination if the new version migrated state forward.In-VPC deployments
For In Your VPC deployments (AWS, Azure), platform component versions are pinned in your deployment configuration. To upgrade, follow the in-cluster process in Component versions and operations for AWS or Azure. The same in-Console upgrade UI is available for the workspace-managed components.See also
- Release notes format
- Changelog - what’s in each release
- Upgrades and releases - the full upgrade workflow