You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by "Yuliya Feldman (JIRA)" <ji...@apache.org> on 2018/07/12 22:58:00 UTC

[jira] [Created] (ARROW-2843) [Format/C++/Java] Removing field layout from Schema.fbs breaks backward compatibility

Yuliya Feldman created ARROW-2843:
-------------------------------------

             Summary: [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.9.0, 0.8.0
            Reporter: Yuliya Feldman
            Assignee: Yuliya Feldman


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)