Helm Chart

Repo: https://downloads.apache.org/incubator/polaris/helm-chart

1.2.0

Apache Polaris 1.2.0-incubating was released on October 23rd, 2025.

• Upgrade Notes

  • Amazon RDS plugin enabled, this allows polaris to connect to AWS Aurora PostgreSQL using IAM authentication.

• Breaking changes

  • Creating or altering a namespace with a custom location outside its parent location is now prohibited by default. To restore the old behavior, set the ALLOW_NAMESPACE_CUSTOM_LOCATION flag to true.

• New Features

  • Added a finer grained authorization model for UpdateTable requests. Existing privileges continue to work for granting UpdateTable, such as TABLE_WRITE_PROPERTIES. However, you can now instead grant privileges just for specific operations, such as TABLE_ADD_SNAPSHOT

  • Added a Management API endpoint to reset principal credentials, controlled by the ENABLE_CREDENTIAL_RESET (default: true) feature flag.

  • The ENABLE_SUB_CATALOG_RBAC_FOR_FEDERATED_CATALOGS was added to support sub-catalog (initially namespace and table) RBAC for federated catalogs. The setting can be configured on a per-catalog basis by setting the catalog property: polaris.config.enable-sub-catalog-rbac-for-federated-catalogs. The realm-level feature flag ALLOW_SETTING_SUB_CATALOG_RBAC_FOR_FEDERATED_CATALOGS (default: true) controls whether this functionality can be enabled or modified at the catalog level.

  • Added support for S3-compatible storage that does not have STS (use stsUavailable: true in catalog storage configuration)

  • Added a Management API endpoint to reset principal credentials, controlled by the ENABLE_CREDENTIAL_RESET (default: true) feature flag.

  • Events Persistence (Preview): Introduced new event types and added support for persisting events to both Relational JDBC Persistence and AWS CloudWatch.

    Note: This is a preview feature. The persistence schema is subject to change in future releases, and previously stored event data MAY become unreadable (i.e., dropped) after an upgrade.

• Changes

  • The following APIs will now return the newly-created objects as part of the successful 201 response: createCatalog, createPrincipalRole, createCatalogRole.

• Deprecations

  • The property polaris.active-roles-provider.type is deprecated and has no effect anymore.
  • The EclipseLink Persistence implementation has been deprecated since 1.0.0 and will be completely removed in 1.3.0 or in 2.0.0 (whichever happens earlier).
  • The legacy management endpoints at /metrics and /healthcheck have been deprecated in 1.2.0 and will be completely removed in 1.3.0 or in 2.0.0 (whichever happens earlier). Please use the standard management endpoints at /q/metrics and /q/health instead.

1.1.0

Apache Polaris 1.1.0-incubating was released on September 19th, 2025.

• New features & enhancements
  • HMS support
  • IMPLICIT authentication type
  • Support for non-AWS S3 compatible storage with STS: MinIO, s3a scheme support
  • Use of Realm instead of RealmId
  • Modularized Federation Architecture
  • Federated Catalog Support in Polaris CLI
  • Expanded External Identity Provider support
  • Python package (official)
  • Documentation improvements (release process, multi-realms configuration)
• Bug fixes
  • Fix drop view with default server configuration
  • Fix MinIO support
  • Remove ThreadLocal
• Breaking changes
  • Helm chart: the default value of the authentication.tokenBroker.secret.symmetricKey.secretKey property has changed from symmetric.pem to symmetric.key.
  • For migrations from 1.0.x to 1.1.x, users using JDBC persistence and wanting to continue using v1 schema, must ensure that they, run following SQL statement under POLARIS_SCHEMA to make sure version table exists:

    CREATE TABLE IF NOT EXISTS version (
       version_key TEXT PRIMARY KEY,
       version_value INTEGER NOT NULL
    );
    INSERT INTO version (version_key, version_value)
      VALUES ('version', 1)
    ON CONFLICT (version_key) DO UPDATE
                            SET version_value = EXCLUDED.version_value;
    COMMENT ON TABLE version IS 'the version of the JDBC schema in use';
    
    ALTER TABLE polaris_schema.entities ADD COLUMN IF NOT EXISTS location_without_scheme TEXT;
    

    • Please don’t enable OPTIMIZED_SIBLING_CHECK feature configuration, once the above SQL statements are run. As it may lead to incorrect behavior, due to missing data for location_without_scheme column.

1.0.1

Apache Polaris 1.0.1-incubating was released on August 16th, 2025. It’s a maintenance release on the 1.0.0 release fixing a couple of issues on the Helm Chart:

• remove db-kind in Helm Chart
• add relational-jdbc to helm

1.0.0

Apache Polaris 1.0.0-incubating was released on July 9th, 2025.

• Highlights
  • First release ready for real-world workloads after the public beta 0.9.0
  • Binary distribution – first release with single downloadable .tgz or .zip artifact.
  • Helm Chart – debut of an official Helm chart for seamless Kubernetes deployment
• New features & enhancements
  • Policy Store — persistence with schema evolution, built‑in TMS policies (Data compaction, Snapshot expiry, etc) and REST CRUD endpoints
  • Postgres JDBC persistence — native JDBC backend with robust support for concurrent changes.
  • Rollback Compaction on Conflicts - makes Polaris smarter, to revert the compaction commits in case of crunch to let the writers who are actually adding or removing the data to the table succeed. In a sense treating compaction as always a lower priority process.
  • Enhanced runtime — new runtime powered by Quarkus delivers out‑of‑the‑box Kubernetes readiness, quick startup, OIDC integration, and many other benefits. Polaris server and admin tool are now using Quarkus as a runtime framework.
  • HTTP caching via ETag — the loadTable endpoint supports ETag, reducing bandwidth and improving perceived latency
  • Support for external identity providers (IdP) — Polaris can now be its own IdP, delegate to an external IdP, or both
  • Snapshot filtering – clients can choose to load only referenced snapshots
  • Catalog Federation (experimental) – federate requests to an external Iceberg REST or Hadoop Catalog
  • Generic Tables (experimental) — serve multiple table formats besides Iceberg tables; initial Spark 3.5 plugin supports Delta Lake
  • Event Listener framework (experimental) — subscribe to catalog events (AfterTableCommitedEvent, BeforeViewCommitedEvent, etc)
• Notable bug fixes
  • CLI and Python Client improvements – Support for new features, CLI repair, changes to the update subcommand, and various fixes
  • Safe configurations – Catalog-level Polaris configurations follow a strict naming convention to avoid name clashes with user-provided configuration entries. Legacy Polaris configuration names are still supported in 1.0 to allow existing deployments to migrate without rush.
  • TableOperations optimizations – Changes to BasePolarisTableOperations result in less traffic to object storage during commits
  • Bounded entity cache – The entity cache is now more memory-aware and less likely to lead to OOMs
  • Bootstrapping fixes – Users can more easily bootstrap a new realm. Root credentials can be provided by the user or generated by Polaris (and returned to the user).
• Breaking changes
  • Server Configuration – The format used to configure the Polaris service in 0.9 has changed with the migration to Quarkus and changes to configurations
  • Bootstrap Flow – The bootstrap flow used in 0.9 has changed with the migration to Quarkus and the new admin tool

0.9.0

Apache Polaris 0.9.0 was released on March 11, 2025 as the first Polaris release. Only the source distribution is available for this release.