Understanding how DDL commands affect Hive tables during replication

The following scenarios explain how the tables are affected when you use the drop table and truncate table DDL commands on Hive tables in a replication policy:

• You drop a table in a replication policy after the policy has run at least once. The table remains on the destination cluster and does not get dropped during subsequent replication runs.
• You drop a table on the destination cluster and the table is still included in the replication job. The table is re-created on the destination during the next replication job.
• You drop a table partition or index on the source cluster. The next replication job drops it on the destination cluster.
• You truncate a table, and the Delete Policy for the replication job is set to Delete to Trash or Delete Permanently. The corresponding data files are deleted on the destination during the next replication job.