Merges two or more face clustering groups into one face clustering group.
Operation description
- Before you call this operation, make sure that you are familiar with the billing of Intelligent Media Management (IMM).****
- Before you call this operation, make sure that you have called the CreateFigureClusteringTask operation to cluster all faces in the dataset.
- If you merge unrelated groups, the feature values of the target groups are affected. As a result, the incremental data may be inaccurately grouped when you create a face clustering task.
- This operation is an asynchronous operation. After a task is executed, the task information is retained only for seven days and cannot be retrieved when the retention period elapses. You can call the GetTask or ListTasks operation to query information about the task.`` If you specify Notification , you can obtain information about the task based on notifications.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
imm:CreateFigureClustersMergingTask | create | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ProjectName | string | Yes | The name of the project. For more information, see CreateProject . | immtest |
DatasetName | string | Yes | The name of the dataset. For more information, see Create a dataset. | dataset001 |
From | string | No | The ID of the source group. You must specify either From or Froms, but not both. | Cluster-2ab85905-23ba-4632-b2d8-1c21cfe**** |
To | string | Yes | The ID of the destination clustering group. | Cluster-4a3a71c1-c092-4788-8826-2f65d17**** |
UserData | string | No | The custom data, which is returned in an asynchronous notification and facilitates notification management. The maximum length is 2,048 bytes. | {"ID": "user1","Name": "test-user1","Avatar": "http://example.com?id=user1"} |
Tags | object | No | The custom tags, which can be used to search for and filter asynchronous tasks. | {"key":"val"} |
Froms | array | No | The IDs of source clustering groups. You must specify either From or Froms, but not both. You can specify up to 100 task IDs. | |
string | No | The ID of a single source clustering group. | Cluster-2ab85905-23ba-4632-b2d8-1c21cfe**** | |
Notification | Notification | No | The notification message configurations. For more information, see the "Metadata indexing" section of the Asynchronous message examples topic. |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "CA995EFD-083D-4F40-BE8A-BDF75FF****",
"TaskId": "92376fbb-171f-4259-913f-705f7ee0****",
"EventId": "0ED-1Bz8z71k5TtsUejT4UJ16E****"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2023-04-03 | The request parameters of the API has changed | View Change Details |
2023-03-09 | The request parameters of the API has changed | View Change Details |
2022-08-16 | The request parameters of the API has changed | View Change Details |
2022-08-16 | The request parameters of the API has changed | View Change Details |