> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 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:

1. Open **Settings → Version Upgrades**.
2. Find the component you want to upgrade (Platform Components or Metadata Service).
3. Click the version dropdown to see available versions.
4. Select the target version.
5. 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 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

| 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](/platform/reference/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](/platform/deploy/aws-cloudprem), [Azure](/platform/deploy/azure-cloudprem)), platform component versions are pinned in your deployment configuration. To upgrade, follow the in-cluster process in Component versions and operations for [AWS](/platform/deploy/aws-cloudprem/component-versions-and-operations) or [Azure](/platform/deploy/azure-cloudprem/component-versions-and-operations). The same in-Console upgrade UI is available for the workspace-managed components.

## See also

* [Release notes format](/platform/reference/release-notes-format)
* [Changelog](/release-notes) - what's in each release
* [Upgrades and releases](/platform/upgrades) - the full upgrade workflow


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.