Nessie 0.102.2
- 6 commits since 0.102.1
- Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.102.2
- Docker images: https://github.com/projectnessie/nessie/pkgs/container/nessie and https://quay.io/repository/projectnessie/nessie?tab=tags
It is a multiplatform Java image (amd64, arm64, ppc64le, s390x):docker pull ghcr.io/projectnessie/nessie:0.102.2-java - PyPI: https://pypi.org/project/pynessie/ (See pynessie)
- Helm Chart repo: https://charts.projectnessie.org/
Try it
The attached nessie-quarkus-0.102.2-runner.jar is a standalone uber-jar file that runs on Java 17 or newer and it is also available via Maven Central. Download and run it (requires Java 17):
wget https://github.com/projectnessie/nessie/releases/download/nessie-0.102.2/nessie-quarkus-0.102.2-runner.jar
java -jar nessie-quarkus-0.102.2-runner.jar
Nessie CLI is attached as nessie-cli-0.102.2.jar, which is a standalone uber-jar file that runs on Java 11 or newer. Nessie CLI is also available as a Docker image: docker run --rm -it ghcr.io/projectnessie/nessie-cli:0.102.2.
Nessie GC tool is attached as nessie-gc-0.102.2.jar, which is a standalone uber-jar file that runs on Java 11 or newer. Shell completion can be generated from the tool, check its help command. Nessie GC tool is also available as a Docker image: docker run --rm ghcr.io/projectnessie/nessie-gc:0.102.2 --help.
Nessie Server Admin tool is attached as nessie-server-admin-tool-0.102.2-runner.jar, which is a standalone uber-jar file that runs on Java 17 or newer. Shell completion can be generated from the tool, check its help command. Nessie Server Admin tool is also available as a Docker image: docker run --rm ghcr.io/projectnessie/nessie-server-admin:0.102.2 --help.
The attached nessie-helm-0.102.2.tgz is a packaged Helm chart, which can be downloaded and installed via Helm. There is also the Nessie Helm chart repo, which can be added and used to install the Nessie Helm chart.
Changelog
Fixes
- Nessie re-assigns IDs for new schemas/partition-specs/sort-orders. The check that the provided ID for
those must be valid (>= 0) is therefore superfluous, it can actually unnecessarily lead to problems. This
change also fixes an issue that the last-added schema/spec/sort ID is set to -1, if the schema/spec/sort
already existed. This lets the set-current-schema/set-default-partition-spec/set-default-sort-order
updates with-1for the last-added one fail, but it should return the ID of the schema/spec/sort ID that
already existed.
Full Changelog (minus renovate commits):
- Catalog: Allow passing -1 for new schema/partition-spec/sort-order (#10264)