[
https://issues.apache.org/jira/browse/ARROW-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981267#comment-15981267
]
Jacques Nadeau commented on ARROW-883:
--------------------------------------
It sounds like my initial thought on where the problem was is wrong. It seems
like the introduction of new date/time types has caused old schemas to break.
Basically, the default units should be the same as the non-unit behavior. In
the case of Date that was MILLISECONDS. However, the default is now DAY (0).
Seems like the flatbuf should be reordered so that 0 corresponds to
MILLISECONDS.
> [JAVA] Introduction of new types has shifted Enumerations
> ---------------------------------------------------------
>
> Key: ARROW-883
> URL: https://issues.apache.org/jira/browse/ARROW-883
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Jacques Nadeau
> Assignee: Julien Le Dem
> Priority: Blocker
> Fix For: 0.3.0
>
>
> The introduction of new types in
> https://github.com/apache/arrow/blame/master/java/vector/src/main/java/org/apache/arrow/vector/types/Types.java
> Has shifted the enumeration ordinals, causing compatibility problems with
> older java code that serializes the ordinals. Should be fixed before 0.3
> release
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
