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

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

wesm commented on issue #1095: ARROW-1425 [Python] Document semantic 
differences between Spark and Arrow timestamps
URL: https://github.com/apache/arrow/pull/1095#issuecomment-339527887
 
 
   @icexelloss @heimir-sverrisson it may make sense to engage in 
https://github.com/apache/spark/pull/18664 and at least try to process the 
discussion that is going on around time zones. This is some very thorny stuff 
and I don't have the bandwidth right this moment to properly engage with this

----------------------------------------------------------------
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
>              Labels: pull-request-available
>             Fix For: 0.8.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
(v6.4.14#64029)

Reply via email to