[jira] [Updated] (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:all-tabpanel ] mahesh kumar behera updated HIVE-20967: --- Resolution: Fixed Status: Resolved (was: Patch Available) [^HIVE-20967.05.patch] committed to master. Thanks [~ashutosh.bapat] for fixing 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-20967.04.patch, HIVE-20967.05.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: HIVE-20967.05.patch Status: Patch Available (was: In Progress) Addressed [~maheshk114]'s recent comments. > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-20967.04.patch, HIVE-20967.05.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Status: In Progress (was: Patch Available) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-20967.04.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: (was: HIVE-21678.02.patch) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-20967.04.patch > > Time Spent: 1h > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: HIVE-20967.04.patch Status: Patch Available (was: In Progress) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-20967.04.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Status: In Progress (was: Patch Available) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: HIVE-20967.03.patch Status: Patch Available (was: In Progress) Patch with fixes for ptest failures in the previous run. > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Status: In Progress (was: Patch Available) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-20967.03.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: HIVE-20967.03.patch Status: Patch Available (was: In Progress) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-20967.03.patch, > HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Status: In Progress (was: Patch Available) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Status: In Progress (was: Patch Available) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: HIVE-21678.02.patch Status: Patch Available (was: In Progress) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch, HIVE-21678.02.patch > > Time Spent: 20m > Remaining Estimate: 0h > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] ASF GitHub Bot updated HIVE-20967: -- Labels: DR pull-request-available (was: DR) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR, pull-request-available > Attachments: HIVE-20967.01.patch > > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Attachment: HIVE-20967.01.patch Status: Patch Available (was: Open) > 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: Ashutosh Bapat >Priority: Minor > Labels: DR > Attachments: HIVE-20967.01.patch > > > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Description: 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. - Do not allow this conversion on source of replication if strict.managed is false. 2. Alter table or partition that changes the location. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). was: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). > 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: Ashutosh Bapat >Priority: Minor > 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. > - Do not allow this conversion on source of replication if strict.managed is > false. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Description: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). was: 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. So, don't dump (and replicate) that event. Anyway, any event generated on the source on such an ALTERed table won't be dumped (and replicated) to the target. 2. Alter table or partition that changes the location. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). > 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: Ashutosh Bapat >Priority: Minor > 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. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Description: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). was: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. > 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: Ashutosh Bapat >Priority: Minor > 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. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Description: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. was: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external tables, if location is changed at source, then location should be updated only for the given object (table or partition, not all partitions). > 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: Ashutosh Bapat >Priority: Minor > 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. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Ashutosh Bapat updated HIVE-20967: -- Description: 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. So, don't dump (and replicate) that event. Anyway, any event generated on the source on such an ALTERed table won't be dumped (and replicated) to the target. 2. Alter table or partition that changes the location. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). was: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external partitioned tables, if location is changed at source, the the location should be changed for the table and any partitions which reside within the table location, but not for the partitions which are not within the table location. (may be we just need the test). > 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: Ashutosh Bapat >Priority: Minor > 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. So, don't dump (and replicate) that event. Anyway, any > event generated on the source on such an ALTERed table won't be dumped (and > replicated) to the target. > 2. Alter table or partition that changes the location. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external partitioned tables, if location is changed at source, the the > location should be changed for the table and any partitions which reside > within the table location, but not for the partitions which are not within > the table location. (may be we just need the test). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Description: 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. - For managed tables at source, the table location shouldn't be changed for the given non-partitioned table and partition location shouldn't be changed for partitioned table as alter event doesn't capture the new files list. So, it may cause data inconsistsency. So, if database is enabled for replication at source, then alter location on managed tables should be blocked. - For external tables, if location is changed at source, then location should be updated only for the given object (table or partition, not all partitions). was: 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. > 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: Minor > 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. > - For managed tables at source, the table location shouldn't be changed for > the given non-partitioned table and partition location shouldn't be changed > for partitioned table as alter event doesn't capture the new files list. So, > it may cause data inconsistsency. So, if database is enabled for replication > at source, then alter location on managed tables should be blocked. > - For external tables, if location is changed at source, then location should > be updated only for the given object (table or partition, not all partitions). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Description: 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. was: 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. > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Priority: Minor (was: Major) > 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: Minor > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Priority: Major (was: Minor) > 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 HDP 2.6.5 may cause conflicts in HDP 3.0 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)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Description: Some of the events from Hive2 may cause conflicts in Hive3 ( 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. was: Some of the events from HDP 2.6.5 may cause conflicts in HDP 3.0 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. > 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 ( 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)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Description: 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. was: Some of the events from Hive2 may cause conflicts in Hive3 ( 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. > 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)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Summary: Handle alter events when replicate to cluster with hive.strict.managed.tables enabled. (was: CLONE - REPL DUMP to dump the default warehouse directory of source.) > 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: Minor > Labels: DR > > The default warehouse directory of the source is needed by target to detect > if DB or table location is set by user or assigned by Hive. > Using this information, REPL LOAD will decide to preserve the path or move > data to default managed table's warehouse directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Sankar Hariappan updated HIVE-20967: Description: Some of the events from HDP 2.6.5 may cause conflicts in HDP 3.0 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. was: The default warehouse directory of the source is needed by target to detect if DB or table location is set by user or assigned by Hive. Using this information, REPL LOAD will decide to preserve the path or move data to default managed table's warehouse directory. > 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: Minor > Labels: DR > > Some of the events from HDP 2.6.5 may cause conflicts in HDP 3.0 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)
