[
https://issues.apache.org/jira/browse/ARROW-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542323#comment-16542323
]
Wes McKinney commented on ARROW-2843:
-------------------------------------
I'm -0 to -1 on this change. We do already have a metadata version number.
We've made no guarantees of backwards compatibility in the columnar format
metadata yet, so we have broken no contracts with users.
To be honest, I'm not pleased that there are still a number of underspecified
parts of the columnar format and metadata. As an example, I proposed a more
complete Interval / Timedelta type about a year ago and these changes have
still not been implemented.
I would very much appreciate if Dremio and other parties depending on Arrow in
production would work more proactively with me and others in the Arrow
community to reach a point where we can declare a stable 1.0 version of the
columnar format and its metadata. In particular, if any more breaking changes
are required (I hope that there will not be), that we make them as soon as
possible to minimize disruption to applications.
> [Format/C++/Java] Removing field layout from Schema.fbs breaks backward
> compatibility
> -------------------------------------------------------------------------------------
>
> Key: ARROW-2843
> URL: https://issues.apache.org/jira/browse/ARROW-2843
> Project: Apache Arrow
> Issue Type: Bug
> Components: Format
> Affects Versions: 0.8.0, 0.9.0
> Reporter: Yuliya Feldman
> Assignee: Yuliya Feldman
> Priority: Major
>
> Change in [ARROW-1785|https://issues.apache.org/jira/browse/ARROW-1785]
> Breaks backward compatibility with schema generated in prior versions of
> Arrow, as VectorLayout field was removed from Field table.
> This is definitely not supported behavior in FlatBuffers.
> I suggest to put back following field
> {code:java}
> layout: [ VectorLayout ] (deprecated);
> {code}
> into
> {code:java}
> table Field
> {code}
> and mark it "deprecated" - as shown above
> It will also require putting back
> {code:java}
> table VectorLayout
> {code}
> which can have all the deprecated fields as well.
> code generation footprint will be minimal in this case, as FlatBuffers won't
> generate getters for deprecated fields, but it will really solve backward
> compatibility issues.
> Also may be a good idea to introduce "version" into Schema.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
