> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/platform-reference/version-upgrades.md).

# 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 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](/query-engine/reference/platform-reference/release-notes-format.md) 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](/query-engine/guides/deployment/azure-in-vpc.md), platform component versions are pinned in your deployment configuration. To upgrade, follow the in-cluster process in [Component versions and operations](/query-engine/guides/deployment/azure-in-vpc/component-versions-and-operations.md). The same in-Console upgrade UI is available for the workspace-managed components.

## See also

* [Release notes format](/query-engine/reference/platform-reference/release-notes-format.md)
* [Changelog](/query-engine/changelog/changelog.md) - what's in each release
* [Upgrades and releases](/query-engine/guides/operations/upgrades-and-releases.md) - the full upgrade workflow


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/reference/platform-reference/version-upgrades.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.