This operation performs a batch index of object metadata by processing input files for tasks such as label detection, face detection, and location detection. The object metadata is then indexed into a dataset to support various data retrieval methods.
Operation description
Before you use this API, review the billing methods and pricing of Intelligent Media Management.
For a list of supported data processing tasks, see Define a workflow.
The files to be indexed are subject to limits on their total number and size. For more information about dataset limits, see Limits. For information about how to create a dataset, see the parameter descriptions.
For information about the regions that support file indexing, see the dataset and index information in Limits.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
imm:BatchIndexFileMeta |
create |
*Dataset
|
None | None |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| ProjectName |
string |
Yes |
The project name. For more information about how to obtain the project name, see Create a project. |
test-project |
| DatasetName |
string |
Yes |
The dataset name. For more information about how to obtain the dataset name, see Create a dataset. |
test-dataset |
| Files |
array |
Yes |
A list of OSS files. This is an array in JSON format that can contain up to 100 files. |
|
| InputFile |
No |
The struct of an OSS file. |
||
| UserData |
string |
No |
Custom user data. This parameter takes effect only when you specify an MNS configuration for the Notification parameter. The data is returned in the asynchronous notification message, which you can use to associate the message with your services. The maximum length is 2048 bytes. |
{ "id": "test-id", "name": "test-name" } |
| Notification | Notification |
No |
The notification configuration. For more information, click Notification. For the format of asynchronous notification messages, see the metadata indexing section in Asynchronous notification message formats. |
Response elements
|
Element |
Type |
Description |
Example |
|
object |
The response struct. |
||
| RequestId |
string |
The request ID. |
8F93E6D9-5AC0-49F9-914D-E02678A3**** |
| EventId |
string |
The event ID. |
387-1DAPFFZplUZhuCuhnB6I9H**** |
Examples
Success response
JSON format
{
"RequestId": "8F93E6D9-5AC0-49F9-914D-E02678A3****",
"EventId": "387-1DAPFFZplUZhuCuhnB6I9H****"
}
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.