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 2026/06/25 23:27:12 UTC
[DISCUSS] Single SQL DDL script
Hi All,
I'd like to propose keeping only one .sql script (per database type) in the
source tree.
I do not really see a use case for bootstrapping Polaris using its JDBC
schema version N-1 from binaries version N.
If users need an old schema, they can always bootstrap using the Admin Tool
from the old version of Polaris that contained that schema.
The benefit is easier SQL script maintenance. Plus, SQL changes will have
clear git add/remove diffs with relevant author/PR annotations.
I believe I've mentioned this in other discussions. At the same time, I
guess having a dedicated thread can help to achieve greater clarity.
Thoughts?
Thanks,
Dmitri.
Re: [DISCUSS] Single SQL DDL script
Posted by Alexandre Dutra <ad...@apache.org>.
Hi all,
Thank you for your input! Since there is consensus around the idea,
here is a PR for it:
https://github.com/apache/polaris/pull/5349
Thanks,
Alex
On Thu, Aug 20, 2026 at 1:15 PM Ayush Saxena <ay...@apache.org> wrote:
>
> +1, to this initiative
>
> This will make schema changes much easier to make and follow
>
> -Ayush
>
> On 2026/08/19 17:39:05 Yufei Gu wrote:
> > +1 on the idea. For more context, I completed one prerequisite, which
> > removes the --schema-version option from the bootstrap command in PR:
> > https://github.com/apache/polaris/pull/5044.
> >
> > Yufei
> >
> >
> > On Wed, Aug 19, 2026 at 7:38 AM Alexandre Dutra <ad...@apache.org> wrote:
> >
> > > Hi Dmitri,
> > >
> > > I missed your email but I actually agree with your suggestion.
> > >
> > > In fact, something odd happened in PR [5301] : the H2 script version
> > > had to be bumped from 5 to 6 for nothing, because the PR was fixing a
> > > bug in the PostgreSQL v5 script specifically. This obviously wouldn't
> > > have happened without versioned scripts.
> > >
> > > Thanks,
> > > Alex
> > >
> > > [5301]: https://github.com/apache/polaris/pull/5301
> > >
> > > On Fri, Jun 26, 2026 at 1:27 AM Dmitri Bourlatchkov <di...@apache.org>
> > > wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I'd like to propose keeping only one .sql script (per database type) in
> > > the
> > > > source tree.
> > > >
> > > > I do not really see a use case for bootstrapping Polaris using its JDBC
> > > > schema version N-1 from binaries version N.
> > > >
> > > > If users need an old schema, they can always bootstrap using the Admin
> > > Tool
> > > > from the old version of Polaris that contained that schema.
> > > >
> > > > The benefit is easier SQL script maintenance. Plus, SQL changes will have
> > > > clear git add/remove diffs with relevant author/PR annotations.
> > > >
> > > > I believe I've mentioned this in other discussions. At the same time, I
> > > > guess having a dedicated thread can help to achieve greater clarity.
> > > >
> > > > Thoughts?
> > > >
> > > > Thanks,
> > > > Dmitri.
> > >
> >
Re: [DISCUSS] Single SQL DDL script
Posted by Ayush Saxena <ay...@apache.org>.
+1, to this initiative
This will make schema changes much easier to make and follow
-Ayush
On 2026/08/19 17:39:05 Yufei Gu wrote:
> +1 on the idea. For more context, I completed one prerequisite, which
> removes the --schema-version option from the bootstrap command in PR:
> https://github.com/apache/polaris/pull/5044.
>
> Yufei
>
>
> On Wed, Aug 19, 2026 at 7:38 AM Alexandre Dutra <ad...@apache.org> wrote:
>
> > Hi Dmitri,
> >
> > I missed your email but I actually agree with your suggestion.
> >
> > In fact, something odd happened in PR [5301] : the H2 script version
> > had to be bumped from 5 to 6 for nothing, because the PR was fixing a
> > bug in the PostgreSQL v5 script specifically. This obviously wouldn't
> > have happened without versioned scripts.
> >
> > Thanks,
> > Alex
> >
> > [5301]: https://github.com/apache/polaris/pull/5301
> >
> > On Fri, Jun 26, 2026 at 1:27 AM Dmitri Bourlatchkov <di...@apache.org>
> > wrote:
> > >
> > > Hi All,
> > >
> > > I'd like to propose keeping only one .sql script (per database type) in
> > the
> > > source tree.
> > >
> > > I do not really see a use case for bootstrapping Polaris using its JDBC
> > > schema version N-1 from binaries version N.
> > >
> > > If users need an old schema, they can always bootstrap using the Admin
> > Tool
> > > from the old version of Polaris that contained that schema.
> > >
> > > The benefit is easier SQL script maintenance. Plus, SQL changes will have
> > > clear git add/remove diffs with relevant author/PR annotations.
> > >
> > > I believe I've mentioned this in other discussions. At the same time, I
> > > guess having a dedicated thread can help to achieve greater clarity.
> > >
> > > Thoughts?
> > >
> > > Thanks,
> > > Dmitri.
> >
>
Re: [DISCUSS] Single SQL DDL script
Posted by Yufei Gu <fl...@gmail.com>.
+1 on the idea. For more context, I completed one prerequisite, which
removes the --schema-version option from the bootstrap command in PR:
https://github.com/apache/polaris/pull/5044.
Yufei
On Wed, Aug 19, 2026 at 7:38 AM Alexandre Dutra <ad...@apache.org> wrote:
> Hi Dmitri,
>
> I missed your email but I actually agree with your suggestion.
>
> In fact, something odd happened in PR [5301] : the H2 script version
> had to be bumped from 5 to 6 for nothing, because the PR was fixing a
> bug in the PostgreSQL v5 script specifically. This obviously wouldn't
> have happened without versioned scripts.
>
> Thanks,
> Alex
>
> [5301]: https://github.com/apache/polaris/pull/5301
>
> On Fri, Jun 26, 2026 at 1:27 AM Dmitri Bourlatchkov <di...@apache.org>
> wrote:
> >
> > Hi All,
> >
> > I'd like to propose keeping only one .sql script (per database type) in
> the
> > source tree.
> >
> > I do not really see a use case for bootstrapping Polaris using its JDBC
> > schema version N-1 from binaries version N.
> >
> > If users need an old schema, they can always bootstrap using the Admin
> Tool
> > from the old version of Polaris that contained that schema.
> >
> > The benefit is easier SQL script maintenance. Plus, SQL changes will have
> > clear git add/remove diffs with relevant author/PR annotations.
> >
> > I believe I've mentioned this in other discussions. At the same time, I
> > guess having a dedicated thread can help to achieve greater clarity.
> >
> > Thoughts?
> >
> > Thanks,
> > Dmitri.
>
Re: [DISCUSS] Single SQL DDL script
Posted by Alexandre Dutra <ad...@apache.org>.
Hi Dmitri,
I missed your email but I actually agree with your suggestion.
In fact, something odd happened in PR [5301] : the H2 script version
had to be bumped from 5 to 6 for nothing, because the PR was fixing a
bug in the PostgreSQL v5 script specifically. This obviously wouldn't
have happened without versioned scripts.
Thanks,
Alex
[5301]: https://github.com/apache/polaris/pull/5301
On Fri, Jun 26, 2026 at 1:27 AM Dmitri Bourlatchkov <di...@apache.org> wrote:
>
> Hi All,
>
> I'd like to propose keeping only one .sql script (per database type) in the
> source tree.
>
> I do not really see a use case for bootstrapping Polaris using its JDBC
> schema version N-1 from binaries version N.
>
> If users need an old schema, they can always bootstrap using the Admin Tool
> from the old version of Polaris that contained that schema.
>
> The benefit is easier SQL script maintenance. Plus, SQL changes will have
> clear git add/remove diffs with relevant author/PR annotations.
>
> I believe I've mentioned this in other discussions. At the same time, I
> guess having a dedicated thread can help to achieve greater clarity.
>
> Thoughts?
>
> Thanks,
> Dmitri.