Nessie 0.76.2
·
2087 commits
to main
since this release
Nessie 0.76.2 release
- 10 commits since 0.76.1
- Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.76.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.76.2-java - PyPI: https://pypi.org/project/pynessie/ (See pynessie)
- Helm Chart repo: https://charts.projectnessie.org/
Try it
The attached nessie-quarkus-0.76.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.76.2/nessie-quarkus-0.76.2-runner.jar
java -jar nessie-quarkus-0.76.2-runner.jar
Nessie GC tool is attached as nessie-gc-0.76.2, which is an executable.
(chmod 744 nessie-gc-0.76.2 after download.)
Can also be run using java -jar nessie-gc-0.76.2, because it is actually a Java archive.
Shell completion can be generated from the nessie-gc tool.
The attached nessie-helm-0.76.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
Highlights
- The Nessie client supports two new authentication flows when using OAuth 2 authentication:
the Authorization Code flow and the Device Code flow. These flows are well suited for use within
a command line program, such as a Spark SQL shell, where a user is interacting with Nessie using a
terminal. In these flows, the user must use their web browser to authenticate with the identity
provider. See the
Nessie documentation
for details. The two new flows are enabled by the following new grant types:authorization_code: enables the Authorization Code flow; this flow can only be used with
a local shell session running on the user's machine.device_code: enables the Device Code flow; this flow can be used with either a local or a
remote shell session.
- The Nessie client now supports endpoint discovery when using OAuth 2 authentication. If an
identity provider supports the OpenID Connect Discovery mechanism, the Nessie client can be
configured to use it to discover the OAuth 2 endpoints. See the
Nessie documentation
for details.
New Features
- Nessie client: the OAUTH2 authentication provider now supports programmatic configuration. See the
Nessie documentation for details.
Fixes
- Fix potential NPE when fetching commit log with fetch option
ALLand access checks enabled.