All Products
Search
Document Center

AnalyticDB:UpsertCollectionDataAsync

Last Updated:Nov 05, 2025
This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.

Uploads vector data in an asynchronous manner by using an on-premises file or a password-free Internet-accessible file URL. The vector data can be up to 200 MB in size.

Operation description

This operation is the asynchronous operation of UpsertCollectionData. The UpsertCollectionData operation supports up to 10 MB of data, and this operation supports up to 200 MB of data.

Note Related operations:
  • You can call the GetUpsertCollectionDataJob operation to query the progress and result of an upload job.

  • You can call the CancelUpsertCollectionDataJob operation to cancel an upload job.

Note You can upload data for the same collection only in a serial manner.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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:
    • For mandatory resource types, indicate with a prefix of * .
    • 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.
OperationAccess levelResource typeCondition keyAssociated operation
gpdb:UpsertCollectionDataAsynccreate
*Collection
acs:gpdb:{#regionId}:{#accountId}:collection/{#DBInstanceId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The region ID of the instance.

cn-hangzhou
DBInstanceIdstringNo

The instance ID.

Note You can call the DescribeDBInstances operation to query the information about all AnalyticDB for PostgreSQL instances within a region, including instance IDs.
gp-xxxxxxxxx
NamespacestringNo

The name of the namespace. Default value: public.

Note You can call the CreateNamespace operation to create a namespace and call the ListNamespaces operation to query a list of namespaces.
mynamespace
CollectionstringYes

The name of the collection.

Note You can call the ListCollections operation to query a list of collections.
document
NamespacePasswordstringYes

The password of the namespace.

Note The value of this parameter is specified when you call the CreateNamespace operation.
testpassword
FileUrlstringYes

The Internet-accessible vector data file URL.

Note
  • The file content must be in the JSONL format. Each line consists of a list of JSON data, which specifies a set of vector data.

  • Data format of each line: {String Id; Map<String, Object> Metadata; List<Double> Vector}. Example: {"Id":"myid", "Metadata": {"my_meta_key": "my_meta_value"}, "Vector": [1.234, -0.123]}.

  • We recommend that you use SDKs to call this operation. SDKs encapsulate the UpsertCollectionDataAsyncAdvance method to upload on-premises files as data sources.

https://xx/vectors.jsonl
WorkspaceIdstringNo

The ID of the Workspace composed of multiple database instances. This parameter and the DBInstanceId parameter cannot both be empty. When both are specified, this parameter takes precedence.

gp-ws-*****

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

ABB39CC3-4488-4857-905D-2E4A051D0521
Messagestring

The returned message.

success
Statusstring

The status of the operation. Valid values:

  • success
  • fail
success
JobIdstring

The job ID. It can be used to query the job status or cancel the job.

231460f8-75dc-405e-a669-0c5204887e91

Examples

Sample success responses

JSONformat

{
  "RequestId": "ABB39CC3-4488-4857-905D-2E4A051D0521",
  "Message": "success",
  "Status": "success",
  "JobId": "231460f8-75dc-405e-a669-0c5204887e91"
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-08-04The request parameters of the API has changedView Change Details