[
https://issues.apache.org/jira/browse/ARROW-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906655#comment-15906655
]
Wes McKinney commented on ARROW-617:
------------------------------------
Practically speaking, I'm OK with having both a "time64" and "time32" data type
with a particular resolution/unit, e.g.
- time64 would be 64 bits per value and accommodate microseconds and
nanoseconds. For compatibility, we could also allow Time64 to hold both seconds
and milliseconds
- time32 would be milliseconds and seconds only
If it makes things too complicated, we could constrain 64-bit time to be only
micro and nanoseconds.
Thoughts?
> Time type is not specified clearly
> ----------------------------------
>
> Key: ARROW-617
> URL: https://issues.apache.org/jira/browse/ARROW-617
> Project: Apache Arrow
> Issue Type: Bug
> Components: Format
> Reporter: Julien Le Dem
>
> 2 options:
> - Use 64 bits for microseconds and nanoseconds, 32 bits for other units
> - Use 64 bits for everything
> The latter is simpler to implement, the former saves space.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
