+1 (binding)

On Wed, Aug 20, 2025 at 7:57 AM Daniel Weeks <dwe...@apache.org> wrote:

> +1 (binding)
>
> On Tue, Aug 19, 2025, 2:54 PM Marc Cenac <marc.ce...@datadoghq.com.invalid>
> wrote:
>
>> +1 (non-binding)
>>
>> On Tue, Aug 19, 2025 at 11:09 AM Fokko Driesprong <fo...@apache.org>
>> wrote:
>>
>>> +1
>>>
>>> Op di 19 aug 2025 om 18:08 schreef Steve <hongyue.apa...@gmail.com>:
>>>
>>>> +1 (non-binding)
>>>>
>>>> On Tue, Aug 19, 2025 at 8:43 AM Russell Spitzer <
>>>> russell.spit...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Tue, Aug 19, 2025 at 10:28 AM Eduard Tudenhöfner <
>>>>> etudenhoef...@apache.org> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Tue, Aug 19, 2025 at 5:23 PM Ryan Blue <rdb...@gmail.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Mon, Aug 18, 2025 at 4:50 PM huaxin gao <huaxin.ga...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1 (non-binding)
>>>>>>>>
>>>>>>>> On Mon, Aug 18, 2025 at 4:33 PM Hussein Awala <huss...@awala.fr>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1 (non-binding)
>>>>>>>>>
>>>>>>>>> On Tuesday, August 19, 2025, Steven Wu <stevenz...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> On Mon, Aug 18, 2025 at 3:35 PM Prashant Singh <
>>>>>>>>>> prashant010...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi All,
>>>>>>>>>>> I propose an update to the Rest Spec to mark 503 as
>>>>>>>>>>> non-retryable error code for the Update Table. As it can lead to 
>>>>>>>>>>> table
>>>>>>>>>>> corruption otherwise. The proposed language in the spec pr also 
>>>>>>>>>>> gives rooms
>>>>>>>>>>> for servers who still want to use 503 for retries.
>>>>>>>>>>>
>>>>>>>>>>> For details please check:
>>>>>>>>>>>
>>>>>>>>>>> PR: https://github.com/apache/iceberg/pull/13619/files
>>>>>>>>>>> Discuss Thread:
>>>>>>>>>>> https://lists.apache.org/thread/wg8m058z1jy9dss7jotx6g8h9ko1fxho
>>>>>>>>>>>
>>>>>>>>>>> Please vote in the next 72 hours:
>>>>>>>>>>>
>>>>>>>>>>> [ ] +1 Add these changes to the spec
>>>>>>>>>>> [ ] +0
>>>>>>>>>>> [ ] -1 I have questions and/or concerns
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Best,
>>>>>>>>>>> Prashant
>>>>>>>>>>>
>>>>>>>>>>

Reply via email to