tencent cloud

Cloud Infinite

문서Cloud InfiniteAPI DocumentationIntelligent Search MetaInsightDataset ManagementBucket BindingBinding Buckets and Datasets

Binding Buckets and Datasets

다운로드
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-09-08 16:24:27
AI 번역

Feature Description

Bind a COS bucket to a Dataset. After binding, the system performs near-real-time incremental tracking scans on new files added to the bucket, processes the files based on the Dataset's search template, and extracts file metadata for indexing. After metadata indexes are established for files in this way, you can use the intelligent search query API to query and analyze data.

Authorization Description

When using a sub-account, add the ci:CreateDatasetBinding permission to the action of the authorization policy. For all operation APIs supported by Cloud Infinite, see CI action.

Use Limits

The maximum number of bindings per dataset is 10.
Currently, only buckets in the Beijing and Shanghai regions can be bound to datasets.
Files in COS encrypted buckets cannot be read, and metadata indexes cannot be created for them.
Cross-account COS buckets are not supported. Only COS buckets under the current account can be bound.
For more usage limitations, see Usage Limits.

Request

Request sample

POST /datasetbinding HTTP/1.1
Host: <AppId>.ci.ap-jakarta.myqcloud.com
Authorization: Auth String
Content-Length: 123
Content-Type: application/json
Accept: application/json
Note:
Authorization: A request header that carries authentication information and is used to verify the legitimacy of the request. For details, see Request Signature.

Request header

This API only uses common request headers. For details, see Common Request Headers.

Request body

{
    "DatasetName": "test",
    "URI": "cos://examplebucket-1250000000/test_data",
    "Mode": 0
}

Request Parameter

Parameter Name
Description
Type
Required
DatasetName
Dataset name, unique within the same account. You can query it through the console or API.
String
Yes
URI
Resource identifier field. Indicates the resource to be bound with the dataset. Currently, COS Buckets and directories within Buckets are supported, and you can add a prefix to bind a directory. Field rule: cos://<BucketName>/prefix, where BucketName indicates the COS Bucket name. Example: cos://examplebucket-1250000000 can be used to directly bind a Bucket. You can also add a prefix, where prefix represents a path. Example: cos://examplebucket-1250000000/test_data.
String
Yes
Mode
After the binding is established, how to extract file index features. Valid values:
0: Indexes are created only for incremental files.
1: Indexes are created for existing files in the bucket while indexes are created for incremental files. The time required to index existing files depends on the number of existing files.
The default value is 0.
Integer
No

Response

Response Headers

This API only returns common response headers. For details, see Common Response Headers.

Response Body

{
	"Binding": {
		"DatasetName": "test",
        "URI": "cos://examplebucket-1250000000/test_data",
		"State": "Running",
		"StockState": "Indexing",
        "CreateTime": "2025-04-09T19:38:08.454310276+08:00",
		"UpdateTime": "2025-04-09T19:38:08.454310276+08:00"
	},
	"RequestId": "NWFjMzQ0MDZfOTBmYTUwXzZkZV8z****"
}
The specific data content of the response body is as follows:
Parameter Name
Type
Description
Binding
Container
Binding information
RequestId
String
Request ID.
Binding node content:
Parameter Name
Type
Description
DatasetName
String
Data set name
URI
String
Resource identifier field. Indicates the resource to be bound with the dataset. Currently, COS Buckets and directories within Buckets are supported, and you can add a prefix to bind a directory. Field rule: cos://<BucketName>/prefix, where BucketName indicates the COS Bucket name. Example: cos://examplebucket-1250000000 can be used to directly bind a Bucket. You can also add a prefix, where prefix represents a path. Example: cos://examplebucket-1250000000/test_data.
State
String
Status of the binding relationship between the dataset and the COS Bucket. Valid value: Running: The binding relationship is running.
StockState
String
Status of the existing index corresponding to the currently bound Bucket. Valid values:
NoIndexing: Existing files are not indexed.
Indexing: Existing file indexes are being created.
Success: Existing file indexes have been created.
CreateTime
String
Timestamp of the creation time of the binding relationship between the dataset and the COS Bucket, in RFC3339Nano format
UpdateTime
String
The timestamp of the modification time of the binding relationship between the dataset and the COS Bucket, in RFC3339Nano format.
After a binding relationship is created, if it has not been paused or restarted, the timestamp of the binding relationship modification time is the same as the timestamp of the binding relationship creation time.

이전 주제: Listing Datasets다음 주제: Unbinding a Bucket from a Dataset

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백

키워드로 검색
    Enter keywords to search documentation