You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Arina Ielchiieva (JIRA)" <ji...@apache.org> on 2016/04/06 18:43:25 UTC

[jira] [Updated] (HIVE-13435) Hive fails to read timestamp stored as binary / int64 from externally generated parquet files

     [ https://issues.apache.org/jira/browse/HIVE-13435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arina Ielchiieva updated HIVE-13435:
------------------------------------
    Description: 
If timestamp in parquet file is stored as binary / int64 (ex: parquet file wasn't created using Hive), Hive fails to read such parquet files, as it expects timestamp to be only in int96.
It would be nice if Hive can read such files.

  was:
If timestamp in parquet file is stored as binary (ex: parquet file wasn't created using Hive), Hive fails to read such parquet files, as it expects timestamp to be only in int96.
It would be nice if Hive can read such files.


> Hive fails to read timestamp stored as binary / int64 from externally generated parquet files
> ---------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13435
>                 URL: https://issues.apache.org/jira/browse/HIVE-13435
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Arina Ielchiieva
>
> If timestamp in parquet file is stored as binary / int64 (ex: parquet file wasn't created using Hive), Hive fails to read such parquet files, as it expects timestamp to be only in int96.
> It would be nice if Hive can read such files.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)