rishii-19-works commented on issue #3378: URL: https://github.com/apache/polaris/issues/3378#issuecomment-3721980319
Thank you for reporting this. I can reproduce the failure when both ALLOW_OPTIMIZED_SIBLING_CHECK=true and OPTIMIZED_SIBLING_CHECK=true are enabled with JDBC persistence. The ClassCastException originates from JdbcBasePersistenceImpl.hasOverlappingSiblings, where a PolarisBaseEntity is being cast to LocationBasedEntity. This suggests the optimized sibling check assumes entity types that are not guaranteed for the JDBC backend. It may be worth adding a type-safe check or providing a fallback path for JDBC persistence when the optimized sibling check is enabled. If this approach looks reasonable, I’d be happy to work on a fix and submit a PR. -- 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]
