[
https://issues.apache.org/jira/browse/ARROW-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550093#comment-16550093
]
Yuliya Feldman commented on ARROW-2843:
---------------------------------------
I am going to resolve this Jira as "won't fix", as it will create issues with
0.8, 0.9 versions around backward compatibility (though we did not promise it
yet).
Just for the future we have to be much more strict regarding changes in "fbs"
and do not allow fields removal - make them deprecated at least.
> [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
> Labels: pull-request-available
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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)
