[RESULT] [VOTE] Adopt the v2 spec changes

[Ryan Blue <bl...@tabular.io>]

With 10 +1 votes and no +0 or -1 votes, this passes.

Thanks, everyone for looking into the format changes and taking the time to
vote! And thanks to everyone that worked on getting v2 implemented, tested,
and documented!

I'll put up some PRs to reflect this change in the spec.

Ryan

On Sun, Aug 1, 2021 at 3:21 PM Anton Okolnychyi
<ao...@apple.com.invalid> wrote:

> +1 (binding)
>
> Anton
>
>
> On Aug 1, 2021, at 2:40 PM, Carl Steinbach <cw...@tabular.io> wrote:
>
> 
> +1 (binding)
>
> On Wed, Jul 28, 2021 at 6:43 PM Daniel Weeks <dw...@apache.org> wrote:
>
>> +1
>>
>> On Wed, Jul 28, 2021, 1:36 PM Kyle Bendickson
>> <kb...@apple.com.invalid> wrote:
>>
>>> +1 (non-binding)
>>>
>>> 
>>>
>>> *Kyle Bendickson*
>>> Software Engineer
>>> Apple
>>> ACS Data
>>> One Apple Park Way,
>>> Cupertino, CA 95014, USA
>>> kbendickson@apple.com
>>>
>>> This email and any attachments may be privileged and may contain
>>> confidential information intended only for the recipient(s) named above.
>>> Any other distribution, forwarding, copying or disclosure of this message
>>> is strictly prohibited. If you have received this email in error, please
>>> notify me immediately by telephone or return email, and delete this message
>>> from your system.
>>>
>>> On Jul 27, 2021, at 9:58 AM, Ryan Blue <bl...@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
Tabular