-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/47353/#review133391
-----------------------------------------------------------




metastore/src/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java (line 
650)
<https://reviews.apache.org/r/47353/#comment197771>

    Don't use normalizeIdentifier() since that does trim() which will be 
incorrect. Use .toLowerCase()



metastore/src/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java 
(lines 694 - 695)
<https://reviews.apache.org/r/47353/#comment197775>

    Ideally this should happen in a single transaction on backend db. If you 
are not planning to address that in this patch, please leave a TODO in here.


- Ashutosh Chauhan


On May 13, 2016, 7:17 p.m., Aihua Xu wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/47353/
> -----------------------------------------------------------
> 
> (Updated May 13, 2016, 7:17 p.m.)
> 
> 
> Review request for hive and Chaoyu Tang.
> 
> 
> Repository: hive-git
> 
> 
> Description
> -------
> 
> HIVE-13616: Investigate renaming a table without invalidating the column stats
> 
> 
> Diffs
> -----
> 
>   metastore/src/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java 
> 0652b9db1a4224262611ff9258e871647442cfeb 
>   ql/src/test/queries/clientpositive/rename_table_update_column_stats.q 
> PRE-CREATION 
>   ql/src/test/results/clientpositive/rename_table_update_column_stats.q.out 
> PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/47353/diff/
> 
> 
> Testing
> -------
> 
> Tests have been run and the failed tests don't seem to be related. 
> 
> To carry over the column stats during renaming the table, the patch 
> 1. Save affected column stats
> 2. Rename the table
> 3. Write the saved column stats for the new table.
> 
> In this order, column stats will find the foreign key when writing in 3).
> 
> 
> Thanks,
> 
> Aihua Xu
> 
>

Reply via email to