检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
检测到您已登录华为云国际站账号，为了您更好的体验，建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
OBS Management Querying the OBS Buckets Querying the OBS Bucket Objects Parent topic: Console
Authorizing an OBS Path to LakeFormation Function This API is used to authorize LakeFormation to read and write OBS paths.
Querying the List of OBS Paths Authorized to LakeFormation Function Querying the list of OBS paths authorized to LakeFormation. URI GET /v1/authorize-location Table 1 Query Parameters Parameter Mandatory Type Description location No String OBS path.
Canceling OBS Path Authorization in Batches from LakeFormation Function This API cancels the authorization of OBS paths in batches from LakeFormation. Note that the authorization of OBS paths already utilized by metadata cannot be canceled.
Parent topic: OBS Management
Parent topic: OBS Management
Object Storage Service (OBS) The actual service data mapped by LakeFormation metadata is stored in the directories and files of the OBS parallel file system.
Location Authorizing an OBS Path to LakeFormation Querying the List of OBS Paths Authorized to LakeFormation Canceling OBS Path Authorization in Batches from LakeFormation Parent topic: Console
OBS OperateAccess: provides the storage function for your instance. OBS AccessLabel: allows your instance to control permissions by using tagging. OBS Bucket Lifecycle: This permission is required to manage the lifecycle of instances.
Tenant resources: LakeFormation needs to read user group and user information, create and delete OBS file directories, and access OBS tag permission APIs. Recommended Security Configuration N/A Infrastructure Security LakeFormation instances run in a cross-AZ cluster.
The data to be discovered has been uploaded to the OBS parallel file system. That is, the data has been uploaded from S3 or HDFS to the planned path of the OBS parallel file system in the region where the LakeFormation instance is located.
services such as OBS and TMS.
Creating a Metadata Storage Path The data files and directories mapped to LakeFormation metadata are stored in the OBS parallel file system. Before creating LakeFormation metadata, you need to create an OBS parallel file system for data storage.
OBS nodes should be separately deployed based on the storage-compute decoupling architecture.
The selected location must start with obs:// and must contain one storage object. For example, select obs://lakeformation-test/catalog1. If no suitable parallel file system is available, click go to OBS and create one.
Location doesn't exist in the OBS Parallel File Systems The path does not exist in the OBS parallel file system. Folder obs://xxxx/yyyy/ is not empty in the OBS During table creation, the OBS directory must be empty.
You can select the target permission information using OBS Authorization Path, Authorization Entity, Entity Type, and Entity Source in the upper right corner as filters. View the data authorization information in the displayed list.
The selected location must start with obs:// and must contain one storage object. For example, select obs://lakeformation-test/catalog1/database1/table1. If no suitable parallel file system is available, click go to OBS and create one.
OBS Management OBS bucket management APIs, which allow you to query OBS buckets and objects. With these APIs, you can obtain the OBS information needed for configuring the storage path of metadata.
If files are also deleted when metadata is deleted, the metadata is moved to the recycle bin (OBS path lake-formation-trash-dir/table_id) of the corresponding OBS bucket. Parent topic: Metadata Management
