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

Lefty Leverenz commented on HIVE-12767:
---------------------------------------

Here's where the documentation belongs:

* [Parquet | https://cwiki.apache.org/confluence/display/Hive/Parquet]
* [Configuration Properties -- Parquet | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-Parquet]
 for *parquet.mr.int96.enable.utc.write.zone* 
* [Table Properties | 
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-listTableProperties]

Question:  Shouldn't the config name start with "hive." as in 
"hive.parquet.mr.int96.enable.utc.write.zone"?

> Implement table property to address Parquet int96 timestamp bug
> ---------------------------------------------------------------
>
>                 Key: HIVE-12767
>                 URL: https://issues.apache.org/jira/browse/HIVE-12767
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 1.2.1, 2.0.0
>            Reporter: Sergio Peña
>            Assignee: Barna Zsombor Klara
>              Labels: TODOC2.2
>             Fix For: 2.2.0
>
>         Attachments: HIVE-12767.10.patch, HIVE-12767.11.patch, 
> HIVE-12767.3.patch, HIVE-12767.4.patch, HIVE-12767.5.patch, 
> HIVE-12767.6.patch, HIVE-12767.7.patch, HIVE-12767.8.patch, 
> HIVE-12767.9.patch, TestNanoTimeUtils.java
>
>
> Parque timestamps using INT96 are not compatible with other tools, like 
> Impala, due to issues in Hive because it adjusts timezones values in a 
> different way than Impala.
> To address such issues. a new table property (parquet.mr.int96.write.zone) 
> must be used in Hive that detects what timezone to use when writing and 
> reading timestamps from Parquet.
> The following is the exit criteria for the fix:
> * Hive will read Parquet MR int96 timestamp data and adjust values using a 
> time zone from a table property, if set, or using the local time zone if it 
> is absent. No adjustment will be applied to data written by Impala.
> * Hive will write Parquet int96 timestamps using a time zone adjustment from 
> the same table property, if set, or using the local time zone if it is 
> absent. This keeps the data in the table consistent.
> * New tables created by Hive will set the table property to UTC if the global 
> option to set the property for new tables is enabled.
> ** Tables created using CREATE TABLE and CREATE TABLE LIKE FILE will not set 
> the property unless the global setting to do so is enabled.
> ** Tables created using CREATE TABLE LIKE <OTHER TABLE> will copy the 
> property of the table that is copied.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to