[ https://issues.apache.org/jira/browse/ARROW-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926591#comment-15926591 ]
Bryan Cutler commented on ARROW-617: ------------------------------------ I am ok with having 2 time types if it helps with performance/zero copies. Will it be something that is transparent to the Arrow user and the storage size is determined automatically by the unit, or will it be unit-less and the user would pick the appropriate type, either Time32 or Time64? I think I'd prefer the latter because I would want to know what's going on behind the scenes. > 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)