[
https://issues.apache.org/jira/browse/ARROW-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213422#comment-16213422
]
ASF GitHub Bot commented on ARROW-1663:
---------------------------------------
Github user jacques-n commented on the issue:
https://github.com/apache/arrow/pull/1193
We aren't making the guarantee at the Arrow level that schema is backwards
compatible. However, we have a bunch of Dremio OSS and Enterprise users that
are relying on this code and the inconsistency here has been causing us
problems (when dealing with data that is initially untyped lists but then is
later found to have a type). I don't see much issue to adding the backwards
compatibility code and it should help others who might have hit a problem. What
are your concerns @BryanCutler?
> Follow up on ARROW-1347 and make schema backward compatible
> -----------------------------------------------------------
>
> Key: ARROW-1663
> URL: https://issues.apache.org/jira/browse/ARROW-1663
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java - Vectors
> Reporter: Yuliya Feldman
> Assignee: Yuliya Feldman
> Labels: pull-request-available
> Fix For: 0.8.0
>
>
> ARROW-1347 covered ListVector to have name of the field $data$ instead of
> [DEFAULT]
> We left FixedSizeListVector behind.
> Another case is backward compatibility - if schema was created before
> ARROW-1347 was in place application may still suffer from side effects as it
> would not be updated based on new code.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
