[ https://issues.apache.org/jira/browse/ARROW-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852546#comment-16852546 ]
Wes McKinney commented on ARROW-3702: ------------------------------------- cc [~npr] > [R] POSIXct mapped to DateType not TimestampType? > ------------------------------------------------- > > Key: ARROW-3702 > URL: https://issues.apache.org/jira/browse/ARROW-3702 > Project: Apache Arrow > Issue Type: Improvement > Components: R > Reporter: Javier Luraschi > Priority: Major > Fix For: 0.14.0 > > > Why was POSIXct mapped to > [DataType|https://arrow.apache.org/docs/cpp/classarrow_1_1_date_type.html#a6aea1fcfd9f998e8fa50f5ae62dbd7e6] > not > [TimestampType|https://arrow.apache.org/docs/cpp/classarrow_1_1_timestamp_type.html#a88e0ba47b82571b3fc3798b6c099499b]? > What are the PRO/CONs from each approach? > This is mostly to interoperate with Spark which choose to map POSIXct to > Timestamps since in Spark, not Arrow, dates do not have a time component. > There is a way to make this work in Spark with POSIXct mapped to DateType by > mapping DateType to timestamps, so mostly looking to understand tradeoffs. > One particular question, timestamps in arrow seem to support timezones, > wouldn't it make more sense to map POSIXct to timestamps? -- This message was sent by Atlassian JIRA (v7.6.3#76005)