[
https://issues.apache.org/jira/browse/ARROW-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054269#comment-16054269
]
Ryan Blue commented on ARROW-1120:
----------------------------------
I don't think Presto has support for the int64 timestamps. I'd recommend using
an int64 with a timestamp in milliseconds for now. That's what we use because
we can control behavior and know what we are getting that way, instead of int96
where you can get different values depending on versions and processing engine.
I think it is a better idea to spend time on support for the types that are
well defined and don't have the historical baggage.
> Write support for int96
> -----------------------
>
> Key: ARROW-1120
> URL: https://issues.apache.org/jira/browse/ARROW-1120
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: colin nichols
>
> Hi there,
> I am trying to use pyarrow to convert CSV files to Parquet for use with
> Redshift Spectrum. I've got everything sorted... almost :)
> Unfortunately, the only format they accept for timestamp columns is int96. I
> understand that int96 timestamps are unofficial/deprecated, but unfortunately
> it's what I am stuck with for integrating with, at least for the moment. I
> contacted Amazon support and 64-bit timestamp support has been added to the
> list of feature requests, but it's unclear when it will be
> prioritized/added/released.
> In the meantime, I am thinking of adding write support for int96 columns to
> arrow. Would that be a welcome addition?
> Thanks,
> Colin
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
