You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2018/12/18 08:34:00 UTC
[jira] [Commented] (HIVE-20967) Handle alter events when replicate
to cluster with hive.strict.managed.tables enabled.
[ https://issues.apache.org/jira/browse/HIVE-20967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723832#comment-16723832 ]
Sankar Hariappan commented on HIVE-20967:
-----------------------------------------
It seems, this JIRA is completed but need to add tests to verify it.
> Handle alter events when replicate to cluster with hive.strict.managed.tables enabled.
> --------------------------------------------------------------------------------------
>
> Key: HIVE-20967
> URL: https://issues.apache.org/jira/browse/HIVE-20967
> Project: Hive
> Issue Type: Sub-task
> Components: repl
> Affects Versions: 4.0.0
> Reporter: mahesh kumar behera
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: DR
>
> Some of the events from Hive2 may cause conflicts in Hive3 (hive.strict.managed.tables=true) when applied. So, need to handle them properly.
> 1. Alter table to convert non-acid to acid.
> This event should be no-op as the table in target might be already acid or MM or external table.
> 2. Alter table or partition that changes the location.
> Once the table is moved to managed table warehouse directory, the location shouldn't be changed.
> 3. Alter database that changes the location.
> Once the database is moved to managed table warehouse directory, the location shouldn't be changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)