Skip to content

Doc: Add breaking changes section for 1.1 release #2654

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
merged 3 commits into from
Sep 24, 2025
Merged

Doc: Add breaking changes section for 1.1 release #2654

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
822ad83
Doc: Add breaking changes section for 1.1 release
singhpk234 Sep 23, 2025
aae6783
Address review feedback
singhpk234 Sep 23, 2025
b4b69d1
Address review feedback
singhpk234 Sep 23, 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
13 changes: 13 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,19 @@ Apache Polaris 1.1.0-incubating was released on September 19th, 2025.
- **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,
Copy link
Contributor

@dimas-b dimas-b Sep 23, 2025

Choose a reason for hiding this comment

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

What's the alternative to continue using v1 schema?

Copy link
Contributor

@flyrain flyrain Sep 24, 2025

Choose a reason for hiding this comment

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

One option is to migrate to v2 schema, which requires more than just the version table. We will need to write a tool for that per offline discussion with @singhpk234

Copy link
Contributor Author

@singhpk234 singhpk234 Sep 24, 2025

Choose a reason for hiding this comment

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

Apologies, I missed responding here:
I think there a couple of scenarios, for example

  • if we simply move to v2 from v1 by adding the column in the entity table we will have to backfill the location without schema column
  • if we started with v2 schema from day 1 we should be good or any realm created with v2 column starting should good too, but in the application layer for the optimization to correctly work there is no way to check this

Bottom line being my understanding is the optimized siblling check for migrated schema version might not be reliable, i was wondering if we should capture some additional metadata in a sense that is_migrated ? default value 0 but incase the schema table exists set this value to 1, now when we do the optimized sibbling check we will just say this is not applicable if the metastore is migrated across version, though this too has shortcommings to be honest for example v2 -> v3 migration should still work, would really appreciate your thoughts

run following SQL statement under `POLARIS_SCHEMA` to make sure version table exists:
```sql
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';
```
- **Deprecations**
- The property `polaris.active-roles-provider.type` is deprecated for removal.
- The `ActiveRolesProvider` interface is deprecated for removal.
Expand Down
16 changes: 16 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 @@ -54,6 +54,22 @@ Apache Polaris 1.1.0-incubating was released on September 19th, 2025.
- 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:
```sql
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';
```

## 1.0.1
| Artifact | PGP Sig | SHA-512 |
Expand Down