You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+40-4Lines changed: 40 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,9 +41,9 @@ request adding CHANGELOG notes for breaking (!) changes and possibly other secti
41
41
42
42
-**MinIO**: Added MinIO integration support with comprehensive getting started documentation.
43
43
44
-
### Upgrade notes
44
+
### Upgrade Notes
45
45
46
-
### Breaking changes
46
+
### Breaking Changes
47
47
48
48
- Helm chart: the default value of the `authentication.tokenBroker.secret.symmetricKey.secretKey` property has changed
49
49
from `symmetric.pem` to `symmetric.key`.
@@ -105,9 +105,45 @@ refresh-credentials flag for the desired storage provider.
105
105
106
106
### Commits
107
107
108
-
## [1.0.0-incubating]
108
+
## [1.0.1-incubating]
109
+
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:
110
+
- remove db-kind in Helm Chart
111
+
- add relational-jdbc to helm
112
+
109
113
110
-
- TODO: backfill 1.0.0 release notes
114
+
## [1.0.0-incubating]
115
+
Apache Polaris 1.0.0-incubating was released on July 9th, 2025.
116
+
117
+
-**Highlights**
118
+
- First release ready for real-world workloads after the public beta 0.9.0
119
+
-**Binary distribution** – first release with single downloadable .tgz or .zip artifact.
120
+
-**Helm Chart** – debut of an official Helm chart for seamless Kubernetes deployment
121
+
-**New features & enhancements**
122
+
-**Policy Store** — persistence with schema evolution, built‑in TMS policies (Data compaction, Snapshot expiry, etc) and REST CRUD endpoints
123
+
-**Postgres JDBC persistence** — native JDBC backend with robust support for concurrent changes.
124
+
-**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.
125
+
-**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.
126
+
-**HTTP caching via ETag** — the loadTable endpoint supports ETag, reducing bandwidth and improving perceived latency
127
+
-**Support for external identity providers (IdP)** — Polaris can now be its own IdP, delegate to an external IdP, or both
128
+
-**Snapshot filtering** – clients can choose to load only referenced snapshots
129
+
-**Catalog Federation (experimental)** – federate requests to an external Iceberg REST or Hadoop Catalog
-**CLI and Python Client improvements** – Support for new features, CLI repair, changes to the update subcommand, and various fixes
134
+
-**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.
135
+
-**TableOperations optimizations** – Changes to BasePolarisTableOperations result in less traffic to object storage during commits
136
+
-**Bounded entity cache** – The entity cache is now more memory-aware and less likely to lead to OOMs
137
+
-**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).
138
+
-**Breaking changes**
139
+
-**Server Configuration** – The format used to configure the Polaris service in 0.9 has changed with the migration to Quarkus and changes to configurations
140
+
-**Bootstrap Flow** – The bootstrap flow used in 0.9 has changed with the migration to Quarkus and the new admin tool
141
+
142
+
143
+
## [0.9.0-incubating]
144
+
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.
enabling seamless multi-engine interoperability across a wide range of platforms, including Apache Doris™, Apache Flink®,
25
-
Apache Spark™, StarRocks, and Trino.
25
+
Apache Spark™, Dremio® OSS, StarRocks, and Trino.
26
26
27
27
Documentation is available at https://polaris.apache.org. The REST OpenAPI specifications are available here:
28
28
[Polaris management API doc](https://editor-next.swagger.io/?url=https://raw.githubusercontent.com/apache/polaris/refs/heads/main/spec/polaris-management-service.yml)
@@ -42,11 +42,11 @@ Click [here](https://polaris.apache.org/in-dev/unreleased/) for a quick overview
42
42
## Quickstart
43
43
Click [here](https://polaris.apache.org/in-dev/unreleased/getting-started/install-dependencies/) for the quickstart experience, which will help you set up a Polaris instance locally or on any supported cloud provider.
44
44
45
-
## Building and Running
45
+
## Project Structure
46
46
47
47
Apache Polaris is organized into the following modules:
48
48
49
-
-`polaris-core` - The main Polaris entity definitions and core business logic
49
+
-[`polaris-core`](./polaris-core/README.md) - The main Polaris entity definitions and core business logic
50
50
- API modules (implementing the Iceberg REST API and Polaris management API):
51
51
-`polaris-api-management-model` - The Polaris management model
52
52
-`polaris-api-management-service` - The Polaris management service
@@ -59,13 +59,15 @@ Apache Polaris is organized into the following modules:
59
59
- Persistence modules:
60
60
-`polaris-eclipselink` - The Eclipselink implementation of the MetaStoreManager interface
61
61
-`polaris-relational-jdbc` - The JDBC implementation of BasePersistence to be used via AtomicMetaStoreManager
62
-
62
+
63
+
## Building and Running
64
+
63
65
Apache Polaris is built using Gradle with Java 21+ and Docker 27+.
64
66
65
67
-`./gradlew build` - To build and run tests. Make sure Docker is running, as the integration tests depend on it.
66
68
-`./gradlew assemble` - To skip tests.
67
69
-`./gradlew check` - To run all checks, including unit tests and integration tests.
68
-
-`./gradlew run` - To run the Polaris server locally; the server is reachable at localhost:8181. This is also suitable for running regression tests, or for connecting with Spark. Set your own credentials by specifying system property `./gradlew run -Dpolaris.bootstrap.credentials=POLARIS,root,s3cr3t` where:
70
+
-`./gradlew run` - To run the Polaris server locally; the server is reachable at localhost:8181. This is also suitable for running regression tests, or for connecting with Spark. Set your own credentials by specifying system property `./gradlew run -Dpolaris.bootstrap.credentials=POLARIS,root,secret` where:
69
71
-`POLARIS` is the realm
70
72
-`root` is the CLIENT_ID
71
73
-`secret` is the CLIENT_SECRET
@@ -136,6 +138,19 @@ Default configuration values can be found in `runtime/defaults/src/main/resource
136
138
```
137
139
- See [README in `site/`](site/README.md) for more information.
138
140
141
+
#### Publishing Build Scans to develocity.apache.org
142
+
143
+
All authenticated builds of Apache Polaris will automatically publish build scans to the ASF Develocity instance at
0 commit comments