Deploying Polaris locally

Mon, 01 Jan 0001 00:00:00 +0000

Polaris can be deployed via a docker image or as a standalone process. Before starting, be sure that you’ve satisfied the relevant prerequisites detailed in the previous page.

Common Setup🔗

Before running Polaris, ensure you have completed the following setup steps:

Build Polaris

1cd ~/polaris
2./gradlew \
3 :polaris-server:assemble \
4 :polaris-server:quarkusAppPartsBuild --rerun \
5 :polaris-admin:assemble \
6 :polaris-admin:quarkusAppPartsBuild --rerun \
7 -Dquarkus.container-image.build=true

For standalone: Omit the -Dquarkus.container-image.tag and -Dquarkus.container-image.build options if you do not need to build a Docker image.

Running Polaris with Docker🔗

To start using Polaris in Docker and launch Polaris, which is packaged with a Postgres instance, Apache Spark, and Trino.

Accessing Storage with TLS and Self-Signed Certificates

Mon, 01 Jan 0001 00:00:00 +0000

Sometimes the storage targeted by the Polaris Server is expected to be accessed over TLS but the storage system’s certificate does not have a trust chain leading to a well-known root. Often such a certificate is simply self-signed.

In this situation the JVM inside the Polaris Server will need to be configured with a custom trust store containing the self-signed certificate or its CA certificate.

The example below assumes using a self-signed certificate for storage and docker for running Polaris.

Deploying Polaris on Apache Polaris

Deploying Polaris locally

Common Setup🔗

Running Polaris with Docker🔗

Accessing Storage with TLS and Self-Signed Certificates