snazy commented on issue #450: URL: https://github.com/apache/polaris/issues/450#issuecomment-2482307170
Honestly, I don't think that reverting is an option. Cross-version tests (or backwards/forwards/migration compatibility tests) are a good idea! SQL schema migration however complicates things, especially in a distributed / horizontally scalable system w/ rolling upgrades. Re cross-version tests (backwards/forwards compatibility + rolling upgrades), we do have something like that in Nessie, where we run REST services from older releases and test the newest client (on `main`) against it, and older clients against the newest REST service (on `main`). It requires quite a bit of class-loading trickery though. With Iceberg/Java (which we don't use in those tests in Nessie) it would be quite hard, because Iceberg/Java and especially the Azure SDK keep resources like threads and thread-locals around, which cause class leaks that then cause OOMs - not great. However, testing relevant things (persistence is one) in isolation should be doable - as dedicated / isolated tests. -- 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]
