Skip to content

Nessie (UNRELEASED/SNAPSHOT/unstable/nightly) Docs

DISCLAIMER You are viewing the docs for the next Nessie version. Docs for the latest release 0.100.2 are here.

This section contains information about an unreleased state, also known as nightly or snapshot builds. The state of the software as well as the documentation

Nessie Server unstable/nightly

The main Nessie server serves the Nessie repository using the Iceberg REST API and Nessie’s native REST API.

Docker images are multiplatform images for amd64, arm64, ppc64le, s390x.

The image tags are updated twice per day during weekdays.

Images are available from the following repositories: 

docker pull ghcr.io/projectnessie/nessie-unstable
docker run -p 19120:19120 -p 9000:9000 ghcr.io/projectnessie/nessie-unstable

docker pull quay.io/projectnessie/nessie-unstable
docker run -p 19120:19120 -p 9000:9000 quay.io/projectnessie/nessie-unstable

Nessie CLI unstable/nightly

Docker images are multiplatform images for amd64, arm64, ppc64le, s390x.

The image tags are updated twice per day during weekdays.

Images are available from the following repositories: 

docker pull ghcr.io/projectnessie/nessie-cli-unstable
docker run -it ghcr.io/projectnessie/nessie-cli-unstable

docker pull quay.io/projectnessie/nessie-cli-unstable
docker run -it quay.io/projectnessie/nessie-cli-unstable

GC Tool unstable/nightly

Nessie GC allows mark and sweep data files based on flexible expiration policies.

Docker images are multiplatform images for amd64, arm64, ppc64le, s390x.

The image tags are updated twice per day during weekdays.

Images are available from the following repositories:

docker pull ghcr.io/projectnessie/nessie-gc-unstable
docker run ghcr.io/projectnessie/nessie-gc-unstable --help

docker pull quay.io/projectnessie/nessie-gc-unstable
docker run quay.io/projectnessie/nessie-gc-unstable --help

Server Admin Tool unstable/nightly

Nessie’s Server Admin Tool allows migration (export/import) of a Nessie repository.

Docker images are multiplatform images for amd64, arm64, ppc64le, s390x.

The image tags are updated twice per day during weekdays.

They are available from the following repositories:

docker pull ghcr.io/projectnessie/nessie-server-admin-unstable
docker run ghcr.io/projectnessie/nessie-server-admin-unstable --help

docker pull quay.io/projectnessie/nessie-server-admin-unstable
docker run quay.io/projectnessie/nessie-server-admin-unstable --help

Build Nessie from source

See projectnessie/nessie GitHub for build instructions.

Nessie SNAPSHOT Maven artifacts

Snapshot artifacts are available from Sonatype. The version of the published SNAPSHOT artifacts changes with every Nessie release.

Note

Snapshot artifacts are meant for development and testing purposes only, especially when developing against Nessie. They are not meant for production use.

The currently published SNAPSHOT version can be inspected in a browser on GitHub or on the command line using the following command:

curl https://github.com/projectnessie/nessie/blob/main/version.txt

Snapshot repositories must be added to your build configuration. The following examples show how to add the repository to your build configuration:

In your Maven pom.xml add the Sonatype repository: 

  <repositories>
    <repository>
      <id>oss.sonatype.org-snapshot</id>
      <url>https://oss.sonatype.org/content/repositories/snapshots</url>
      <releases>
        <enabled>false</enabled>
      </releases>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </repository>
  </repositories>

In your Gradle project’s settings.gradle.kts add the repository: 

dependencyResolutionManagement {
  repositories {
    mavenCentral()
    maven {
      name = "Apache Snapshots"
      url = URI("https://oss.sonatype.org/content/repositories/snapshots")
      mavenContent { snapshotsOnly() }
      metadataSources {
        // Workaround for
        // https://youtrack.jetbrains.com/issue/IDEA-327421/IJ-fails-to-import-Gradle-project-with-dependency-with-classifier
        ignoreGradleMetadataRedirection()
        mavenPom()
      }
    }
  }
}

The following examples show how to add the Nessie BOM to your build configuration:

In your Maven pom.xml add the Nessie BOM as a dependency: 

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.projectnessie.nessie</groupId>
      <artifactId>nessie-bom</artifactId>
      <version>0.100.3-SNAPSHOT</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>
Then you can use all Nessie artifacts like this: 
<dependencies>
  <dependency>
    <groupId>org.projectnessie.nessie</groupId>
    <artifactId>nessie-client</artifactId>
  </dependency>
</dependencies>

In your Gradle project’s build.gradle.kts add the Nessie BOM as an enforced platform: 

dependencies {
  enforcedPlatform("org.projectnessie.nessie:nessie-bom:0.100.3-SNAPSHOT")
}
A full example using the nessie-client artifact: 
dependencies {
  enforcedPlatform("org.projectnessie.nessie:nessie-bom:0.100.3-SNAPSHOT")
  implementation("org.projectnessie.nessie:nessie-client")
}