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

Kishen Das commented on HIVE-25372:
-----------------------------------

[https://github.com/apache/hive/pull/2524] 

> [Hive] Advance write ID for remaining DDLs
> ------------------------------------------
>
>                 Key: HIVE-25372
>                 URL: https://issues.apache.org/jira/browse/HIVE-25372
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2
>            Reporter: Kishen Das
>            Assignee: Kishen Das
>            Priority: Major
>
> We guarantee data consistency for table metadata, when serving data from the 
> HMS cache. HMS cache relies on Valid Write IDs to decide whether to serve 
> from cache or refresh from the backing DB and serve, so we have to ensure we 
> advance write IDs during all alter table flows. We have to ensure we advance 
> the write ID for below DDLs.
> AlterTableSetOwnerAnalyzer.java 
> AlterTableSkewedByAnalyzer.java
> AlterTableSetSerdeAnalyzer.java
> AlterTableSetSerdePropsAnalyzer.java
> AlterTableUnsetSerdePropsAnalyzer.java
> AlterTableSetPartitionSpecAnalyzer
> AlterTableClusterSortAnalyzer.java
> AlterTableIntoBucketsAnalyzer.java
> AlterTableConcatenateAnalyzer.java
> AlterTableCompactAnalyzer.java
> AlterTableSetFileFormatAnalyzer.java
> AlterTableSetSkewedLocationAnalyzer.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to