[
https://issues.apache.org/jira/browse/ARROW-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247993#comment-16247993
]
ASF GitHub Bot commented on ARROW-1785:
---------------------------------------
icexelloss commented on issue #1297: WIP ARROW-1785: [Format/C++/Java] Remove
VectorLayout from serialized schemas
URL: https://github.com/apache/arrow/pull/1297#issuecomment-343572816
I can take a look at this. My understanding is we want to remove vector
layout from metadata and assume buffer ordering (validity, data) and (validity,
offset, data) in readers, is that correct?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> [Format] Remove VectorLayout metadata from Flatbuffers metadata
> ---------------------------------------------------------------
>
> Key: ARROW-1785
> URL: https://issues.apache.org/jira/browse/ARROW-1785
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Format, Java - Vectors
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Labels: pull-request-available
> Fix For: 0.8.0
>
>
> Based on the discussions on the mailing list, we should remove the
> VectorLayout metadata from the Flatbuffers spec for 0.8.0 since we are
> already breaking the metadata. We should instead make the buffer layouts an
> immutable part of the format specification so there is no ambiguity about
> what buffers accompany each type of field in an Arrow payload
> see also ARROW-1693
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
