[Format] Interval(DAY_TIME) has no unit

[asfimport]

Interval(DATE_TIME) assumes milliseconds.
we should have a time unit like timestamp.

Reporter: Julien Le Dem / @julienledem
Assignee: Micah Kornfield / @emkornfield

Related issues:

• [Format] Add Timedelta type to describe time intervals (is related to)

PRs and other links:

• GitHub Pull Request #3644
• GitHub Pull Request #3645
• GitHub Pull Request #920

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

[asfimport]

Wes McKinney / @wesm:
Is this a blocker?

[asfimport]

Wes McKinney / @wesm:
Made not a blocker

[asfimport]

Wes McKinney / @wesm:
Per https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/c-interval-structure; I think if we add a unit to Interval then this accounts for the Timedelta type we've discussed in ARROW-835

[asfimport]

Wes McKinney / @wesm:
PR: #920

[asfimport]

Wes McKinney / @wesm:
Moving off 0.6.0 as this will require some discussion

[asfimport]

Wes McKinney / @wesm:
@jacques-n what's the best way forward on this?

[asfimport]

Wes McKinney / @wesm:
It doesn't look like we will resolve this for 0.9.0

[asfimport]

Wes McKinney / @wesm:
We've stalled out on this issue. I marked this as part of getting the columnar format to a "1.0" state. We should try to reach a consensus and make appropriate changes in the next few months

[asfimport]

Micah Kornfield / @emkornfield:
This type is marked as optional. Duration should be used in most use-cases when finer resolution is needed.

[asfimport]

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