You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iceberg.apache.org by Steven Wu <st...@gmail.com> on 2026/10/07 18:22:31 UTC
[VOTE] Require monotonically increasing snapshot timestamps in v4
Hi,
I propose requiring each new snapshot in a v4 table to have a
timestamp-ms strictly
greater than its parent snapshot’s timestamp on the same branch. Root
snapshots are unconstrained, and v1–v3 behavior remains unchanged.
This ensures snapshot timestamps align with snapshot order. This change
would resolve time travel issues caused by out-of-order snapshot
timestamps. This can also enable a row timestamp metadata column inherited
from the snapshot timestamp (a separate follow-up v4 spec change).
Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
Reference implementation: #16293
<https://github.com/apache/iceberg/pull/16293>
Please vote in the next 72 hours:
[ ] +1 Adopt the requirement
[ ] +0 No preference
[ ] -1 Do not adopt the requirement (please explain)
Thanks, Steven
Discussion thread:
https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Talat Uyarer via dev <de...@iceberg.apache.org>.
+1 (non-binding)
On Thu, Oct 8, 2026 at 7:00 AM Amogh Jahagirdar <2a...@gmail.com> wrote:
> +1 (binding)
>
> On Wed, Oct 7, 2026 at 11:59 PM Aihua Xu <ai...@gmail.com> wrote:
>
>> +1 (non-binding)
>>
>>
>> Thanks
>> Aihua
>>
>> On Oct 7, 2026, at 5:58 PM, Junwang Zhao <zh...@gmail.com> wrote:
>>
>>
>> +1 (non-binding)
>>
>>
>> Regards
>> Junwang Zhao
>>
>> On Thu, Oct 8, 2026 at 05:25 Ryan Blue <bl...@apache.org> wrote:
>>
>>> +1 (binding)
>>>
>>> On Wed, Oct 7, 2026 at 1:57 PM Yufei Gu <fl...@gmail.com> wrote:
>>>
>>>> +1(binding)
>>>> Yufei
>>>>
>>>> On Wed, Oct 7, 2026 at 1:55 PM Péter Váry <pe...@gmail.com>
>>>> wrote:
>>>> >
>>>> > +1
>>>> >
>>>> > Matt Topol <zo...@gmail.com> ezt írta (időpont: 2026. okt.
>>>> 7., Sze, 22:30):
>>>> >>
>>>> >> +1 (binding)
>>>> >>
>>>> >> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <
>>>> neeleshssalian@gmail.com> wrote:
>>>> >>>
>>>> >>> +1 (non-binding)
>>>> >>>
>>>> >>> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com>
>>>> wrote:
>>>> >>>>
>>>> >>>> Hi,
>>>> >>>>
>>>> >>>> I propose requiring each new snapshot in a v4 table to have a
>>>> timestamp-ms strictly greater than its parent snapshot’s timestamp on the
>>>> same branch. Root snapshots are unconstrained, and v1–v3 behavior remains
>>>> unchanged.
>>>> >>>>
>>>> >>>> This ensures snapshot timestamps align with snapshot order. This
>>>> change would resolve time travel issues caused by out-of-order snapshot
>>>> timestamps. This can also enable a row timestamp metadata column inherited
>>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>>> >>>>
>>>> >>>> Spec PR: #16294
>>>> >>>> Reference implementation: #16293
>>>> >>>>
>>>> >>>> Please vote in the next 72 hours:
>>>> >>>>
>>>> >>>> [ ] +1 Adopt the requirement
>>>> >>>> [ ] +0 No preference
>>>> >>>> [ ] -1 Do not adopt the requirement (please explain)
>>>> >>>>
>>>> >>>> Thanks, Steven
>>>> >>>>
>>>> >>>>
>>>> >>>> Discussion thread:
>>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>>
>>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Amogh Jahagirdar <2a...@gmail.com>.
+1 (binding)
On Wed, Oct 7, 2026 at 11:59 PM Aihua Xu <ai...@gmail.com> wrote:
> +1 (non-binding)
>
>
> Thanks
> Aihua
>
> On Oct 7, 2026, at 5:58 PM, Junwang Zhao <zh...@gmail.com> wrote:
>
>
> +1 (non-binding)
>
>
> Regards
> Junwang Zhao
>
> On Thu, Oct 8, 2026 at 05:25 Ryan Blue <bl...@apache.org> wrote:
>
>> +1 (binding)
>>
>> On Wed, Oct 7, 2026 at 1:57 PM Yufei Gu <fl...@gmail.com> wrote:
>>
>>> +1(binding)
>>> Yufei
>>>
>>> On Wed, Oct 7, 2026 at 1:55 PM Péter Váry <pe...@gmail.com>
>>> wrote:
>>> >
>>> > +1
>>> >
>>> > Matt Topol <zo...@gmail.com> ezt írta (időpont: 2026. okt. 7.,
>>> Sze, 22:30):
>>> >>
>>> >> +1 (binding)
>>> >>
>>> >> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <ne...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> +1 (non-binding)
>>> >>>
>>> >>> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
>>> >>>>
>>> >>>> Hi,
>>> >>>>
>>> >>>> I propose requiring each new snapshot in a v4 table to have a
>>> timestamp-ms strictly greater than its parent snapshot’s timestamp on the
>>> same branch. Root snapshots are unconstrained, and v1–v3 behavior remains
>>> unchanged.
>>> >>>>
>>> >>>> This ensures snapshot timestamps align with snapshot order. This
>>> change would resolve time travel issues caused by out-of-order snapshot
>>> timestamps. This can also enable a row timestamp metadata column inherited
>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>> >>>>
>>> >>>> Spec PR: #16294
>>> >>>> Reference implementation: #16293
>>> >>>>
>>> >>>> Please vote in the next 72 hours:
>>> >>>>
>>> >>>> [ ] +1 Adopt the requirement
>>> >>>> [ ] +0 No preference
>>> >>>> [ ] -1 Do not adopt the requirement (please explain)
>>> >>>>
>>> >>>> Thanks, Steven
>>> >>>>
>>> >>>>
>>> >>>> Discussion thread:
>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>
>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Aihua Xu <ai...@gmail.com>.
+1 (non-binding)
Thanks
Aihua
> On Oct 7, 2026, at 5:58 PM, Junwang Zhao <zh...@gmail.com> wrote:
>
>
>
>
> +1 (non-binding)
>
>
>
>
>
> Regards
>
>
> Junwang Zhao
>
>
>
>
> On Thu, Oct 8, 2026 at 05:25 Ryan Blue
> <[blue@apache.org](mailto:blue@apache.org)> wrote:
>
>
>> +1 (binding)
>>
>>
>
>>
>> On Wed, Oct 7, 2026 at 1:57 PM Yufei Gu
<[flyrain000@gmail.com](mailto:flyrain000@gmail.com)> wrote:
>
>>
>>> +1(binding)
> Yufei
>
> On Wed, Oct 7, 2026 at 1:55 PM Péter Váry
> <[peter.vary.apache@gmail.com](mailto:peter.vary.apache@gmail.com)> wrote:
> >
> > +1
> >
> > Matt Topol <[zotthewizard@gmail.com](mailto:zotthewizard@gmail.com)> ezt
> írta (időpont: 2026. okt. 7., Sze, 22:30):
> >>
> >> +1 (binding)
> >>
> >> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian
> <[neeleshssalian@gmail.com](mailto:neeleshssalian@gmail.com)> wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>> On Thu, Oct 8, 2026 at 03:23 Steven Wu
> <[stevenz3wu@gmail.com](mailto:stevenz3wu@gmail.com)> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I propose requiring each new snapshot in a v4 table to have a
> timestamp-ms strictly greater than its parent snapshot’s timestamp on the
> same branch. Root snapshots are unconstrained, and v1–v3 behavior remains
> unchanged.
> >>>>
> >>>> This ensures snapshot timestamps align with snapshot order. This
> change would resolve time travel issues caused by out-of-order snapshot
> timestamps. This can also enable a row timestamp metadata column inherited
> from the snapshot timestamp (a separate follow-up v4 spec change).
> >>>>
> >>>> Spec PR: #16294
> >>>> Reference implementation: #16293
> >>>>
> >>>> Please vote in the next 72 hours:
> >>>>
> >>>> [ ] +1 Adopt the requirement
> >>>> [ ] +0 No preference
> >>>> [ ] -1 Do not adopt the requirement (please explain)
> >>>>
> >>>> Thanks, Steven
> >>>>
> >>>>
> >>>> Discussion thread:
> <https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10>
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Junwang Zhao <zh...@gmail.com>.
+1 (non-binding)
Regards
Junwang Zhao
On Thu, Oct 8, 2026 at 05:25 Ryan Blue <bl...@apache.org> wrote:
> +1 (binding)
>
> On Wed, Oct 7, 2026 at 1:57 PM Yufei Gu <fl...@gmail.com> wrote:
>
>> +1(binding)
>> Yufei
>>
>> On Wed, Oct 7, 2026 at 1:55 PM Péter Váry <pe...@gmail.com>
>> wrote:
>> >
>> > +1
>> >
>> > Matt Topol <zo...@gmail.com> ezt írta (időpont: 2026. okt. 7.,
>> Sze, 22:30):
>> >>
>> >> +1 (binding)
>> >>
>> >> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <ne...@gmail.com>
>> wrote:
>> >>>
>> >>> +1 (non-binding)
>> >>>
>> >>> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> I propose requiring each new snapshot in a v4 table to have a
>> timestamp-ms strictly greater than its parent snapshot’s timestamp on the
>> same branch. Root snapshots are unconstrained, and v1–v3 behavior remains
>> unchanged.
>> >>>>
>> >>>> This ensures snapshot timestamps align with snapshot order. This
>> change would resolve time travel issues caused by out-of-order snapshot
>> timestamps. This can also enable a row timestamp metadata column inherited
>> from the snapshot timestamp (a separate follow-up v4 spec change).
>> >>>>
>> >>>> Spec PR: #16294
>> >>>> Reference implementation: #16293
>> >>>>
>> >>>> Please vote in the next 72 hours:
>> >>>>
>> >>>> [ ] +1 Adopt the requirement
>> >>>> [ ] +0 No preference
>> >>>> [ ] -1 Do not adopt the requirement (please explain)
>> >>>>
>> >>>> Thanks, Steven
>> >>>>
>> >>>>
>> >>>> Discussion thread:
>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Ryan Blue <bl...@apache.org>.
+1 (binding)
On Wed, Oct 7, 2026 at 1:57 PM Yufei Gu <fl...@gmail.com> wrote:
> +1(binding)
> Yufei
>
> On Wed, Oct 7, 2026 at 1:55 PM Péter Váry <pe...@gmail.com>
> wrote:
> >
> > +1
> >
> > Matt Topol <zo...@gmail.com> ezt írta (időpont: 2026. okt. 7.,
> Sze, 22:30):
> >>
> >> +1 (binding)
> >>
> >> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <ne...@gmail.com>
> wrote:
> >>>
> >>> +1 (non-binding)
> >>>
> >>> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I propose requiring each new snapshot in a v4 table to have a
> timestamp-ms strictly greater than its parent snapshot’s timestamp on the
> same branch. Root snapshots are unconstrained, and v1–v3 behavior remains
> unchanged.
> >>>>
> >>>> This ensures snapshot timestamps align with snapshot order. This
> change would resolve time travel issues caused by out-of-order snapshot
> timestamps. This can also enable a row timestamp metadata column inherited
> from the snapshot timestamp (a separate follow-up v4 spec change).
> >>>>
> >>>> Spec PR: #16294
> >>>> Reference implementation: #16293
> >>>>
> >>>> Please vote in the next 72 hours:
> >>>>
> >>>> [ ] +1 Adopt the requirement
> >>>> [ ] +0 No preference
> >>>> [ ] -1 Do not adopt the requirement (please explain)
> >>>>
> >>>> Thanks, Steven
> >>>>
> >>>>
> >>>> Discussion thread:
> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Yufei Gu <fl...@gmail.com>.
+1(binding)
Yufei
On Wed, Oct 7, 2026 at 1:55 PM Péter Váry <pe...@gmail.com> wrote:
>
> +1
>
> Matt Topol <zo...@gmail.com> ezt írta (időpont: 2026. okt. 7., Sze, 22:30):
>>
>> +1 (binding)
>>
>> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <ne...@gmail.com> wrote:
>>>
>>> +1 (non-binding)
>>>
>>> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I propose requiring each new snapshot in a v4 table to have a timestamp-ms strictly greater than its parent snapshot’s timestamp on the same branch. Root snapshots are unconstrained, and v1–v3 behavior remains unchanged.
>>>>
>>>> This ensures snapshot timestamps align with snapshot order. This change would resolve time travel issues caused by out-of-order snapshot timestamps. This can also enable a row timestamp metadata column inherited from the snapshot timestamp (a separate follow-up v4 spec change).
>>>>
>>>> Spec PR: #16294
>>>> Reference implementation: #16293
>>>>
>>>> Please vote in the next 72 hours:
>>>>
>>>> [ ] +1 Adopt the requirement
>>>> [ ] +0 No preference
>>>> [ ] -1 Do not adopt the requirement (please explain)
>>>>
>>>> Thanks, Steven
>>>>
>>>>
>>>> Discussion thread: https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Péter Váry <pe...@gmail.com>.
+1
Matt Topol <zo...@gmail.com> ezt írta (időpont: 2026. okt. 7., Sze,
22:30):
> +1 (binding)
>
> On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <ne...@gmail.com>
> wrote:
>
>> +1 (non-binding)
>>
>> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I propose requiring each new snapshot in a v4 table to have a
>>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>>> remains unchanged.
>>>
>>> This ensures snapshot timestamps align with snapshot order. This change
>>> would resolve time travel issues caused by out-of-order snapshot
>>> timestamps. This can also enable a row timestamp metadata column inherited
>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>>
>>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>>> Reference implementation: #16293
>>> <https://github.com/apache/iceberg/pull/16293>
>>>
>>> Please vote in the next 72 hours:
>>>
>>> [ ] +1 Adopt the requirement
>>> [ ] +0 No preference
>>> [ ] -1 Do not adopt the requirement (please explain)
>>>
>>> Thanks, Steven
>>>
>>>
>>> Discussion thread:
>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>
>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Matt Topol <zo...@gmail.com>.
+1 (binding)
On Wed, Oct 7, 2026, 4:03 PM Neelesh Salian <ne...@gmail.com>
wrote:
> +1 (non-binding)
>
> On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
>
>> Hi,
>>
>> I propose requiring each new snapshot in a v4 table to have a
>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>> remains unchanged.
>>
>> This ensures snapshot timestamps align with snapshot order. This change
>> would resolve time travel issues caused by out-of-order snapshot
>> timestamps. This can also enable a row timestamp metadata column inherited
>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>
>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>> Reference implementation: #16293
>> <https://github.com/apache/iceberg/pull/16293>
>>
>> Please vote in the next 72 hours:
>>
>> [ ] +1 Adopt the requirement
>> [ ] +0 No preference
>> [ ] -1 Do not adopt the requirement (please explain)
>>
>> Thanks, Steven
>>
>>
>> Discussion thread:
>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Neelesh Salian <ne...@gmail.com>.
+1 (non-binding)
On Thu, Oct 8, 2026 at 03:23 Steven Wu <st...@gmail.com> wrote:
> Hi,
>
> I propose requiring each new snapshot in a v4 table to have a timestamp-ms strictly
> greater than its parent snapshot’s timestamp on the same branch. Root
> snapshots are unconstrained, and v1–v3 behavior remains unchanged.
>
> This ensures snapshot timestamps align with snapshot order. This change
> would resolve time travel issues caused by out-of-order snapshot
> timestamps. This can also enable a row timestamp metadata column inherited
> from the snapshot timestamp (a separate follow-up v4 spec change).
>
> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
> Reference implementation: #16293
> <https://github.com/apache/iceberg/pull/16293>
>
> Please vote in the next 72 hours:
>
> [ ] +1 Adopt the requirement
> [ ] +0 No preference
> [ ] -1 Do not adopt the requirement (please explain)
>
> Thanks, Steven
>
>
> Discussion thread:
> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Micah Kornfield <em...@gmail.com>.
+1 (non-binding)
On Wed, Oct 7, 2026 at 12:54 PM Anoop Johnson <an...@apache.org> wrote:
> +1 (non-binding)
>
> On Wed, Oct 7, 2026 at 12:36 PM huaxin gao <hu...@gmail.com> wrote:
>
>> +1 (non-binding)
>>
>> On Wed, Oct 7, 2026 at 12:28 PM Szehon Ho <sz...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> On Wed, Oct 7, 2026 at 11:30 AM Andrei Tserakhau via dev <
>>> dev@iceberg.apache.org> wrote:
>>>
>>>> +1 (non-binding)
>>>>
>>>> On Wed, Oct 7, 2026 at 8:27 PM Russell Spitzer <
>>>> russell.spitzer@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I propose requiring each new snapshot in a v4 table to have a
>>>>>> timestamp-ms strictly greater than its parent snapshot’s timestamp
>>>>>> on the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>>>>>> remains unchanged.
>>>>>>
>>>>>> This ensures snapshot timestamps align with snapshot order. This
>>>>>> change would resolve time travel issues caused by out-of-order snapshot
>>>>>> timestamps. This can also enable a row timestamp metadata column inherited
>>>>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>>>>>
>>>>>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>>>>>> Reference implementation: #16293
>>>>>> <https://github.com/apache/iceberg/pull/16293>
>>>>>>
>>>>>> Please vote in the next 72 hours:
>>>>>>
>>>>>> [ ] +1 Adopt the requirement
>>>>>> [ ] +0 No preference
>>>>>> [ ] -1 Do not adopt the requirement (please explain)
>>>>>>
>>>>>> Thanks, Steven
>>>>>>
>>>>>>
>>>>>> Discussion thread:
>>>>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>>>>
>>>>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Anoop Johnson <an...@apache.org>.
+1 (non-binding)
On Wed, Oct 7, 2026 at 12:36 PM huaxin gao <hu...@gmail.com> wrote:
> +1 (non-binding)
>
> On Wed, Oct 7, 2026 at 12:28 PM Szehon Ho <sz...@gmail.com> wrote:
>
>> +1
>>
>> On Wed, Oct 7, 2026 at 11:30 AM Andrei Tserakhau via dev <
>> dev@iceberg.apache.org> wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Wed, Oct 7, 2026 at 8:27 PM Russell Spitzer <
>>> russell.spitzer@gmail.com> wrote:
>>>
>>>> +1
>>>>
>>>> On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I propose requiring each new snapshot in a v4 table to have a
>>>>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>>>>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>>>>> remains unchanged.
>>>>>
>>>>> This ensures snapshot timestamps align with snapshot order. This
>>>>> change would resolve time travel issues caused by out-of-order snapshot
>>>>> timestamps. This can also enable a row timestamp metadata column inherited
>>>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>>>>
>>>>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>>>>> Reference implementation: #16293
>>>>> <https://github.com/apache/iceberg/pull/16293>
>>>>>
>>>>> Please vote in the next 72 hours:
>>>>>
>>>>> [ ] +1 Adopt the requirement
>>>>> [ ] +0 No preference
>>>>> [ ] -1 Do not adopt the requirement (please explain)
>>>>>
>>>>> Thanks, Steven
>>>>>
>>>>>
>>>>> Discussion thread:
>>>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>>>
>>>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by huaxin gao <hu...@gmail.com>.
+1 (non-binding)
On Wed, Oct 7, 2026 at 12:28 PM Szehon Ho <sz...@gmail.com> wrote:
> +1
>
> On Wed, Oct 7, 2026 at 11:30 AM Andrei Tserakhau via dev <
> dev@iceberg.apache.org> wrote:
>
>> +1 (non-binding)
>>
>> On Wed, Oct 7, 2026 at 8:27 PM Russell Spitzer <ru...@gmail.com>
>> wrote:
>>
>>> +1
>>>
>>> On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I propose requiring each new snapshot in a v4 table to have a
>>>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>>>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>>>> remains unchanged.
>>>>
>>>> This ensures snapshot timestamps align with snapshot order. This change
>>>> would resolve time travel issues caused by out-of-order snapshot
>>>> timestamps. This can also enable a row timestamp metadata column inherited
>>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>>>
>>>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>>>> Reference implementation: #16293
>>>> <https://github.com/apache/iceberg/pull/16293>
>>>>
>>>> Please vote in the next 72 hours:
>>>>
>>>> [ ] +1 Adopt the requirement
>>>> [ ] +0 No preference
>>>> [ ] -1 Do not adopt the requirement (please explain)
>>>>
>>>> Thanks, Steven
>>>>
>>>>
>>>> Discussion thread:
>>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>>
>>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Szehon Ho <sz...@gmail.com>.
+1
On Wed, Oct 7, 2026 at 11:30 AM Andrei Tserakhau via dev <
dev@iceberg.apache.org> wrote:
> +1 (non-binding)
>
> On Wed, Oct 7, 2026 at 8:27 PM Russell Spitzer <ru...@gmail.com>
> wrote:
>
>> +1
>>
>> On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I propose requiring each new snapshot in a v4 table to have a
>>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>>> remains unchanged.
>>>
>>> This ensures snapshot timestamps align with snapshot order. This change
>>> would resolve time travel issues caused by out-of-order snapshot
>>> timestamps. This can also enable a row timestamp metadata column inherited
>>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>>
>>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>>> Reference implementation: #16293
>>> <https://github.com/apache/iceberg/pull/16293>
>>>
>>> Please vote in the next 72 hours:
>>>
>>> [ ] +1 Adopt the requirement
>>> [ ] +0 No preference
>>> [ ] -1 Do not adopt the requirement (please explain)
>>>
>>> Thanks, Steven
>>>
>>>
>>> Discussion thread:
>>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>>
>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Andrei Tserakhau via dev <de...@iceberg.apache.org>.
+1 (non-binding)
On Wed, Oct 7, 2026 at 8:27 PM Russell Spitzer <ru...@gmail.com>
wrote:
> +1
>
> On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
>
>> Hi,
>>
>> I propose requiring each new snapshot in a v4 table to have a
>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>> remains unchanged.
>>
>> This ensures snapshot timestamps align with snapshot order. This change
>> would resolve time travel issues caused by out-of-order snapshot
>> timestamps. This can also enable a row timestamp metadata column inherited
>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>
>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>> Reference implementation: #16293
>> <https://github.com/apache/iceberg/pull/16293>
>>
>> Please vote in the next 72 hours:
>>
>> [ ] +1 Adopt the requirement
>> [ ] +0 No preference
>> [ ] -1 Do not adopt the requirement (please explain)
>>
>> Thanks, Steven
>>
>>
>> Discussion thread:
>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Daniel Weeks <dw...@apache.org>.
+1 (binding)
On Wed, Oct 7, 2026, 11:27 AM Russell Spitzer <ru...@gmail.com>
wrote:
> +1
>
> On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
>
>> Hi,
>>
>> I propose requiring each new snapshot in a v4 table to have a
>> timestamp-ms strictly greater than its parent snapshot’s timestamp on
>> the same branch. Root snapshots are unconstrained, and v1–v3 behavior
>> remains unchanged.
>>
>> This ensures snapshot timestamps align with snapshot order. This change
>> would resolve time travel issues caused by out-of-order snapshot
>> timestamps. This can also enable a row timestamp metadata column inherited
>> from the snapshot timestamp (a separate follow-up v4 spec change).
>>
>> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
>> Reference implementation: #16293
>> <https://github.com/apache/iceberg/pull/16293>
>>
>> Please vote in the next 72 hours:
>>
>> [ ] +1 Adopt the requirement
>> [ ] +0 No preference
>> [ ] -1 Do not adopt the requirement (please explain)
>>
>> Thanks, Steven
>>
>>
>> Discussion thread:
>> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>>
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Russell Spitzer <ru...@gmail.com>.
+1
On Wed, Oct 7, 2026 at 1:23 PM Steven Wu <st...@gmail.com> wrote:
> Hi,
>
> I propose requiring each new snapshot in a v4 table to have a timestamp-ms strictly
> greater than its parent snapshot’s timestamp on the same branch. Root
> snapshots are unconstrained, and v1–v3 behavior remains unchanged.
>
> This ensures snapshot timestamps align with snapshot order. This change
> would resolve time travel issues caused by out-of-order snapshot
> timestamps. This can also enable a row timestamp metadata column inherited
> from the snapshot timestamp (a separate follow-up v4 spec change).
>
> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
> Reference implementation: #16293
> <https://github.com/apache/iceberg/pull/16293>
>
> Please vote in the next 72 hours:
>
> [ ] +1 Adopt the requirement
> [ ] +0 No preference
> [ ] -1 Do not adopt the requirement (please explain)
>
> Thanks, Steven
>
>
> Discussion thread:
> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Steven Wu <st...@gmail.com>.
The vote passes with 9 binding +1s and 11 non-binding +1s, and no 0s or
-1s.
Thanks everyone for the voting. I will merge the spec PR.
On Sun, Oct 11, 2026 at 8:42 AM Maninder Parmar <
parmar.maninderjit@gmail.com> wrote:
> +1 (non-binding)
> Thanks for adding this Steven! This will help greatly to reason about
> transactional consistency.
> I do want us to consider extending timestamp-ms to higher precision
> timestamp-ns (nanoseconds) to allow for greater transaction throughput.
>
>
> On Fri, Oct 9, 2026 at 6:55 PM Hongyue Zhang <ho...@gmail.com>
> wrote:
>
>> +1 (non-binding) and thanks Steven!
>>
>> On Fri, Oct 9, 2026 at 2:53 AM Eduard Tudenhöfner <
>> etudenhoefner@apache.org> wrote:
>>
>>> +1 (binding)
>>>
>>> On Fri, Oct 9, 2026 at 11:03 AM Xuanwo <xu...@apache.org> wrote:
>>>
>>>> +1 (non-binding)
>>>>
>>>> I support requiring newly committed v4 snapshots to have a timestamp-ms
>>>> strictly greater than their parent on the same branch, while leaving root
>>>> snapshots, pre-upgrade snapshots and v1-v3 behavior unchanged.
>>>>
>>>> Thanks,
>>>> Xuanwo
>>>>
>>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Maninder Parmar <pa...@gmail.com>.
+1 (non-binding)
Thanks for adding this Steven! This will help greatly to reason about
transactional consistency.
I do want us to consider extending timestamp-ms to higher precision
timestamp-ns (nanoseconds) to allow for greater transaction throughput.
On Fri, Oct 9, 2026 at 6:55 PM Hongyue Zhang <ho...@gmail.com>
wrote:
> +1 (non-binding) and thanks Steven!
>
> On Fri, Oct 9, 2026 at 2:53 AM Eduard Tudenhöfner <
> etudenhoefner@apache.org> wrote:
>
>> +1 (binding)
>>
>> On Fri, Oct 9, 2026 at 11:03 AM Xuanwo <xu...@apache.org> wrote:
>>
>>> +1 (non-binding)
>>>
>>> I support requiring newly committed v4 snapshots to have a timestamp-ms
>>> strictly greater than their parent on the same branch, while leaving root
>>> snapshots, pre-upgrade snapshots and v1-v3 behavior unchanged.
>>>
>>> Thanks,
>>> Xuanwo
>>>
>>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Hongyue Zhang <ho...@gmail.com>.
+1 (non-binding) and thanks Steven!
On Fri, Oct 9, 2026 at 2:53 AM Eduard Tudenhöfner <et...@apache.org>
wrote:
> +1 (binding)
>
> On Fri, Oct 9, 2026 at 11:03 AM Xuanwo <xu...@apache.org> wrote:
>
>> +1 (non-binding)
>>
>> I support requiring newly committed v4 snapshots to have a timestamp-ms
>> strictly greater than their parent on the same branch, while leaving root
>> snapshots, pre-upgrade snapshots and v1-v3 behavior unchanged.
>>
>> Thanks,
>> Xuanwo
>>
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Eduard Tudenhöfner <et...@apache.org>.
+1 (binding)
On Fri, Oct 9, 2026 at 11:03 AM Xuanwo <xu...@apache.org> wrote:
> +1 (non-binding)
>
> I support requiring newly committed v4 snapshots to have a timestamp-ms
> strictly greater than their parent on the same branch, while leaving root
> snapshots, pre-upgrade snapshots and v1-v3 behavior unchanged.
>
> Thanks,
> Xuanwo
>
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Xuanwo <xu...@apache.org>.
+1 (non-binding)
I support requiring newly committed v4 snapshots to have a timestamp-ms strictly greater than their parent on the same branch, while leaving root snapshots, pre-upgrade snapshots and v1-v3 behavior unchanged.
Thanks,
Xuanwo
Re: [VOTE] Require monotonically increasing snapshot timestamps in v4
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (non binding)
Regards
JB
On Wed, Oct 7, 2026 at 7:23 PM Steven Wu <st...@gmail.com> wrote:
> Hi,
>
> I propose requiring each new snapshot in a v4 table to have a timestamp-ms strictly
> greater than its parent snapshot’s timestamp on the same branch. Root
> snapshots are unconstrained, and v1–v3 behavior remains unchanged.
>
> This ensures snapshot timestamps align with snapshot order. This change
> would resolve time travel issues caused by out-of-order snapshot
> timestamps. This can also enable a row timestamp metadata column inherited
> from the snapshot timestamp (a separate follow-up v4 spec change).
>
> Spec PR: #16294 <https://github.com/apache/iceberg/pull/16294>
> Reference implementation: #16293
> <https://github.com/apache/iceberg/pull/16293>
>
> Please vote in the next 72 hours:
>
> [ ] +1 Adopt the requirement
> [ ] +0 No preference
> [ ] -1 Do not adopt the requirement (please explain)
>
> Thanks, Steven
>
>
> Discussion thread:
> https://lists.apache.org/thread/cln7xtjy9kw2096gzqlg5c4gg8b9td10
>