- 70 commits since 0.103.2
- Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.103.3
- 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.103.3-java - PyPI: https://pypi.org/project/pynessie/ (See pynessie)
- Helm Chart repo: https://charts.projectnessie.org/
Try it
The attached nessie-quarkus-0.103.3-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.103.3/nessie-quarkus-0.103.3-runner.jar
java -jar nessie-quarkus-0.103.3-runner.jar
Nessie CLI is attached as nessie-cli-0.103.3.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.103.3.
Nessie GC tool is attached as nessie-gc-0.103.3.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.103.3 --help.
Nessie Server Admin tool is attached as nessie-server-admin-tool-0.103.3-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.103.3 --help.
The attached nessie-helm-0.103.3.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
New Features
- Introduces a hard objects-cache capacity limit to ensure that the cache does never consume more than
the configured cache-capacity plus a configurable "overshoot" (defaults to 10%). New cache entries are
admitted as long as the current cache size is less than the "cache-capacity + overshoot".
Changes
- Nessie's REST API endpoints now accept "truncated timestamps" in relative-commit-specs, aka without the
second-fraction.