You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "H. Vetinari (JIRA)" <ji...@apache.org> on 2019/07/17 11:45:00 UTC

[jira] [Created] (HIVE-22006) Hive parquet timestamp compatibility, part 2

H. Vetinari created HIVE-22006:
----------------------------------

             Summary: Hive parquet timestamp compatibility, part 2
                 Key: HIVE-22006
                 URL: https://issues.apache.org/jira/browse/HIVE-22006
             Project: Hive
          Issue Type: Bug
    Affects Versions: All Versions
            Reporter: H. Vetinari


The interaction between HIVE / IMPALA / SPARK writing timestamps is a major source of headaches in every scenario where such interaction cannot be avoided.

HIVE-9482 added hive.parquet.timestamp.skip.conversion, which *only* affects the *reading* of timestamps.

It formulates the next steps as:
> Later fix will change the write path to not convert, and stop the read-conversion even for files written by Hive itself.

At the very least, HIVE needs a switch to also turn off the conversion on writes. That would at least allow a setup where all three of HIVE / IMPALA / SPARK can be configured not to convert on read/write, and can hence safely work on the same data



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)