+1 (non-binding). On Wed, Apr 30, 2025 at 3:49 PM Daniel Weeks <dwe...@apache.org> wrote:
> +1 (binding) > > On Wed, Apr 30, 2025 at 1:38 PM Amogh Jahagirdar <2am...@gmail.com> wrote: > >> +1 (binding) >> >> On Wed, Apr 30, 2025 at 1:29 PM Anurag Mantripragada >> <amantriprag...@apple.com.invalid> wrote: >> >>> +1 (non-binding) >>> >>> ~ Anurag Mantripragada >>> >>> >>> >>> >>> >>> >>> >>> On Apr 30, 2025, at 11:44 AM, Ryan Blue <rdb...@gmail.com> wrote: >>> >>> +1 (binding) >>> >>> On Wed, Apr 30, 2025 at 10:34 AM Huang-Hsiang Cheng >>> <hua...@apple.com.invalid> wrote: >>> >>>> +1 (non-binding) >>>> >>>> Huang-Hsiang >>>> >>>> On Apr 30, 2025, at 10:06 AM, Yufei Gu <flyrain...@gmail.com> wrote: >>>> >>>> +1 >>>> Yufei >>>> >>>> >>>> On Wed, Apr 30, 2025 at 10:04 AM Russell Spitzer < >>>> russell.spit...@gmail.com> wrote: >>>> >>>>> +1 >>>>> >>>>> On Wed, Apr 30, 2025 at 11:36 AM Szehon Ho <szehon.apa...@gmail.com> >>>>> wrote: >>>>> >>>>>> +1 >>>>>> >>>>>> Thanks >>>>>> Szehon >>>>>> >>>>>> On Wed, Apr 30, 2025 at 4:10 AM Eduard Tudenhöfner < >>>>>> etudenhoef...@apache.org> wrote: >>>>>> >>>>>>> +1 (binding) >>>>>>> >>>>>>> On Tue, Apr 29, 2025 at 9:29 PM Ryan Blue <rdb...@gmail.com> wrote: >>>>>>> >>>>>>>> Hi everyone, >>>>>>>> >>>>>>>> I’d like to propose merging PR 12162 >>>>>>>> <https://github.com/apache/iceberg/pull/12162/files> into the >>>>>>>> table spec for v3. The changes are a minimal set of additions needed to >>>>>>>> support table encryption schemes, including the scheme that we’re >>>>>>>> working >>>>>>>> on for table encryption with client-managed keys that will be a >>>>>>>> separate >>>>>>>> doc. >>>>>>>> >>>>>>>> There are two main changes: >>>>>>>> >>>>>>>> - Add a table of encryption-keys that stores encrypted keys >>>>>>>> - Add a key-id to snapshot metadata that identifies the key >>>>>>>> used to encrypt the snapshot >>>>>>>> >>>>>>>> These are the only changes needed for v3, which we want to keep >>>>>>>> separate from the encryption scheme. The table format is responsible >>>>>>>> for >>>>>>>> storing the encrypted key material and the key used for a snapshot. >>>>>>>> These >>>>>>>> changes are compatible with REST catalogs as well as older catalogs >>>>>>>> like >>>>>>>> Hive that manage the metadata JSON location. >>>>>>>> >>>>>>>> Please take a look and vote in the next 72 hours. >>>>>>>> >>>>>>>> [ ] +1 Add these changes to the spec >>>>>>>> [ ] +0 >>>>>>>> [ ] -1 I have questions and/or concerns >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Ryan >>>>>>>> >>>>>>> >>>> >>>
