[
https://issues.apache.org/jira/browse/ARROW-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420732#comment-15420732
]
Wes McKinney commented on ARROW-256:
------------------------------------
Agreed. I would assume that we would add this as the first field in the Message
type in
https://github.com/apache/arrow/blob/master/format/Message.fbs#L174
As an aside, for Flatbuffers as a metadata representation in particular, we
will obviously have to take care that a v2 message can be received by a v1
consumer (where the internals of the Message differ significantly). My
understanding from reading the docs is that as long as the version is at the
head of the Message table then the vtable indirection
(https://google.github.io/flatbuffers/flatbuffers_white_paper.html) makes this
safe.
> Add versioning to the arrow spec.
> ---------------------------------
>
> Key: ARROW-256
> URL: https://issues.apache.org/jira/browse/ARROW-256
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Format
> Reporter: Julien Le Dem
>
> We should add a version field that describes the version of the spec.
> This will allow creating a spec v2 and schema negotiation between
> implementers that may not be using the same version of the spec.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
