[ https://issues.apache.org/jira/browse/HIVE-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sankar Hariappan updated HIVE-16171: ------------------------------------ Description: Need to support truncate table for replication. Key points to note. 1. For non-partitioned table, truncate table will remove all the rows from the table. 2. For partitioned tables, need to consider how truncate behaves if truncate a partition or the whole table. 3. Bootstrap load with truncate table must work as it is just loadTable/loadPartition with empty dataset. 4. It is suggested to re-use the alter table/alter partition events to handle truncate. 5. Need to consider the case where insert event happens before truncate table which needs to see their data files through change management. The data files should be recycled to the cmroot path before trashing it. was: Need to support truncate table for replication. Key points to note. 1. For non-partitioned table, truncate table will remove all the rows from the table. 2. For partitioned tables, need to consider how truncate behaves if truncate a partition or the whole table. 3. Bootstrap load with truncate table must work as it is just loadTable/loadPartition with empty dataset. 4. It is suggested to re-use the alter table/alter partition events to handle truncate. > Support replication of truncate table > ------------------------------------- > > Key: HIVE-16171 > URL: https://issues.apache.org/jira/browse/HIVE-16171 > Project: Hive > Issue Type: Sub-task > Components: repl > Affects Versions: 2.1.0 > Reporter: Sankar Hariappan > Assignee: Sankar Hariappan > Labels: DR > Attachments: HIVE-16171.01.patch, HIVE-16171.02.patch, > HIVE-16171.03.patch, HIVE-16171.04.patch > > > Need to support truncate table for replication. Key points to note. > 1. For non-partitioned table, truncate table will remove all the rows from > the table. > 2. For partitioned tables, need to consider how truncate behaves if truncate > a partition or the whole table. > 3. Bootstrap load with truncate table must work as it is just > loadTable/loadPartition with empty dataset. > 4. It is suggested to re-use the alter table/alter partition events to handle > truncate. > 5. Need to consider the case where insert event happens before truncate table > which needs to see their data files through change management. > The data files should be recycled to the cmroot path before trashing it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)