Milvus Connector Guide

The Milvus connector package for milvus-1.0.0 is currently a legacy-compatible stub. All runtime operations are intentionally non-functional because this connector does not yet implement a Milvus gRPC client in backend-next.

Current behavior

Supported operation names:

• create
• get
• search
• update
• delete
• test

Behavior details:

• create, get, search, update, and delete always return an error because gRPC execution is not implemented.
• test first validates endpoint_url with legacy-compatible validation behavior, then returns the same gRPC limitation error.

Configuration

Configuration parameters are read from integration config (not call payload):

• endpoint_url (required): Milvus endpoint URL.
• api_key (optional): API key for protected deployments.
• timeout_seconds (optional, default 30): timeout value reserved for future real client calls.

Example request and current response

curl -X POST "https://api.example.com/api/v1/integrations/<ENTITY_ID>/execute" \
  -H "X-API-Key: <API_KEY>" \
  -H "X-Tenant-ID: <TENANT_ID>" \
  -H "Content-Type: application/json" \
  -d '{
    "operation": "search"
  }'

{
  "success": false,
  "error": "Milvus requires a gRPC client. Use @zilliz/milvus2-sdk-node or similar for full implementation.",
  "execution_id": "corr-12345",
  "processing_time_ms": 3
}

test with missing endpoint_url:

{
  "success": false,
  "error": "Configuration validation failed",
  "execution_id": "corr-12345",
  "processing_time_ms": 1
}

Migration note

This mirrors legacy connector behavior where operation names exist, but execution paths are placeholders that return a gRPC limitation error. If you need real Milvus integration, implement a connector variant that uses a supported Milvus SDK/gRPC client.

Additional resources

• Milvus documentation
• Milvus API reference
• Milvus Node SDK