flyrain commented on issue #1875: URL: https://github.com/apache/polaris/issues/1875#issuecomment-2964661534
> Dropped tables: entities_active, entities_change_tracking, polaris_sequence, sequence They are not needed any more in JDBC. It's safe to drop them. I consider its backward-compatible. > Renamed principal_secrets → principal_authentication_data Renaming is a safe operation, which is also backward-compatible. > Added new table: polaris_mapping_records Used by policy store. It's safe to add it. > Added realm_id column to existing tables We will need to backfill the field realm_id for every row. > Change default schema from public to polaris_schema Renaming a Postgres schema should be fine in terms of compatibilies. In conclusion, the only not compatible place should be the new field `realm_id`. cc @singhpk234 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
