hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wuchang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-20398) [Hive Metastore] Add a Configuration Item for Metastore Server to Skip the HDFS Data Modification
Date Fri, 24 Aug 2018 00:47:00 GMT

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

wuchang commented on HIVE-20398:
--------------------------------

[~alangates] , [~thejas] @ would you please give me some suggestions?

 

> [Hive Metastore] Add a Configuration Item for Metastore Server to Skip the HDFS Data
Modification
> -------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-20398
>                 URL: https://issues.apache.org/jira/browse/HIVE-20398
>             Project: Hive
>          Issue Type: Task
>          Components: Metastore
>    Affects Versions: 2.3.2
>            Reporter: wuchang
>            Assignee: wuchang
>            Priority: Major
>
> 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 
> {code:java}
> hive.metastore.skip.hdfs=false{code}
> 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.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message