[
https://issues.apache.org/jira/browse/HIVE-19512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mahesh kumar behera updated HIVE-19512:
---------------------------------------
Description: The move task does meta store operations. If the meta hive
object is shared between Move tasks, then meta store throwing out of sequence
error. So each move task should have a hive object of its own. (was: * add a
parameter at db level to identify if its a source of replication. beacon will
set this.
* Enable CM root only for databases that are a source of a replication policy,
for other db's skip the CM root functionality.
* prevent database drop if the parameter indicating its source of a
replication, is set.
* as an upgrade to this version, beacon should set the property on all
existing database policies, in affect.
* the parameter should be of the form . – repl.source.for : List < policy ids
>)
> create thread local hive object for Movetask
> --------------------------------------------
>
> Key: HIVE-19512
> URL: https://issues.apache.org/jira/browse/HIVE-19512
> Project: Hive
> Issue Type: Task
> Components: Hive, HiveServer2, repl
> Affects Versions: 3.1.0
> Reporter: mahesh kumar behera
> Assignee: mahesh kumar behera
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.1.0
>
>
> The move task does meta store operations. If the meta hive object is shared
> between Move tasks, then meta store throwing out of sequence error. So each
> move task should have a hive object of its own.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
