Skip to main content
Version: 3.13

How to Upgrade ScalarDB

This guide explains how to upgrade to a newer version of ScalarDB.

Before you begin

Before you upgrade ScalarDB Cluster to a newer version, check the following rules to ensure compatibility between ScalarDB Cluster and the client SDKs.

note

Versions are expressed as x.y.z, where x represents the major version, y represents the minor version, and z represents the patch version. This format follows Semantic Versioning.

  • If the major versions are different between ScalarDB Cluster and a client SDK, they are not compatible and are not supported.
  • If the major versions are the same and the minor versions are different between ScalarDB Cluster and a client SDK, the version of ScalarDB Cluster must be greater than or equal to the client SDK version. For example:
    • Supported: Combination of ScalarDB Cluster 3.13 and client SDK 3.11
    • Not supported: Combination of ScalarDB Cluster 3.11 and client SDK 3.13
  • If the major versions and the minor versions are the same, you can use different patch versions between ScalarDB Cluster and a client SDK. For example:
    • Supported: Combination of ScalarDB Cluster 3.13.2 and client SDK 3.13.0
    • Supported: Combination of ScalarDB Cluster 3.13.0 and client SDK 3.13.2

Upgrade versions

To learn about upgrading your version of ScalarDB, select the type of upgrade you want to do.

Major versions do not keep backward compatibility. So, you might need to do special operations when you upgrade from one major version to another major version. For example:

  • Update the database schema on the backend database side.
  • Update the API in your application.

For details on what you need when you upgrade to a major version, please refer to the release notes for the major version that you want to upgrade to.

warning

ScalarDB does not support downgrading to a previous version (major, minor, or patch). You can only upgrade to a newer version.