+1 (non-binding)

On Mon, Mar 31, 2025 at 7:44 PM Renjie Liu <liurenjie2...@gmail.com> wrote:

> +1
>
> On Tue, Apr 1, 2025 at 10:33 AM Denny Lee <denny.g....@gmail.com> wrote:
>
>> +1 (non-binding)
>>
>> On Mon, Mar 31, 2025 at 7:27 PM roryqi <ror...@apache.org> wrote:
>>
>>> +1.
>>>
>>> Gang Wu <ust...@gmail.com> 于2025年4月1日周二 09:30写道:
>>>
>>>> +1 (non-binding)
>>>>
>>>> On Tue, Apr 1, 2025 at 5:15 AM Russell Spitzer <
>>>> russell.spit...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Mon, Mar 31, 2025 at 2:22 PM Amogh Jahagirdar <2am...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> Thanks Dan!
>>>>>>
>>>>>> On Mon, Mar 31, 2025 at 1:20 PM Ryan Blue <rdb...@gmail.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Mon, Mar 31, 2025 at 12:01 PM Anton Okolnychyi <
>>>>>>> aokolnyc...@gmail.com> wrote:
>>>>>>>
>>>>>>>> +1 (binding)
>>>>>>>>
>>>>>>>> - Anton
>>>>>>>>
>>>>>>>> пн, 31 бер. 2025 р. о 11:43 Daniel Weeks <dwe...@apache.org> пише:
>>>>>>>>
>>>>>>>>> Hey Everyone,
>>>>>>>>>
>>>>>>>>> I'd like to raise the proposal to make row-lineage required
>>>>>>>>> <https://github.com/apache/iceberg/pull/12580> by default to a
>>>>>>>>> vote.
>>>>>>>>>
>>>>>>>>> There was general support for this change in the discussion thread
>>>>>>>>> <https://lists.apache.org/thread/ms3t9jp628z6mlkgbtxv7q92fo8bm3nl> 
>>>>>>>>> with
>>>>>>>>> the reasoning that it would lead to broader adoption.  Notably, we 
>>>>>>>>> allow
>>>>>>>>> engines to model inserts/deletes/updates based on their own 
>>>>>>>>> semantics, but
>>>>>>>>> indicate a preference for row ids to be preserved where feasible.
>>>>>>>>>
>>>>>>>>> An open question of whether we should include a property or flag
>>>>>>>>> for writers to signal whether or not row ids are preserved was 
>>>>>>>>> raised, but
>>>>>>>>> can be handled separately from these changes.
>>>>>>>>>
>>>>>>>>> This vote will be open for at least 72 hours.
>>>>>>>>>
>>>>>>>>> [ ] +1 Make row lineage required in v3
>>>>>>>>> [ ] +0
>>>>>>>>> [ ] -1 I object to these changes because . . .
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> -Dan
>>>>>>>>>
>>>>>>>>

Reply via email to