+1 on having 1.1.1 release done. I was chatting with Yufei also with this, IMHO considering the there can be hybrid cases where some realms are bootstrapped with v1 and another with v2 (as we just do create table if exists so essentially its a no-op) we can do the following : 1. From the ModelEntity remove the newly added column `location_without_scheme` so that we don't project it and already bootstrapped realms with v1 works 2. make v 1.1.1 the default schema version as 1 (even when no schema table exists) 3. Add prod readiness check that Overlapping check should not be enabled
Please let me know your thoughts Best, Prashant Singh On Thu, Sep 25, 2025 at 7:11 AM Dmitri Bourlatchkov <[email protected]> wrote: > Hi All, > > Upgrade issues in 1.1.0 with JDBC persistence [1] apparently break our > previously established guarantees [2]. Users should be able to perform > rolling upgrades, but apparently they cannot. > > I think it would be good to fix that and release it immediately as 1.1.1. > > WDYT? > > [1] https://github.com/apache/polaris/issues/2671 > [2] > > https://polaris.apache.org/in-dev/unreleased/evolution/#managing-polaris-database > > Thanks, > Dmitri. >
