Tencent Cloud TCHouse-D supports integrating Apache Ranger through productized configuration when a Hive Catalog is created, enabling database-, table-, and column-level permission verification for EMR (Hive/Iceberg/Hudi) external tables. After this feature is enabled, database, table, and column access permissions for external tables are uniformly verified by Apache Ranger. You no longer need to manually submit Ranger configuration files to the R&D team for manual configuration, and the entire process can be completed in the console. For related configuration information, see Hive Catalog. Note:
1. Currently, only kernel version 4.1.3 and later support configuring Ranger-Hive Authentication through the console. This is an allowlist feature. To use it, contact us.
2. Currently, database, table, and column permission verification is supported, while row-level permissions and data masking configuration are not yet supported.
3. Currently, only the standard open-source Ranger is supported, and other versions may be incompatible.
4. If HTTPS communication is enabled for your Ranger Admin, upload ranger-policymgr-ssl.xml separately in the configuration file upload section in the console and modify the corresponding parameter settings. For details, see Ranger-Hive Authentication. Operation Guide
2. Click + on the right side of Data Source Management, select Create Hive Catalog, and select Enable Ranger Authentication. After this feature is enabled, database, table, and column permissions for the Hive Catalog are uniformly verified by Apache Ranger.
3. You can choose to reuse the existing configuration of the current cluster or upload a new Ranger configuration file. Uploading ranger-policymgr-ssl.xml through this page is not currently supported. The files that can be uploaded are as follows:
ranger-hive-security.xml: Ranger authentication security configuration
ranger-hive-audit.xml: Ranger audit configuration
4. The system automatically generates the authentication properties. Confirm them on this page. You do not need to enter them again in the Properties field above.
5. After uploading the configuration file, restart the FE nodes for the configuration to take effect. A restart may affect read and write operations, so you are advised to perform it during off-peak business hours.
6. After confirming that all configurations are correct, click OK to complete the Catalog creation. Ranger authentication will take effect after the FE nodes are restarted.
FAQs
Q1: Why Is It Necessary to Restart the FE After the Configuration File Is Uploaded?
Ranger-related configurations are loaded when FE starts up and take effect only after the FE nodes are restarted. To ensure business continuity, a rolling restart is recommended.
Q2: Can Existing Hive Catalogs Be Modified to Use Ranger Authentication?
No. Currently, you can specify Ranger as the authentication method only when creating a new Catalog. Existing Catalogs cannot be changed to use Ranger authentication.
Q3: Where Are the Uploaded Configuration Files Distributed?
When a Catalog is created, the uploaded XML file is automatically distributed to the conf directory of all FE nodes. You can view it in the configuration file section of the console.