[ 
https://issues.apache.org/jira/browse/ARROW-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356182#comment-16356182
 ] 

ASF GitHub Bot commented on ARROW-1425:
---------------------------------------

wesm commented on a change in pull request #1575: ARROW-1425 [Doc] Document 
Arrow timestamps, and interops w/ other systems
URL: https://github.com/apache/arrow/pull/1575#discussion_r166779301
 
 

 ##########
 File path: python/doc/source/timestamps.rst
 ##########
 @@ -0,0 +1,433 @@
+All About Timestamps (work in progress)
 
 Review comment:
   This is a big document. I'd like to see if we can make this about 50% as 
long or less. I will review in more detail as soon as I can and make some 
comments to help

----------------------------------------------------------------
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: Heimir Thor Sverrisson
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.9.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)

Reply via email to