+1 on a slower deprecation path. Ideally, the feature config can be set at a catalog level instead of just a realm level. Otherwise, it requires a deployment every time someone needs to turn it on
Mike On Mon, Mar 2, 2026 at 9:03 AM Prashant Singh via dev < [email protected]> wrote: > Hey Dmitri, > Thanks for raising the discussion thread, I understand this is for backward > compatibility > Though, I would recommend keeping it on by default (with a warning that > it's going to be turned off soon), for smoother upgrades, if we choose that > path. Otherwise, older clients will break, based on my experience > Upgrading Iceberg clients is sometimes a multi-quarter effort, and i > anticipate most people will end up enabling it. > > Nevertheless, if we want we can check the older client versions; there is a > header: *X-Client-Version*: Apache Iceberg 1.9.2, that client sends, I know > not all clients are gonna send this > But this is an additional signal we have in the catalog if we want to do > something special. > > Best, > Prashant Singh > > On Mon, Mar 2, 2026 at 8:18 AM Dmitri Bourlatchkov <[email protected]> > wrote: > > > Hi All, > > > > As discussed on the Iceberg dev ML [1], adding credentials to the > ordinary > > config section in LoadTable responses appears to be required only for > > compatibility with older clients. > > > > Shall we consider making this functionality optional and not do it by > > default in Polaris? Of course, adding a feature flag to turn it back on > in > > interested deployments is implied. > > > > WDYT? > > > > [1] https://lists.apache.org/thread/33vyko8qtsmpdp75f25kx6rjrmgr5kwq > > > > Thanks, > > Dmitri. > > >
