[jira] [Resolved] (HIVE-25372) [Hive] Advance write ID for remaining DDLs

["Kishen Das (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-25372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kishen Das resolved HIVE-25372.
-------------------------------
    Resolution: Fixed

> [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
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> 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)