Skip to content

Add Apache Polaris provider - #77188

Draft
XD-DENG wants to merge 1 commit into
apache:mainfrom
XD-DENG:add-apache-polaris-provider
Draft

XD-DENG wants to merge 1 commit into
apache:mainfrom
XD-DENG:add-apache-polaris-provider

Conversation

@XD-DENG

@XD-DENG XD-DENG commented Nov 17, 2026

Copy link
Copy Markdown
Member

Adds apache-airflow-providers-apache-polaris, a new community provider for Apache Polaris, the open-source catalog for Apache Iceberg.

The provider includes:

  • A polaris connection type. It supports Polaris's internal OAuth tokens, an external OIDC identity provider, or a static bearer token, and it masks every token it fetches.
  • PolarisManagementHook and PolarisCatalogHook for the Polaris Management and catalog APIs. They can also hand catalog properties to pyiceberg (optional iceberg extra) or to Spark and other engines.
  • Idempotent operators (if_exists / if_missing) for catalogs, namespaces, tables, principals, principal and catalog roles, grants, and policies.
  • A helper that turns Polaris table-maintenance policies into Iceberg Spark procedure calls.
  • How-to docs for every operator, plus example Dags as system tests.
  • A Breeze integration (breeze --integration polaris, Polaris 1.9.0) with integration tests.

Requirements: Airflow >= 3.1.1, Python >= 3.11, apache-polaris>=1.9.0. The provider starts in the incubation lifecycle stage.

Notes for reviewers:

  • apache-polaris 1.9.0, the first SDK release the provider can use, was published on 2026-11-16, inside uv's 4-day exclude-newer window. pyproject.toml carries a temporary exclude-newer-package entry for it, to be removed after 2026-11-21.
  • Polaris 1.8 and 1.9 answer 409 when one namespace-properties request both sets and removes keys, so the hook sends updates and removals as separate requests.
  • This PR stays a draft while the [DISCUSS] thread for the new provider runs on the dev list.

Checks run locally:

  • prek run --from-ref main --stage pre-commit passes. check-provider-yaml-valid was skipped because it needs the Breeze CI image.
  • Provider unit tests: 376 passed.
  • mypy on the provider's source and tests: no issues.
  • Integration tests against Polaris 1.9.0: 18 passed. The 3 example Dags (system tests) passed against the same server.
  • Breeze tests for selective checks and test types: passed.
  • Not run locally: the docs build with spellcheck, and the Breeze-image checks.

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 5.5)

Generated-by: Claude Code (Opus 5.5) following the guidelines


🤖 Generated with Claude Code

https://claude.ai/code/session_01KCYvgMVjToFjwMVF4nrawu

Apache Polaris is an open-source catalog for Apache Iceberg. Managing it from
Airflow has so far meant hand-written REST calls or shelling out to its CLI.
This provider gives Dags a `polaris` connection type, hooks for the Polaris
Management and catalog APIs, idempotent operators for catalogs, namespaces,
tables, principals, roles, grants and policies, and a helper that turns
table-maintenance policies into Iceberg Spark procedure calls.

It builds on the official apache-polaris SDK. Release 1.9.0 is the first one
the provider can use, and it was published inside uv's 4-day exclude-newer
window, so the lock carries a temporary exclude-newer-package entry for it.
Integration tests run against Polaris through a new Breeze integration.

Co-authored-by: Yufei Gu <yufei@apache.org>
Co-authored-by: Yong Zheng <29619290+MonkeyCanCode@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant