Hi all, At yesterday's catalog sync, a request was made to split the current PR into two: one for spec changes and one for code changes.
In response to this, I am canceling the current vote. Once the new spec change PR has been reviewed and approved, I will initiate a new vote thread. My apologies for the confusion. Thanks, Alex On Wed, Feb 25, 2026 at 4:42 PM Eduard Tudenhöfner <[email protected]> wrote: > > +1, thanks Alex > > On Mon, Feb 23, 2026 at 9:27 PM Dmitri Bourlatchkov <[email protected]> wrote: >> >> +1 (non-binding) >> >> Cheers, >> Dmitri. >> >> On Mon, Feb 23, 2026 at 5:33 AM Alexandre Dutra <[email protected]> wrote: >>> >>> Hi all, >>> >>> We recently agreed [1] on promoting the remote signing endpoint to the >>> main REST spec. Now that the corresponding PR [2] is approved, I would >>> like to start a formal vote to adopt the REST spec changes. >>> >>> Summary of spec-related changes in the PR: >>> >>> - The remote signing endpoint has been moved to the main REST spec >>> under the table path: >>> /v1/{prefix}/namespaces/{namespace}/tables/{table}/sign. >>> >>> - The remote signing endpoint now accepts an optional "provider" >>> parameter in the request body for future storage provider >>> disambiguation. It defaults to "s3" for backwards compatibility. >>> >>> - The old, S3-specific remote signing spec is deprecated for removal. >>> >>> Many thanks to everyone who contributed with feedback and reviews. >>> >>> Related links: >>> >>> [1]: https://lists.apache.org/thread/2kqdqb46j7jww36wwg4txv6pl2hqq9w7 >>> [2]: https://github.com/apache/iceberg/pull/15112 >>> >>> Please vote within the next 72 hours. >>> >>> [ ] +1 Adopt the promotion of the remote signing endpoint to the main REST >>> spec >>> [ ] +0 >>> [ ] -1 Do not adopt, please explain why >>> >>> Thanks, >>> Alex
