You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Dmitri Bourlatchkov <di...@apache.org> on 2025/09/25 14:10:56 UTC

[DISCUSS] Fixing JDBC upgrades in a parch release (ASAP)

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.

Re: [DISCUSS] Fixing JDBC upgrades in a parch release (ASAP)

Posted by Yufei Gu <fl...@gmail.com>.
Given the breaking change in 1.1.0, I think it’s reasonable to keep the
door open for a 1.1.1 release. We haven’t released 1.2.0 yet, and we don’t
know when it will land or whether it will introduce new issues. A patched
1.1.x line still gives users the flexibility to adopt new features without
jumping to 1.2.0 immediately.
The only scenario where we could safely skip 1.1.1 is if 1.2.0 ships very
soon, proves stable, and allows us to deprecate 1.1.0 quickly.

Yufei


On Fri, Sep 26, 2025 at 11:10 AM Dmitri Bourlatchkov <di...@apache.org>
wrote:

> Stepping back on 1.1.1 a bit... We're almost ready to release 1.2.0, so it
> might be preferable to release JDBC fixes in 1.2.0 so as not to waste
> effort on making a patch release immediately followed by a "better" minor
> release.
>
> Cheers,
> Dmitri.
>
> On 2025/09/25 22:23:45 Prashant Singh wrote:
> > +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 <di...@apache.org>
> > 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.
> > >
> >
>

Re: [DISCUSS] Fixing JDBC upgrades in a parch release (ASAP)

Posted by Dmitri Bourlatchkov <di...@apache.org>.
Stepping back on 1.1.1 a bit... We're almost ready to release 1.2.0, so it might be preferable to release JDBC fixes in 1.2.0 so as not to waste effort on making a patch release immediately followed by a "better" minor release.

Cheers,
Dmitri.

On 2025/09/25 22:23:45 Prashant Singh wrote:
> +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 <di...@apache.org>
> 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.
> >
>

Re: [DISCUSS] Fixing JDBC upgrades in a parch release (ASAP)

Posted by Prashant Singh <pr...@gmail.com>.
+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 <di...@apache.org>
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.
>