Thanks for bringing this to my attention. I’ve been debugging this issue for a few days, and here’s the related Slack thread for context: https://apache-polaris.slack.com/archives/C084XDM50CB/p1758368000877189.
First, I believe we should allow users to upgrade the Polaris version without being forced to upgrade the schema versions. Schema migrations need to be handled carefully. Naturally, some features in the new version will be limited if the schema isn’t upgraded, and older database schemas may eventually be deprecated as Polaris advances. To ensure this works, we need cross-version testing. The issue Prashant filed ( https://github.com/apache/polaris/issues/2675) is a good starting point. Second, I agree that a migration tool will be essential to make sure schema upgrades happen safely and predictably. The Admin tool seems like a natural place to start. Yufei On Wed, Sep 24, 2025 at 5:07 PM Dmitri Bourlatchkov <[email protected]> wrote: > Hi All, > > Recent issues like [2671] and [2654] indicate that users expect a > "smoother" upgrade path. > > I was thinking that it might be time to resume work on the Admin Tool and > add commands to it to perform schema upgrades. > > WDYT? > > [2671] https://github.com/apache/polaris/issues/2671 > [2654] https://github.com/apache/polaris/pull/2654 > > Thanks, > Dmitri. >
