FYI, regarding the syntax to allow experimenting with the v2 format easily,
I put up a PR: https://github.com/apache/iceberg/pull/2887
-Jack

On Wed, Jul 28, 2021 at 12:23 PM Yan Yan <yyany...@gmail.com> wrote:

> +1 (non-binding)
>
> On Wed, Jul 28, 2021 at 10:52 AM Yufei Gu <flyrain...@gmail.com> wrote:
>
>> +1 (non-binding)
>> Best,
>>
>> Yufei
>>
>> `This is not a contribution`
>>
>>
>> On Wed, Jul 28, 2021 at 8:34 AM Ryan Murray <rym...@gmail.com> wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Wed, Jul 28, 2021 at 5:14 PM Russell Spitzer <
>>> russell.spit...@gmail.com> wrote:
>>>
>>>> +1 (non-binding)
>>>>
>>>> On Jul 28, 2021, at 10:11 AM, Ryan Blue <b...@apache.org> wrote:
>>>>
>>>> +1
>>>>
>>>> On Tue, Jul 27, 2021 at 9:58 AM Ryan Blue <b...@apache.org> wrote:
>>>>
>>>>> I’d like to propose that we adopt the pending v2 spec changes as the
>>>>> supported v2 spec. The full list of changes is documented in the v2
>>>>> summary section of the spec
>>>>> <https://iceberg.apache.org/spec/#version-2>.
>>>>>
>>>>> The major breaking change is the addition of delete files and metadata
>>>>> to track delete files. In addition, there are a few other minor breaking
>>>>> changes. For example, v2 drops the block_size_in_bytes field in
>>>>> manifests that was previously required and also omits fields in table
>>>>> metadata that are now tracked by lists; schema is no longer written
>>>>> in favor of schemas. Other changes are forward compatible, mostly
>>>>> tightening field requirements where possible (e.g., schemas and
>>>>> current-schema-id are now required).
>>>>>
>>>>> Adopting the changes will signal that the community intends to support
>>>>> the current set of changes and will guarantee forward-compatibility for v2
>>>>> tables that implement the current v2 spec. Any new breaking changes would
>>>>> go into v3.
>>>>>
>>>>> Please vote on adopting the v2 changes in the next 72 hours.
>>>>>
>>>>> [ ] +1 Adopt the changes as v2
>>>>> [ ] +0
>>>>> [ ] -1 Do not adopt the changes, because…
>>>>> --
>>>>> Ryan Blue
>>>>>
>>>>
>>>>
>>>> --
>>>> Ryan Blue
>>>>
>>>>
>>>>

Reply via email to