Drop function (legacy)
Connection and CORS help
Use HTTPS for remote clusters or HTTP on loopback. Requests go directly from your browser to the endpoint. Run List collections to populate the collection selector. When copying an authenticated cURL command, set MILVUS_TOKEN in your shell.
For cross-origin requests, configure the endpoint to answer OPTIONS and allow the docs origin, POST, Content-Type, and Authorization if you use a token. Try the copied cURL command to troubleshoot outside the browser.
POST/v2/vectordb/collections/drop_function
{
"dbName": "default",
"collectionName": "books",
"FunctionName": "title_bm25"
}Example response
{
"code": 1100,
"message": "DropCollectionFunction RPC is no longer supported; drop a function via drop_function_field: invalid parameter"
}cURL command
curl --request POST --url 'https://your-cluster.example.com/v2/vectordb/collections/drop_function' \
--header 'Content-Type: application/json' \
--header "Authorization: Bearer ${MILVUS_TOKEN}" \
--data-raw '{
"dbName": "default",
"collectionName": "books",
"FunctionName": "title_bm25"
}'Milvus 3.0.6 rejects this legacy route. Use drop_function_field to remove the function and its output field.
Request fields
dbNamestring- Database name. Operations on collections use default when omitted.
collectionNamestring (required)- Name of the collection.
FunctionNamestring (required)- Name of the collection function to remove.
For new SDK code, use HttpClient.dropFunctionField to manage the function together with its output field and index.