venkateshwaracholan opened a new issue, #4600: URL: https://github.com/apache/polaris/issues/4600
### Describe the bug Summary hasOverlappingSiblings() recently exposed a JDBC-specific behavior issue fixed in #4580, but there are still no dedicated regression tests covering the JDBC persistence path for overlapping sibling detection. The current tests validate the fix indirectly, but there is no focused coverage around: JDBC materialization of persisted entities PolarisEntityUtils.asLocationBasedEntity(...) overlapping sibling detection across schema versions location normalization / comparison behavior Why this matters The original issue was specific to JDBC persistence behavior and did not reproduce uniformly across persistence implementations. Without dedicated regression tests, future refactors around: entity materialization location handling schema upgrades JDBC persistence optimizations could reintroduce the same class of issue without detection. Suggested follow-up Add focused JDBC persistence regression tests around: hasOverlappingSiblings() overlapping base locations normalized location comparisons schema-version coverage where applicable Potentially alongside the existing AtomicMetastoreManagerWithJdbcBasePersistenceImpl* test suite. Related #3378 #4580 ### 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]
