Nessie Server upgrade notes¶

The following table lists the upgrade types from one Nessie version to another Nessie version.

A check-mark in the Rolling Upgrade column means that it is okay to run Nessie instances running versions in the From column during the limited time of a rolling-upgrade with Nessie versions in the To column.

A red cross in the Rolling Upgrade column means that rolling upgrades for the mentioned versions are not supported and must be avoided.

Also read the release notes on GitHub and the release notes page.

Rolling Upgrade Supported	From Nessie version	To Nessie version
	0.61.0 or newer	0.101.3 or newer
	0.40.0 or newer	0.61.0 or newer
	0.40.0 or newer	0.60.0 or newer
	< 0.40.0	0.40.0 or newer
	0.26.0 to 0.29.0	0.27.0 to 0.30.0
	0.25.0 or older	0.26.0 or newer
	0.18.0 to 0.24.0	0.19.0 to 0.25.0

Older releases than 0.18.0 are not supported.

See Releases for release notes.

Rolling upgrades target version notes¶

Also read the release notes on GitHub and the release notes page.

“Legacy” version store types¶

The version store types ROCKS, MONGO, DYNAMO, TRANSACTIONAL and INMEMORY were deprecated for a long time and have been removed in Nessie 0.75.0!

If you are using one of these version types migrate to one of the supported version store type mentioned above before upgrading to Nessie 0.75.0 or newer.

The migration process is described in the migration guide.

Nessie 0.61.0¶

The serialized format of internal key-indexes got bumped. For a rolling-upgrade to version 0.61.0 or newer, follow these steps.

1. Deploy Nessie with the system property nessie.internal.store-index-format-version set to 1
2. Perform the rolling upgrade to 0.61.0 or newer
3. Remove the system property nessie.internal.store-index-format-version (or set it to 2)
4. Perform a rolling restart

Alternatively you can also stop all Nessie instances, upgrade those and just restart.