Skip to content

Prep: Site for 1.2 release #2877

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
singhpk234 merged 5 commits into from
Oct 27, 2025
Merged

Prep: Site for 1.2 release #2877

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
de857f0
update site
singhpk234 Oct 23, 2025
7557580
address review feedback
singhpk234 Oct 23, 2025
3cc1d34
Add extra line
singhpk234 Oct 23, 2025
bbc7f81
mark event persistence as preview
singhpk234 Oct 27, 2025
8dd8fbb
remove request-id
singhpk234 Oct 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions site/content/downloads/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,46 @@ params:
## Helm Chart
Repo: https://downloads.apache.org/incubator/polaris/helm-chart

## 1.2.0
| Artifact | PGP Sig | SHA-512 |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [source tar.gz](https://dlcdn.apache.org/incubator/polaris/1.2.0-incubating/apache-polaris-1.2.0-incubating.tar.gz) | [.asc](https://downloads.apache.org/incubator/polaris/1.2.0-incubating/apache-polaris-1.2.0-incubating.tar.gz.asc) | [.sha512](https://downloads.apache.org/incubator/polaris/1.2.0-incubating/apache-polaris-1.2.0-incubating.tar.gz.sha512) |
| [binary tgz](https://dlcdn.apache.org/incubator/polaris/1.2.0-incubating/polaris-bin-1.2.0-incubating.tgz) | [.asc](https://downloads.apache.org/incubator/polaris/1.2.0-incubating/polaris-bin-1.2.0-incubating.tgz.asc) | [.sha512](https://downloads.apache.org/incubator/polaris/1.2.0-incubating/polaris-bin-1.2.0-incubating.tgz.sha512) |
| [binary zip](https://dlcdn.apache.org/incubator/polaris/1.2.0-incubating/polaris-bin-1.2.0-incubating.zip) | [.asc](https://downloads.apache.org/incubator/polaris/1.2.0-incubating/polaris-bin-1.2.0-incubating.zip.asc) | [.sha512](https://downloads.apache.org/incubator/polaris/1.2.0-incubating/polaris-bin-1.2.0-incubating.zip.sha512) |
| [Spark 3.5 with Scala 2.12 Client Jar](https://repo1.maven.org/maven2/org/apache/polaris/polaris-spark-3.5_2.12/1.2.0-incubating/polaris-spark-3.5_2.12-1.2.0-incubating-bundle.jar) | [.asc](https://repo1.maven.org/maven2/org/apache/polaris/polaris-spark-3.5_2.12/1.2.0-incubating/polaris-spark-3.5_2.12-1.2.0-incubating-bundle.jar.asc) | [.sha512](https://repo1.maven.org/maven2/org/apache/polaris/polaris-spark-3.5_2.12/1.2.0-incubating/polaris-spark-3.5_2.12-1.2.0-incubating-bundle.jar.sha512) |
| [Spark 3.5 with Scala 2.13 Client Jar](https://repo1.maven.org/maven2/org/apache/polaris/polaris-spark-3.5_2.13/1.2.0-incubating/polaris-spark-3.5_2.13-1.2.0-incubating-bundle.jar) | [.asc](https://repo1.maven.org/maven2/org/apache/polaris/polaris-spark-3.5_2.13/1.2.0-incubating/polaris-spark-3.5_2.13-1.2.0-incubating-bundle.jar.asc) | [.sha512](https://repo1.maven.org/maven2/org/apache/polaris/polaris-spark-3.5_2.13/1.2.0-incubating/polaris-spark-3.5_2.13-1.2.0-incubating-bundle.jar.sha512) |
Apache Polaris 1.2.0-incubating was released on October 23rd, 2025.
Comment thread
singhpk234 marked this conversation as resolved.
- **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.
- Added AWS CloudWatch Event Sink Implementation

@dimas-b dimas-b Oct 23, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to flag this as "beta"? If so, I think we can do that without re-releasing 1.2.0.

I do not recall if we discussed this before, so apologies for rocking the boat. Cf. https://lists.apache.org/thread/yx7pkgczl6k7bt4k4yzqrrq9gn7gqk2p

@singhpk234 singhpk234 Oct 23, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can update the release notes in the website if we have concencus ? (post this pr as well, wdyt ?) we did that for 1.1 release

why do we wanna call it as beta though ? is it the interface gonna change or something ?

@flyrain flyrain Oct 23, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @dimas-b, could you elaborate the reason here? I'm not sure I understanding the reason behind beta label and re-releasing?

@dimas-b dimas-b Oct 23, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason for "beta" is in the ML thread (linked above)... TL;DR: possible changes to binary / JSON representation.

@dimas-b dimas-b Oct 23, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're ok flagging persisted events as "beta" we could do this in the docs / release notes on the site, I think.

@adutra adutra Oct 24, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also support flagging events as beta.

For a few reasons:

  • The API is still evolving, see this ML thread: https://lists.apache.org/thread/rl5cpcft16sn5n00mfkmx9ldn3gsqtfy
  • As the ML thread linked above shows, the SQL schema of the events table could evolve and require SQL migration.
  • Existing listeners are both incomplete:
    • JDBC: only processes after-create-table, after-create-catalog events, other events are ignored.
    • CloudWatch: only processes after-refresh-table events, other events are ignored.

As I already suggested a few times, a complete, general-purpose, production-ready event listener must either process all events equally, or expose a configuration option to select which events to process or ignore. See #2630 and #2836 (comment) for more discussions on this specific topic.

For all the above reasons, I think it would be nicer for our users to mark the events feature as beta/experimental, so that they don't accidentally rely on it prematurely in production-critical deployments.

@dimas-b dimas-b Oct 24, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another point for "beta": the current Polaris Evolution doc has stronger guarantees for persisted data than for java interfaces.

If events only had a java representation, it would be not necessary to flag them as "beta" now. However, given that events are persisted and their representation in the Polaris database is very likely to change per dev ML discussions, I think we ought to warn uses about foreseeable upgrade issues in this area with the help of the "beta" label (plus some brief explanation of the issue).

CC: @jbonofre : related to you comment in the main thread.

@dimas-b dimas-b Oct 27, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dev ML discussion: https://lists.apache.org/thread/xogjyozb7qqj5jjs330f5s6lw69ldptv

- Generate Request IDs (if not specified) for all incoming requests to Polaris.

@dimas-b dimas-b Oct 27, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatic ID generation is removed by #2914 (assuming it gets merged).

I believe we should mention this as a "preview" too, and make a note that is may be removed in the next release.

@dimas-b dimas-b Oct 27, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would not mind removing the Generate Request IDs point from the list of features completely. Per email discussion linked from #2914 it was not really intended to be a user-level feature.

@singhpk234 singhpk234 Oct 27, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thats make sense, i think the general concecus as per linked is to use Quarkus OTEL ! I removed the auto request id generation


- **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
| Artifact | PGP Sig | SHA-512 |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|---|
Expand Down
12 changes: 8 additions & 4 deletions site/hugo.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,22 +104,26 @@ menu:
url: "/in-dev/unreleased/"
parent: "releases"
weight: 10
- name: "1.2.0"
url: "/releases/1.2.0/"
parent: "releases"
weight: 20
- name: "1.1.0"
url: "/releases/1.1.0/"
parent: "releases"
weight: 20
weight: 30
- name: "1.0.1"
url: "/releases/1.0.1/"
parent: "releases"
weight: 30
weight: 40
- name: "1.0.0"
url: "/releases/1.0.0/"
parent: "releases"
weight: 40
weight: 50
- name: "0.9.0"
url: "/releases/0.9.0/"
parent: "releases"
weight: 50
weight: 60
Comment thread
singhpk234 marked this conversation as resolved.
Outdated

- name: "Downloads"
identifier: "downloads"
Expand Down