Hi all, Polaris will soon be updated to Iceberg 1.12.
This release includes the new remote-signing-config field within LoadTableResult, which addresses nearly all remaining requirements for Polaris to complete its remote signing implementation, abandoned a while ago due to impending spec changes. However, one detail remains: when we added the remote-signing-config structure, refreshing the contained authentication or authorization data was intentionally left out of scope. I plan to start a separate discussion and spec change proposal with the Iceberg community regarding this shortly. Despite this, the core remote signing functionality is again viable in Polaris today, with Iceberg 1.12. The only missing piece being that auth data cannot be refreshed yet, though this capability could be added incrementally in a future update. With that in mind, I would like to ask the Polaris community: Should we resume the remote signing work where we left [1]? Or would it be preferable to wait until the specification for refreshing auth data is finalized? For additional background, you can refer to the original DISCUSS thread [2], but keep in mind that much of it is now outdated. Thanks, Alex [1]: https://github.com/apache/polaris/pull/3995 [2]: https://lists.apache.org/thread.html/xpf60ko823c7mlg5bhnddq3btvdsq5s1
