[
https://issues.apache.org/jira/browse/HIVE-23995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190684#comment-17190684
]
Ádám Szita commented on HIVE-23995:
-----------------------------------
This commit has removed HiveStrictManagedMigration.java (and the corresponding
test) but I don't see its functionality being ported to anywhere. AFAIK it was
not really related to replication but we use this class to prepare Hive
warehouse between major upgrades. Was there a particular reason this had to be
removed?
cc:
[~thejas] [~jdere]
> Don't set location for managed tables in case of replication
> ------------------------------------------------------------
>
> Key: HIVE-23995
> URL: https://issues.apache.org/jira/browse/HIVE-23995
> Project: Hive
> Issue Type: Task
> Reporter: Aasha Medhi
> Assignee: Aasha Medhi
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-23995.01.patch, HIVE-23995.02.patch,
> HIVE-23995.03.patch, HIVE-23995.04.patch, HIVE-23995.05.patch,
> HIVE-23995.06.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Managed table location should not be set
> Migration code of replication should be removed
> add logging to all ack files
> set hive.repl.data.copy.lazy to true
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
