Project Nessie is a Transactional Catalog for Data Lakes with Git-like semantics.
Nessie supports Iceberg Tables, Delta Lake Tables and Sql Views.
More information can be found at projectnessie.org.
You can quickly get started with Nessie by using our small, fast docker image.
docker pull projectnessie/nessie
docker run -p 19120:19120 projectnessie/nessie
For trying Nessie image with different configuration options, refer to the templates under the docker module.
A local Web UI will be available at this point.
Then install the Nessie CLI tool (to learn more about CLI tool and how to use it, check Nessie CLI Documentation).
pip install pynessie
From there, you can use one of our technology integrations such those for
To learn more about all supported integrations and tools, check here
Have fun! We have a Google Group and a Slack channel we use for both developers and users. Check them out here.
By default, Nessie servers run with authentication disabled and all requests are processed under the "anonymous" user identity.
Nessie supports bearer tokens and uses OpenID Connect for validating them.
Authentication can be enabled by setting the following Quarkus properties:
nessie.server.authentication.enabled=true
quarkus.oidc.auth-server-url=<OpenID Server URL>
quarkus.oidc.client-id=<Client ID>
One can start the projectnessie/nessie
docker image in authenticated mode by setting
the properties mentioned above via docker environment variables. For example:
docker run -p 19120:19120 -e QUARKUS_OIDC_CLIENT_ID=<Client ID> -e QUARKUS_OIDC_AUTH_SERVER_URL=<OpenID Server URL> -e NESSIE_SERVER_AUTHENTICATION_ENABLED=true --network host projectnessie/nessie
- JDK 11 or higher: JDK11 or higher is needed to build Nessie (artifacts are built for Java 8)
Clone this repository and run maven:
git clone https://github.com/projectnessie/nessie
cd nessie
./mvnw clean install
Nessie required some minor changes to Delta for full support of branching and history. These changes are currently being integrated into the mainline repo. Until these have been merged we have provided custom builds in our fork which can be downloaded from a separate maven repository.
To run:
- configuration in
servers/quarkus-server/src/main/resources/application.properties
- execute
./mvnw quarkus:dev
- go to
http://localhost:19120
To run the ui (from ui
directory):
- If you are running in test ensure that
setupProxy.js
points to the correct api instance. This ensures we avoid CORS issues in testing npm install
will install dependenciesnpm run start
to start the ui in development mode via node
To deploy the ui (from ui
directory):
npm install
will install dependenciesnpm build
will minify and collect the package for deployment inbuild
- the
build
directory can be deployed to any static hosting environment or run locally asserve -s build
When running mvn clean install -Pdocker
a docker image will be created at projectnessie/nessie
which can be started
with docker run -p 19120:19120 projectnessie/nessie
and the relevant environment variables. Environment variables
are specified as per https://github.com/eclipse/microprofile-config/blob/master/spec/src/main/asciidoc/configsources.asciidoc#default-configsources
You can also deploy to AWS lambda function by following the steps in servers/lambda/README.md
The Nessie project uses the Google Java Code Style, scalafmt and pep8. See CONTRIBUTING.md for more information.