fivetran-arunsuri opened a new issue, #1875: URL: https://github.com/apache/polaris/issues/1875
### Describe the bug Hey Team, We are using older version of Polaris repo with eclipse link as metastore and that is currently deployed in our production environment. I see the major breaking changes in DB schema with both the metastores with postgres as backend. Eclipse link as metastore after being bootstrapped creates following tables in the DB <img width="628" alt="Image" src="https://github.com/user-attachments/assets/9597e839-ab25-4b9a-b664-2e43733927eb"; /> When I am bootstrapping with Relational JDBC with latest incubating polaris repo, the DB schema looks like this <img width="913" alt="Image" src="https://github.com/user-attachments/assets/bb776001-3e1d-4aec-bee6-7267880f80d4"; /> I see following changes in the DB schema - Dropped tables: entities_active, entities_change_tracking, polaris_sequence, sequence - Renamed principal_secrets → principal_authentication_data - Added new table: polaris_mapping_records - Added realm_id column to existing tables - Change default schema from public to polaris_schema We would like to upgrade the Polaris to this latest with relational JDBC as we are facing issues with eclipse link as metastore. Was this change made ensuring the backward compatibility? ### To Reproduce _No response_ ### Actual Behavior _No response_ ### Expected Behavior _No response_ ### Additional context _No response_ ### System information _No response_ -- 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]
