Atlas replication policies (technical preview)
You can create Atlas replication policies to replicate the metadata and data lineage of all the Hive external tables, Iceberg tables, and any other Atlas supported entities between CDP Private Cloud Base 7.1.9 SP1 clusters using Cloudera Manager 7.11.3 CHF7 or higher. During an Atlas replication policy run, Replication Manager exports the Atlas metadata and data lineage to a staging directory in the target cluster, and then imports into the target cluster. You can enter the required staging directory during the replication policy creation process.
You can use one of the following methods to replicate Atlas metadata and data lineage for Hive external tables and Iceberg tables:
- Create Atlas replication policy to replicate the metadata and data lineage of all the Hive external tables, Iceberg tables, and any other Atlas supported entities in the source cluster to the target cluster.
- Choose during the Hive external table replication policy creation or edit process to replicate the metadata associated with the chosen Hive external tables.
- Choose during the Iceberg replication policy creation or edit process to replicate the metadata associated with the chosen Iceberg tables.
Some use cases where you can use Atlas replication policies are:
- Disaster recovery scenarios. You can back up the Atlas metadata and data lineage periodically, and restore it to the same cluster or a different cluster as required.
- High availability scenarios.
- Prevent accidental access of Ranger policies and Atlas metadata for specific Hive external tables and Iceberg tables. You can accomplish this by running both Ranger, Hive external table, and Iceberg replication policies on the required tables in the disaster-recovery cluster. The replication policies replicate the data and its associated metadata and access controls.