[JAVA] Introduction of new types has shifted Enumerations

[asfimport]

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

Reporter: Jacques Nadeau / @jacques-n
Assignee: Julien Le Dem / @julienledem

Related issues:

• Arrow 0.3 release (blocks)
• [format] For backward compatibility, new unit fields must have default values matching previous implied unit (is related to)

_{Note: This issue was originally created as ARROW-883. Please see the migration documentation for further details.}

[asfimport]

Julien Le Dem / @julienledem:
@jacques-n To clarify, You are referring to the ordinals of the Types.MinorType enum?

[asfimport]

Jacques Nadeau / @jacques-n:
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.

[asfimport]

Julien Le Dem / @julienledem:
That was resolved by ARROW-887

[asfimport]

Todd Farmer / @toddfarmer:
Transitioning issue from Resolved to Closed to based on resolution field value.