Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
DataArts Lake Formation
DataArts Lake Formation
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- Developer Guide
-
API Reference
- Before You Start
- API Overview
- API Calling
-
API
-
Console
- Instance Management
- Job Management
-
Service Authorization Management
- Granting Permissions for Accessing Other Cloud Services
- Querying Cloud Service Access Permissions
- Registering a Tenant Agreement
- Querying whether a Tenant Has Registered an Agreement
- Deleting a Tenant Agreement
- Registering a Tenant Agreement
- Querying whether a Tenant Has Registered an Agreement
- Deleting a Tenant Agreement
- Querying the Current System Agreement
- OBS Management
- Access Management
- Specification Management
- Quota Management Service
- Tag Management Service
- Agency Management
- Alarm Management
- Metadata Management
- Location
-
LakeCat
- Function Management
- Catalog Management
- Database Management
- Table Management
- Data Table Statistics
- Zone-based Management
- Partition Statistics
- Authorization Management
- User Group Management
- Metadata Statistics
-
Role Management
- Creating a Role
- Listing Roles on Different Pages by Condition
- Deleting a Role
- Obtaining a Role
- Modifying a Role
- Listing All Role Names
- Querying the Users or User groups Under a Role
- Adding One or More Users or User Groups to a Role
- Removing One or More Users or User Groups from a Role
- Updating the Entities in a Role
- Credential Management
- Configuration Management
- User
-
Console
- Application Examples
- Permissions and Supported Actions
- Appendix
- FAQs
- General Reference
On this page
Show all
Help Center/
DataArts Lake Formation/
Best Practices/
Configuring Interconnection Between Open Source Hive and LakeFormation/
Interconnecting Hive with LakeFormation
Copied.
Interconnecting Hive with LakeFormation
- Add the following content to the hive-site.xml file in the conf directory in the Hive server installation environment (replace some parameter values as prompted):
<property> <name>hive.metastore.session.client.class</name> <value>com.huawei.cloud.dalf.lakecat.client.hiveclient.LakeCatMetaStoreClient</value> </property> <property> <name>lakeformation.project.id</name> <value>****</value> </property> <property> <name>lakeformation.instance.id</name> <value>LakeFormation instance ID</value> </property> <!--AK information for LakeFormation IAM authentication. This parameter is optional. Ignore it if you plan to use the custom authentication information obtaining class.--> <property> <name>lakeformation.authentication.access.key</name> <value>AK</value> </property> <!--SK information for LakeFormation IAM authentication. This parameter is optional. Ignore it if you plan to use the custom authentication information obtaining class.--> <property> <name>lakeformation.authentication.secret.key</name> <value>SK</value> </property> <!--SecurityToken for accessing LakeFormation IAM authentication information. This parameter is optional. If a permanent AK/SK or a custom authorizer information obtaining class is used, skip this parameter.--> <property> <name>lakeformation.authentication.security.token</name> <value>SecurityToken information</value> </property> <property> <name>fs.obs.impl</name> <value>org.apache.hadoop.fs.obs.OBSFileSystem</value> </property> <property> <name>fs.AbstractFileSystem.obs.impl</name> <value>org.apache.hadoop.fs.obs.OBS</value> </property> <property> <name>fs.obs.endpoint</name> <value>Endpoint information</value> </property> <property> <name>fs.obs.credentials.provider</name> <value>com.huawei.cloud.dalf.lakecat.client.obs.LakeFormationObsCredentialProvider</value> </property> <property> <name>fs.obs.impl.disable.cache</name> <value>true</value> </property> <property> <name>dfs.namenode.acls.enabled</name> <value>false</value> </property> <!--Name of the LakeFormation catalog to be connected. This parameter is optional. If this parameter is not set, the Hive catalog is connected instead. The value of this parameter is for reference only.--> <property> <name>lakecat.catalogname.default</name> <value>hive</value> </property>
NOTE:
- lakeformation.project.id indicates the project ID. For how to obtain a project ID, see Obtaining a Project ID.
- lakeformation.instance.id indicates the LakeFormation instance ID. For how to obtain the ID of a LakeFormation instance, see How Do I Obtain the ID of a LakeFormation Instance?
- For how to obtain an AK/SK, see How Do I Obtain the AK/SK?
- For how to obtain a securityToken, see Obtaining a Temporary Access Key and SecurityToken Through a Token.
- Restart the Hive service.
- Log in to the Hive client and run the following command:
show tables;
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot