Version upgrades

How to upgrade Platform Components and the Metadata Service for your workspace, and what to expect.

Two upgradeable elements appear in Settings → Version Upgrades inside the Compute Plane: Platform Components and the Metadata Service.

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.

The upgrade runs in the background. The page shows progress and the current vs. target version.

What you can upgrade

Platform Components

The core platform - query routing, planner, and executor runtime. Affects how queries are routed and executed. 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

Aspect

Behavior

Active queries

Continue to completion on the old version

New queries during upgrade

Routed to the new version once it's ready

Downtime

Typically none; the platform performs rolling upgrades

Total time

Usually 1–5 minutes per component

For most upgrades, users won't notice anything other than the version dropdown changing.

When to upgrade vs. wait

Situation

Recommendation

New version brings a feature you need

Upgrade

Security or critical bug fix

Upgrade promptly

Major version bump (breaking changes possible)

Read release notes first; test on a non-prod workspace

Minor or patch version

Generally safe to upgrade in place

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, platform component versions are pinned in your deployment configuration. To upgrade, follow the in-cluster process in Component versions and operations. The same in-Console upgrade UI is available for the workspace-managed components.