Drop Pipeline
Drop a specific pipeline
DELETE
https://controller.${CLOUD_REGION}.zillizcloud.com/v1/pipelines/{PIPELINE_ID}
Example
📘Notes
This API requires an API key as the authentication token.
export CLOUD_REGION="gcp-us-west1"
export API_KEY=""
curl --location --request DELETE "https://controller.api.${CLOUD_REGION}.zillizcloud.com/v1/pipelines/pipe-xxxxxxxxxxxxxxxxxxxxxx" \
--header "Authorization: Bearer ${API_KEY}"
Possible response is similar to the following.
{
"code": 200,
"data": {
"pipelineId": "pipe-xxxxxxxxxxxxxxxxxxxxxx",
"name": "my_doc_ingestion_pipeline",
"type": "INGESTION",
"createTimestamp": 1720601290000,
"description": "A doc ingestion pipeline",
"status": "SERVING",
"totalUsage": {
"embedding": 0
},
"functions": [
{
"name": "index_my_doc",
"action": "INDEX_DOC",
"inputFields": [
"doc_url",
"doc_name"
],
"language": "ENGLISH",
"chunkSize": 500,
"splitBy": [
"\n\n",
"\n",
" ",
""
],
"embedding": "zilliz/bge-base-en-v1.5"
},
{
"name": "keep_doc_info",
"action": "PRESERVE",
"inputField": "publish_year",
"outputField": "publish_year",
"fieldType": "Int16"
}
],
"clusterId": "inxx-xxxxxxxxxxxxxxx",
"collectionName": "doc_pipeline"
}
}
Request
Parameters
-
No query parameters required
-
Path parameters
Parameter Description PIPELINE_ID string(required) -
No header parameters required
Request Body
No request body required
Response
Returns information of a specific pipeline just dropped.
Response Body
Option 1:
{
"code": "integer",
"data": {
"pipelineId": "integer",
"name": "string",
"type": "string",
"description": "string",
"status": "string",
"functions": {
"oneOf": [
{
"name": "string",
"action": "string",
"inputFields": [
{}
],
"langauge": "string",
"embedding": "string"
},
{
"name": "string",
"action": "string",
"inputField": "string",
"langauge": "string",
"chunkSize": "integer",
"embedding": "string",
"splitBy": "string"
},
{
"name": "string",
"action": "string",
"inputFields": [
{}
],
"embedding": "string"
},
{
"name": "string",
"action": "string",
"inputField": "string",
"outputField": "string",
"fieldType": "string"
}
]
},
"clusterID": "string",
"collectionName": "string"
}
}
Property | Description |
---|---|
code | integer Indicates whether the request succeeds.
|
data | object |
data.pipelineId | integer A pipeline ID. |
data.name | string Name of the pipeline. |
data.type | string Type of the pipeline. For an ingestion pipeline, the value should be INGESTION . |
data.description | string Description of the pipeline. |
data.status | string Current status of the pipeline. If the value is other than SERVING , the pipeline is not working. |
functions | object | object | object | object Functions in the pipeline. For an ingestion pipeline, there should be only one INDEX_DOC function. |
functions[opt_1] | object |
functions[opt_1].name | string Name of the function to create. |
functions[opt_1].action | string Type of the function to create. For an ingestion pipeline, possible values are INDEX_DOC and PRESERVE . |
functions[opt_1][].inputFields | array Names the fields according to your needs. In an INDEX_TEXT function of an ingestion pipeline, use them for the user-provided texts. |
functions[opt_1][].inputFields[] | string An input field. |
functions[opt_1].langauge | string Language that your document is in. Possible values are english or chinese . The parameter applies only to ingestion pipelines. |
functions[opt_1].embedding | string Name of the embedding model in use. |
functions[opt_2] | object |
functions[opt_2].name | string Name of the function to create. |
functions[opt_2].action | string Type of the function to create. For an ingestion pipeline, possible values are INDEX_DOC and PRESERVE . |
functions[opt_2].inputField | string Name the field according to your needs. In an INDEX_DOC function of an ingestion pipeline, use it for pre-signed document URLs in GCS or AWS S3 buckets. |
functions[opt_2].langauge | string Language that your document is in. Possible values are english or chinese . The parameter applies only to ingestion pipelines. |
functions[opt_2].chunkSize | integer The maximum size of a splitted document segment. |
functions[opt_2].embedding | string Name of the embedding model in use. |
functions[opt_2].splitBy | string The splitters that Zilliz Cloud uses to split the specified docs. |
functions[opt_3] | object |
functions[opt_3].name | string Name of the function to create. |
functions[opt_3].action | string Type of the function to create. For an ingestion pipeline, possible values are INDEX_DOC and PRESERVE . |
functions[opt_3][].inputFields | array Names the fields according to your needs. In an INDEX_IMAGE function of an ingestion pipeline: image_url stands for pre-signed image URLs in GCS or AWS S3 buckets, and image_id stands for the image ID. |
functions[opt_3][].inputFields[] | string An input field. |
functions[opt_3].embedding | string Name of the embedding model in use. |
functions[opt_4] | object |
functions[opt_4].name | string Name of the function to create. |
functions[opt_4].action | string Type of the function to create. For an ingestion pipeline, possible values are INDEX_DOC and PRESERVE . |
functions[opt_4].inputField | string Name the field according to your needs. In a preserve function of an ingestion pipeline, Zilliz Cloud uses the value as the name of a field in the collection to create. |
functions[opt_4].outputField | string Name of the output field. The value should be the same as that of input_field . |
functions[opt_4].fieldType | string Data type of the field to create in the target collection. Possible values are BOOL , INT8 , INT16 , INT32 , INT64 , FLOAT , DOUBLE , and VARCHAR . |
data.clusterID | string The target cluster to which the pipeline applies. |
data.collectionName | string The target collection to which the pipeline applies. |
Option 2:
{
"code": "integer",
"data": {
"pipelineId": "integer",
"name": "string",
"type": "string",
"description": "string",
"status": "string",
"functions": [
{
"name": "string",
"action": "string",
"inputFields": [
{}
],
"clusterID": "string",
"collectionName": "string",
"reranker": "string"
}
]
}
}
Property | Description |
---|---|
code | integer Indicates whether the request succeeds.
|
data | object |
data.pipelineId | integer A pipeline ID. |
data.name | string Name of the pipeline |
data.type | string Type of the pipeline. For a search pipeline, the value should be SEARCH . |
data.description | string Description of the pipeline. |
data.status | string Current status of the pipeline. If the value is not SERVING , the pipeline is not working. |
data[].functions | array Functions in the pipeline. For a search pipeline, each of its member functions targets at a different collection. |
data[].functions[] | object |
data[].functions[].name | string Name of the function. |
data[].functions[].action | string Type of the function. For a search function, the value should be SEARCH_DOC_CHUNKS , SEARCH_TEXT , SEARCH_IMAGE_BY_IMAGE , and SEARCH_IMAGE_BY_TEXT . |
data[].functions[][].inputFields | array Name of the input fields. |
data[].functions[][].inputFields[] | string For a SEARCH_DOC_CHUNKS or a SEARCH_IMAGE_BY_TEXT function, you should include query_text as the value. |
data[].functions[].clusterID | string Target cluster of this function. |
data[].functions[].collectionName | string Target collection of this function. |
data[].functions[].reranker | string If you need to reorder or rank a set of candidate outputs to improve the quality of the search results, set this parameter to a reranker model. This parameter applies only to pipelines for Text and Doc Data. Currently, only zilliz/bge-reranker-base is available as the parameter value. |
Option 3:
{
"code": "integer",
"data": {
"pipelineId": "integer",
"name": "string",
"type": "string",
"description": "string",
"status": "string",
"functions": [
{
"name": "string",
"action": "string",
"inputField": "string"
}
],
"clusterID": "string",
"collectionName": "string"
}
}
Property | Description |
---|---|
code | integer Indicates whether the request succeeds.
|
data | object |
data.pipelineId | integer A pipeline ID. |
data.name | string Name of the pipeline. |
data.type | string Type of the pipeline. For a deletion pipeline, the value should be DELETION . |
data.description | string Description of the pipeline. |
data.status | string Current status of the pipeline. If the value is not SERVING , the pipeline is not working. |
data[].functions | array Functions in the pipeline. For a deletion pipeline, there can be multiple member functions with each representing a deletion request. |
data[].functions[] | object |
data[].functions[].name | string Name of the function. |
data[].functions[].action | string Type of the function. For a deletion pipeline, its member functions should be of PURGE_BY_EXPRESSION , PURGE_DOC_INDEX , and PURGE_IMAGE_BY_ID . |
data[].functions[].inputField | string Name of the input field. For a PURGE_DOC_INDEX function, the value should be the name of the doc to delete. |
data.clusterID | string Target cluster of the pipeline. |
data.collectionName | string Target collection of the pipeline. |
Error Response
{
"code": integer,
"message": string
}
Property | Description |
---|---|
code | integer Indicates whether the request succeeds.
|
message | string Indicates the possible reason for the reported error. |