projectnessie/nessie nessie-0.106.2

Nessie 0.106.2

on GitHub

• 2 commits since 0.106.1
• Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.106.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.106.2-java
• PyPI: https://pypi.org/project/pynessie/ (See pynessie)
• Helm Chart repo: https://charts.projectnessie.org/

Try it

The attached nessie-quarkus-0.106.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.106.2/nessie-quarkus-0.106.2-runner.jar
java -jar nessie-quarkus-0.106.2-runner.jar

Nessie CLI is attached as nessie-cli-0.106.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.106.2.

Nessie GC tool is attached as nessie-gc-0.106.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.106.2 --help.

Nessie Server Admin tool is attached as nessie-server-admin-tool-0.106.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.106.2 --help.

The attached nessie-helm-0.106.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

• BigTable: the gRPC channel pool is no longer capped at a single channel by default. Deployments
  that relied on the previous (unintended) behavior and have sized their BigTable instance around
  one connection per Nessie instance may see more concurrent connections to BigTable. The previous
  behavior can be restored by setting
  nessie.version.store.persist.bigtable.initial-channel-count=1 together with
  nessie.version.store.persist.bigtable.max-channel-count=1, although this is not recommended.

New Features

• Helm chart: the BigTable gRPC channel pool settings can now be configured via the new
  bigtable.channelPool values, instead of having to go through advancedConfig.

Changes

• BigTable: unset channel pool settings are no longer taken from GAX's generic defaults, but from
  the settings tuned by the BigTable client library. The GAX defaults
  (min-rpcs-per-channel=0 and max-rpcs-per-channel=Integer.MAX_VALUE) made the channel pool
  statically sized, which prevented gax from ever resizing it and pinned it to a single channel for
  the lifetime of the client. Since gRPC starts queuing requests locally beyond 100 concurrent RPCs
  per channel, this silently capped BigTable throughput per Nessie instance and surfaced as
  DEADLINE_EXCEEDED errors under load, once the local queuing had exhausted a request's total
  timeout.

Full Changelog (minus renovate commits):

• BigTable: don't collapse the gRPC channel pool to a single channel (backport #12917) (#13065)
• Maintenance 0.106 backport (#13064)