[
https://issues.apache.org/jira/browse/ARROW-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205262#comment-16205262
]
ASF GitHub Bot commented on ARROW-1674:
---------------------------------------
Github user wesm commented on the issue:
https://github.com/apache/arrow/pull/1201
@jacques-n I see. Our data types in Schema.fbs are all logical anyway, and
it's only through interpretation of the metadata that we determine the physical
memory representation.
I can implement a solution using `custom_metadata` to unblock the immediate
need for 0.8.0 and perhaps we can take a "wait and see" approach on the Arrow
schema having built-in knowledge of 8-bit booleans. This will be useful anyway
for the next time we need to add a C++ logical type that isn't part of
Schema.fbs. @pcmoritz do you mind me pushing to this branch?
> [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)
