[
https://issues.apache.org/jira/browse/ARROW-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205249#comment-16205249
]
ASF GitHub Bot commented on ARROW-1674:
---------------------------------------
Github user wesm commented on the issue:
https://github.com/apache/arrow/pull/1201
@jacques-n in general I would agree where “odd logical types” do not fit in
any obvious place in our type metadata, the custom_metadata field can be
employed. The data here is not a bit vector, it semantically boolean. In this
particular case I would argue that over time enough systems will feature native
support for a byte-size boolean that having unambiguous metadata would be
valuable. If we use custom_metadata, then two systems must be aware of their
respective conventions for annotating boolean data, which may cause
implementers a headache
> [Format] Add bit width metadata to Bool logical type
> ----------------------------------------------------
>
> Key: ARROW-1674
> URL: https://issues.apache.org/jira/browse/ARROW-1674
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Format
> Reporter: Wes McKinney
> Labels: pull-request-available
> Fix For: 0.8.0
>
>
> Some libraries represent boolean data as a single byte per value as a vector
> of int8/uint8 1's and 0's. It would be useful to be able to retain this
> metadata as an optional field on the {{Bool}} table in {{Schema.fbs}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
