[
https://issues.apache.org/jira/browse/HIVE-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sankar Hariappan updated HIVE-16171:
------------------------------------
Attachment: HIVE-16171.06.patch
Patch: 06
- Passed the truncate op type from truncate-table itself. So, added a
notifyEvent call from truncate_table itself.
- Moved the alter stats logic to megastore itself along with truncate_table
flow.
- Modified truncate table/partition REPL LOAD logic to perform only Truncate
task.
> 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.2.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, HIVE-16171.05.patch,
> HIVE-16171.06.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)
