[
https://issues.apache.org/jira/browse/HIVE-22006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040145#comment-17040145
]
H. Vetinari edited comment on HIVE-22006 at 2/19/20 3:11 PM:
-------------------------------------------------------------
[~klcopp]
I hadn't seen that document, that's very cool to see, thanks!
It hasn't seen more than a typo fix in more than a year though (at least what's
noted in the changelog) - is this tracked somewhere in JIRA (umbrella / per
project / subtasks)?
Nevermind, found the one for Hive at least: HIVE-21348
was (Author: h-vetinari):
[~klcopp]
I hadn't seen that document, that's very cool to see, thanks!
It hasn't seen more than a typo fix in more than a year though (at least what's
noted in the changelog) - is this tracked somewhere in JIRA (umbrella / per
project / subtasks)?
> 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
> Priority: Major
>
> 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
(v8.3.4#803005)
