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 2017/06/15 18:13:00 UTC

[jira] [Commented] (ARROW-1120) Write support for int96

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

Uwe L. Korn commented on ARROW-1120:
------------------------------------

Feel free to make a PR to add Int96 write support. Most of the work is probably in parquet-cpp where we already have a read support for Int96 thus testing the new code should be quite easily. Also you will have to add a flag in pyarrow & parquet-cpp to select the target timestamp type for the Parquet files.

cc [~rdblue]: Two cases for the highlight: I thought Spectrum/Athena are Presto-based, is there no int64-timestamp support there? Also adding Int96 write support to parquet-cpp will help us get some parquet-cpp/pyarrow usage in this case but also harm the deprecation of Int96.

> 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)