fivetran-arunsuri commented on issue #1875: URL: https://github.com/apache/polaris/issues/1875#issuecomment-2989455928
>They are not needed any more in JDBC. It's safe to drop them. I consider its backward-compatible. @flyrain We're migrating from the EclipseLink-based version of Polaris to the new JDBC-based version. I understand that tables like entities_active, entities_change_tracking, polaris_sequence, and sequence are no longer needed and can be safely dropped. However, I had a question regarding backward compatibility — if we drop these tables and start using the new ID generation strategy with JDBC, will the new Polaris APIs still be able to query and interact with entities that were created earlier (using the old EclipseLink-based persistence and sequence ID generation)? In short, is there any risk of losing access to old entities if we drop those tables and switch entirely to JDBC? -- 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]
