You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Uwe L. Korn (JIRA)" <ji...@apache.org> on 2018/01/11 08:25:00 UTC

[jira] [Created] (ARROW-1989) [Python] Better UX on timestamp conversion to Pandas

Uwe L. Korn created ARROW-1989:
----------------------------------

             Summary: [Python] Better UX on timestamp conversion to Pandas
                 Key: ARROW-1989
                 URL: https://issues.apache.org/jira/browse/ARROW-1989
             Project: Apache Arrow
          Issue Type: Improvement
          Components: Python
            Reporter: Uwe L. Korn
             Fix For: 0.9.0


Converting timestamp columns to Pandas, users often have the problem that they have dates that are larger than Pandas can represent with their nanosecond representation. Currently they simply see an Arrow exception and think that this problem is caused by Arrow. We should try to change the error from

{code}
ArrowInvalid: Casting from timestamp[ns] to timestamp[us] would lose data: XX
{code}

to something along the lines of 

{code}
ArrowInvalid: Casting from timestamp[ns] to timestamp[us] would lose data: XX. This conversion is needed as Pandas does only support nanosecond timestamps. Your data is likely out of the range that can be represented with nanosecond resolution.
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)