[
https://issues.apache.org/jira/browse/ARROW-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412818#comment-16412818
]
ASF GitHub Bot commented on ARROW-1425:
---------------------------------------
wesm commented on issue #1575: ARROW-1425: [Python] Document Arrow timestamps,
and interops w/ other systems
URL: https://github.com/apache/arrow/pull/1575#issuecomment-375929245
Yes, we should. This document is too long. I can take a shot at making it
much shorter, summarizing only the relevant details that pandas users need to
understand. If you would like to take a pass on it in the meantime, please go
ahead. We are still having problems with 0.9.0 packages so 0.9.0 issues live on
right now
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [Python] Document semantic differences between Spark timestamps and Arrow
> timestamps
> ------------------------------------------------------------------------------------
>
> Key: ARROW-1425
> URL: https://issues.apache.org/jira/browse/ARROW-1425
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Wes McKinney
> Assignee: Li Jin
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.10.0
>
>
> The way that Spark treats non-timezone-aware timestamps as session local can
> be problematic when using pyarrow which may view the data coming from
> toPandas() as time zone naive (but with fields as though it were UTC, not
> session local). We should document carefully how to properly handle the data
> coming from Spark to avoid problems.
> cc [~bryanc] [~holdenkarau]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
