[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source via alter table.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Resolution: Fixed Fix Version/s: 4.0.0 Status: Resolved (was: Patch Available) Thanks [~anishek] and [~ashutosh.bapat] for the review! 03.patch committed to master. > Disable conversion of managed table to external and vice versa at source via > alter table. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Fix For: 4.0.0 > > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch, > HIVE-21500.03.patch > > Time Spent: 6h 20m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source via alter table.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Summary: Disable conversion of managed table to external and vice versa at source via alter table. (was: Disable conversion of managed table to external and vice versa at source.) > Disable conversion of managed table to external and vice versa at source via > alter table. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch, > HIVE-21500.03.patch > > Time Spent: 6h 20m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Patch Available (was: Open) 03.patch addressed comments from [~ashutosh.bapat]. > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch, > HIVE-21500.03.patch > > Time Spent: 6h > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Open (was: Patch Available) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch, > HIVE-21500.03.patch > > Time Spent: 6h > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Attachment: HIVE-21500.03.patch > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch, > HIVE-21500.03.patch > > Time Spent: 6h > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Open (was: Patch Available) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Patch Available (was: Open) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Attachment: HIVE-21500.02.patch > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Attachment: (was: HIVE-21500.02.patch) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Patch Available (was: Open) Fixed checkstyle issues. > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Attachment: HIVE-21500.02.patch > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch, HIVE-21500.02.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Open (was: Patch Available) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch > > Time Spent: 10m > Remaining Estimate: 0h > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HIVE-21500: -- Labels: DR Replication pull-request-available (was: DR Replication) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication, pull-request-available > Attachments: HIVE-21500.01.patch > > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Attachment: HIVE-21500.01.patch > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication > Attachments: HIVE-21500.01.patch > > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Status: Patch Available (was: Open) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication > Attachments: HIVE-21500.01.patch > > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21500) Disable conversion of managed table to external and vice versa at source.
[ https://issues.apache.org/jira/browse/HIVE-21500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21500: Summary: Disable conversion of managed table to external and vice versa at source. (was: Disable conversion of managed table to external at source.) > Disable conversion of managed table to external and vice versa at source. > - > > Key: HIVE-21500 > URL: https://issues.apache.org/jira/browse/HIVE-21500 > Project: Hive > Issue Type: Sub-task >Affects Versions: 4.0.0 >Reporter: Sankar Hariappan >Assignee: Sankar Hariappan >Priority: Major > Labels: DR, Replication > > Couple of scenarios for Hive2 to Hive3(strict managed tables enabled) > replication where managed table is converted to external at source. > *Scenario-1: (ACID/MM table converted to external at target)* > 1. Create non-ACID ORC format table. > 2. Insert some rows > 3. Replicate this create event which creates ACID table at target (due to > migration rule). Each insert event adds transactional metadata in HMS > corresponding to the current table. > 4. Convert table to external table using ALTER command at source. > *Scenario-2: (External table at target changes table location)* > 1. Create non-ACID avro format table. > 2. Insert some rows > 3. Replicate this create event which creates external table at target (due to > migration rule). The data path is chosen under default external warehouse > directory. > 4. Convert table to external table using ALTER command at source. > It is unable to convert an ACID table to external table at target. Also, it > is hard to detect what would be the table type at target when perform this > ALTER table operation at source. > So, it is decided to disable conversion of managed table at source (Hive2) to > EXTERNAL or vice-versa if the DB is enabled for replication and strict > managed is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
