<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Federation on Apache Polaris</title><link>https://polaris.apache.org/releases/1.9.0/federation/</link><description>Recent content in Federation on Apache Polaris</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://www.apache.org/"&gt;Copyright © 2026 The Apache Software Foundation&lt;/a&gt;.&lt;br&gt;Licensed under the &lt;a href="https://www.apache.org/licenses/LICENSE-2.0"&gt;Apache License, Version 2.0&lt;/a&gt;.</copyright><atom:link href="https://polaris.apache.org/releases/1.9.0/federation/index.xml" rel="self" type="application/rss+xml"/><item><title>Iceberg REST Federation</title><link>https://polaris.apache.org/releases/1.9.0/federation/iceberg-rest-federation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polaris.apache.org/releases/1.9.0/federation/iceberg-rest-federation/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="runtime-requirements" id="runtime-requirements"&gt;Runtime requirements&lt;a class="heading-anchor" href="#runtime-requirements" aria-label="Anchor"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;REST endpoint:&lt;/strong&gt; The remote service must expose the Iceberg REST specification. Configure
firewalls so Polaris can reach the base URI you provide in the connection config.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Authentication:&lt;/strong&gt; Polaris forwards requests using the credentials defined in
&lt;code&gt;ConnectionConfigInfo.AuthenticationParameters&lt;/code&gt;. OAuth2 client credentials, bearer tokens, GCP,
and AWS SigV4 are supported; choose the scheme the remote service expects.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="feature-configuration" id="feature-configuration"&gt;Feature configuration&lt;a class="heading-anchor" href="#feature-configuration" aria-label="Anchor"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;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):&lt;/p&gt;</description></item><item><title>Hive Metastore Federation</title><link>https://polaris.apache.org/releases/1.9.0/federation/hive-metastore-federation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polaris.apache.org/releases/1.9.0/federation/hive-metastore-federation/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="build-time-enablement" id="build-time-enablement"&gt;Build-time enablement&lt;a class="heading-anchor" href="#build-time-enablement" aria-label="Anchor"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;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 &lt;code&gt;NonRESTCatalogs&lt;/code&gt; Gradle
property to include &lt;code&gt;HIVE&lt;/code&gt; (and any other non-REST backends you need):&lt;/p&gt;</description></item><item><title>Hadoop Catalog Federation</title><link>https://polaris.apache.org/releases/1.9.0/federation/hadoop-catalog-federation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polaris.apache.org/releases/1.9.0/federation/hadoop-catalog-federation/</guid><description>&lt;p&gt;Polaris can federate catalog operations to an Iceberg
&lt;a href="https://iceberg.apache.org/docs/latest/java-api-quickstart/#using-a-hadoop-catalog"&gt;Hadoop catalog&lt;/a&gt;:
a warehouse directory in which namespaces and tables are tracked by directory layout, without a
metastore service. This lets existing file-based Iceberg tables remain where they are while Polaris
brokers access, policies, and multi-engine connectivity.&lt;/p&gt;
&lt;h2 id="build-time-enablement" id="build-time-enablement"&gt;Build-time enablement&lt;a class="heading-anchor" href="#build-time-enablement" aria-label="Anchor"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Unlike Hive and BigQuery federation, the Hadoop factory is part of the default server build:
&lt;code&gt;runtime/server/build.gradle.kts&lt;/code&gt; always includes &lt;code&gt;polaris-extensions-federation-hadoop&lt;/code&gt;, so no
Gradle property is needed. Standard Polaris binaries and container images can federate to Hadoop
catalogs as soon as the feature flags below are set.&lt;/p&gt;</description></item><item><title>BigQuery Metastore Federation</title><link>https://polaris.apache.org/releases/1.9.0/federation/bigquery-metastore-federation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polaris.apache.org/releases/1.9.0/federation/bigquery-metastore-federation/</guid><description>&lt;p&gt;Polaris can federate catalog operations to a BigQuery Metastore catalog. This lets BigQuery Metastore
remain the source of truth for Iceberg table metadata while Polaris brokers access, policies, and
multi-engine connectivity.&lt;/p&gt;
&lt;h2 id="build-time-enablement" id="build-time-enablement"&gt;Build-time enablement&lt;a class="heading-anchor" href="#build-time-enablement" aria-label="Anchor"&gt;🔗&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;The BigQuery 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 &lt;code&gt;NonRESTCatalogs&lt;/code&gt;
Gradle property to include &lt;code&gt;BIGQUERY&lt;/code&gt; (and any other non-REST backends you need):&lt;/p&gt;</description></item></channel></rss>