mirror of
https://github.com/apache/superset.git
synced 2026-04-24 10:35:01 +00:00
0fb7fc2721
Major restructuring of documentation to separate concerns: **New Structure:** - `/docs/` - User-facing docs (intro, quickstart, databases, using-superset, faq) - `/admin-docs/` - Administrator docs (installation, configuration, security) - `/developer-docs/` - Developer docs (contributing, extensions, guidelines, testing) **Changes:** - Move installation, configuration, and security docs to admin_docs/ - Move contributing, extensions, guidelines, and testing to developer_docs/ - Rename developer_portal to developer_docs (with underscore to hyphen in URL) - Add sidebarAdminDocs.js for admin documentation navigation - Update versions-config.json with new doc sections - Update docusaurus.config.ts with new plugins and redirects - Update internal links in versioned docs (6.0.0) to use new paths - Keep user-facing content (databases, using-superset, faq) in main docs This separation makes it clearer which documentation is relevant for: - End users exploring and visualizing data - Administrators deploying and configuring Superset - Developers contributing to or extending Superset Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
62 lines
1.4 KiB
Plaintext
62 lines
1.4 KiB
Plaintext
---
|
|
title: Upgrading Superset
|
|
hide_title: true
|
|
sidebar_position: 6
|
|
version: 1
|
|
---
|
|
|
|
# Upgrading Superset
|
|
|
|
## Docker Compose
|
|
|
|
First, make sure to shut down the running containers in Docker Compose:
|
|
|
|
```bash
|
|
docker compose down
|
|
```
|
|
|
|
Next, update the folder that mirrors the `superset` repo through git:
|
|
|
|
```bash
|
|
git pull origin master
|
|
```
|
|
|
|
Then, restart the containers and any changed Docker images will be automatically pulled down:
|
|
|
|
```bash
|
|
docker compose up
|
|
```
|
|
|
|
## Updating Superset Manually
|
|
|
|
To upgrade superset in a native installation, run the following commands:
|
|
|
|
```bash
|
|
pip install apache_superset --upgrade
|
|
```
|
|
|
|
## Upgrading the Metadata Database
|
|
|
|
Migrate the metadata database by running:
|
|
|
|
```bash
|
|
superset db upgrade
|
|
superset init
|
|
```
|
|
|
|
While upgrading superset should not delete your charts and dashboards, we recommend following best
|
|
practices and to backup your metadata database before upgrading. Before upgrading production, we
|
|
recommend upgrading in a staging environment and upgrading production finally during off-peak usage.
|
|
|
|
## Breaking Changes
|
|
|
|
For a detailed list of breaking changes and migration notes for each version, see
|
|
[UPDATING.md](https://github.com/apache/superset/blob/master/UPDATING.md).
|
|
|
|
This file documents backwards-incompatible changes and provides guidance for migrating between
|
|
major versions, including:
|
|
- Configuration changes
|
|
- API changes
|
|
- Database migrations
|
|
- Deprecated features
|