+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 <[email protected]> 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 <[email protected]> > 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. >
