Format change review request: ARROW-62

[Wes McKinney <we...@cloudera.com>]

Can another committer please review

https://github.com/apache/arrow/pull/34

This corrects a format specification inconsistency viz-a-viz the
bitmap encoding null/not-null from the initial draft format documents.

Note that this is orthogonal to the discussion about whether the
concept of "non-nullable" (or "required") is a part of the physical
memory layout or the schema metadata. I will propose a patch for
ARROW-76 after this one is addressed.

Thank you,
Wes

Re: Format change review request: ARROW-62

[Wes McKinney <we...@cloudera.com>]

I also addressed ARROW-76 in this patch per Jacques's feedback — more
comments welcome! Hopefully these changes are not controversial now
that we have a draft end-to-end metadata specification (which includes
non-nullable fields, if they are needed).

Thanks

On Wed, Mar 23, 2016 at 2:00 PM, Wes McKinney <we...@cloudera.com> wrote:
> Can another committer please review
>
> https://github.com/apache/arrow/pull/34
>
> This corrects a format specification inconsistency viz-a-viz the
> bitmap encoding null/not-null from the initial draft format documents.
>
> Note that this is orthogonal to the discussion about whether the
> concept of "non-nullable" (or "required") is a part of the physical
> memory layout or the schema metadata. I will propose a patch for
> ARROW-76 after this one is addressed.
>
> Thank you,
> Wes