[HIVE-25372] [Hive] Advance write ID for remaining DDLs

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: HiveServer2
• Labels: pull-request-available
• Assignee: Kishen Das
• Reporter: Kishen Das
• Created: 22/Jul/21 16:49
• Updated: 26/Aug/21 16:00
• Resolved: 17/Aug/21 16:48

Description

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

Issue Links

• links to: GitHub Pull Request #2524