Iceberg REST Federation

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

Polaris can federate an external Iceberg REST catalog (e.g., another Polaris deployment, AWS Glue, or a custom Iceberg REST implementation), enabling a Polaris service to access table and view entities managed by remote Iceberg REST Catalogs.

Runtime requirements🔗

REST endpoint: The remote service must expose the Iceberg REST specification. Configure firewalls so Polaris can reach the base URI you provide in the connection config.
Authentication: Polaris forwards requests using the credentials defined in ConnectionConfigInfo.AuthenticationParameters. OAuth2 client credentials, bearer tokens, and AWS SigV4 are supported; choose the scheme the remote service expects.

Feature configuration🔗

The catalog federation feature is disabled by default. Enable the necessary feature flag in your application.properties file (or equivalent configuration mechanism such as environment variables or a Kubernetes ConfigMap):

Hive Metastore Federation

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

Polaris can federate catalog operations to an existing Hive Metastore (HMS). This lets an external HMS remain the source of truth for table metadata while Polaris brokers access, policies, and multi-engine connectivity.

Build-time enablement🔗

The Hive factory is packaged as an optional extension and is not baked into default server builds. Include it when assembling the runtime or container images by setting the NonRESTCatalogs Gradle property to include HIVE (and any other non-REST backends you need):

Federation on Apache Polaris

Iceberg REST Federation

Runtime requirements🔗

Feature configuration🔗

Hive Metastore Federation

Build-time enablement🔗