| ranger_service_names_mapping | dict(str, str) | A mapping between source to destination ranger services. <p> Note that if a mapping is not given for a service then it will stay the same on the destination. <p> Example: {"cm_hdfs":"dr_hdfs", "cm_hive":"dr_hive"} <br> Default: empty or null, every service name will stay the same on the destination | [optional] |
| ranger_users_mapping | dict(str, str) | A mapping between source to destination ranger usernames. <p> Note that if a mapping is not given for a username then it will stay the same on the destination. <p> Example: {"testuser1":&", "testuser2":&" }quot;testuser1@host.comquot;testuser2@host.com<br> Default: empty or null, every username will stay the same on the destination | [optional] |
| ranger_resources_mapping | dict(str, str) | A mapping between source to destination ranger resources. <p> If a mapping is not given for a resource then it will stay the same on the destination. <p> <b>Example</b>: <br> {"/srcdir1/srcfile1": "/destdir1/destfile1", "src_url.com": "dest_url.com", "source_db": "dest_db", "source_table":"dest_table"} } <br> Default: empty or null, every resource will remain the same on destination <p> If replication contains <b>HDFS Ranger service type</b> and replication is done from on-prem to cloud, then for transforming HDFS Ranger service policies to Cloud policies <b>NO resource mapping is needed</b>. Instead, provide one of the following: #getHdfsToAdlsArgs(), #getHdfsToS3Args(), #getHdfsToGcsArgs() <p> <b>HIVE prefixed based resource URL replacement is supported</b>, but it should be provided in a <b>different mapping</b>, for more info see #getHiveUrlsMapping(). | [optional] |
| hive_urls_mapping | dict(str, str) | Used for <b>HIVE prefixed based resource URL replacement</b>. <p> <b>For instance</b>, if Hive resource URLs on <b>source</b> are: <ul> <li>hdfs://namenodehost:8020/user/hive/warehouse/table1</li> <li>hdfs://namenodehost:8020/user/hive/warehouse/table2</li> </ul> and <b>destination is Amazon S3</b>, and the resource mapping contains the following entry: <br> &": &" quot;hdfs://namenodehost:8020/user/hive/warehousequot;s3a://bucket<br> then after transformation hive urls will be: <ul> <li>s3a://bucket/table1</li> <li>s3a://bucket/table2</li> </ul> Default: empty or null, every HIVE URL will remain the same on destination. | [optional] |
| hdfs_to_adls_args | ApiRangerReplicationHdfsToAdlsArgs | | [optional] |
| hdfs_to_s3_args | ApiRangerReplicationHdfsToS3Args | | [optional] |
| hdfs_to_gcs_args | ApiRangerReplicationHdfsToGcsArgs | | [optional] |