hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16171) Support truncate table for replication
Date Fri, 10 Mar 2017 08:31:04 GMT

     [ 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 drop a partition or rename
the partition or so.

Following gaps are noticed with Truncate Table:
1. Incremental replication for truncate table does’t work.
2. After bootstrap load with a partition truncated and then incremental load with insert into
same truncated partition is not getting replicated. But insert into new partition works and
also insert into non-partitioned table works even after truncate. If we drop the truncated
partition and insert into same partition and does incremental load, it works.

  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 drop a partition or rename
the partition or so.


> Support truncate table for replication
> --------------------------------------
>
>                 Key: HIVE-16171
>                 URL: https://issues.apache.org/jira/browse/HIVE-16171
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>
> 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 drop a partition
or rename the partition or so.
> Following gaps are noticed with Truncate Table:
> 1. Incremental replication for truncate table does’t work.
> 2. After bootstrap load with a partition truncated and then incremental load with insert
into same truncated partition is not getting replicated. But insert into new partition works
and also insert into non-partitioned table works even after truncate. If we drop the truncated
partition and insert into same partition and does incremental load, it works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message