Apache Polaris 1.1.0-incubating
Released on September 19th, 2025.
Downloads🔗
| Artifact | PGP Sig | SHA-512 |
|---|---|---|
| source tar.gz | .asc | .sha512 |
| binary tgz | .asc | .sha512 |
| binary zip | .asc | .sha512 |
| Spark 3.5 with Scala 2.12 Client Jar | .asc | .sha512 |
| Spark 3.5 with Scala 2.13 Client Jar | .asc | .sha512 |
Release Notes🔗
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.secretKeyproperty has changed fromsymmetric.pemtosymmetric.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_SCHEMAto make sure version table exists:1CREATE TABLE IF NOT EXISTS version ( 2 version_key TEXT PRIMARY KEY, 3 version_value INTEGER NOT NULL 4); 5INSERT INTO version (version_key, version_value) 6 VALUES ('version', 1) 7ON CONFLICT (version_key) DO UPDATE 8 SET version_value = EXCLUDED.version_value; 9COMMENT ON TABLE version IS 'the version of the JDBC schema in use'; 10 11ALTER 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.