Description
When we are conducting the hive upgrading, we have following use case:
We want to sync the operations between two metastore server (A and B) by thrift api, but both them are based on the same HDFS. So, for operations like drop_partitions, drop_table, insert_overwrite, create_table which will cause the data modification in HDFS, these HDFS data modification will be executed twice, which is not what we want, instead, we want it to be executed by only Metastore Server A. For metastore Server B, It should be configured to only change his metadata, but skipping the HDFS data modification.
So, we need a switch to control this.
like
hive.metastore.skip.hdfs=false
whose default value is false. When its value is true, the metastore server will only conduct the metadata modification, but skip the HDFS data modification.
Attachments
Issue Links
- is related to
-
HIVE-20346 [Hive Upgrade] A rollback script is necessary when upgrade hive
- In Progress
- relates to
-
HIVE-20346 [Hive Upgrade] A rollback script is necessary when upgrade hive
- In Progress