Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node integrates with Qdrant, a vector search engine, to manage collections of vectors and their metadata. Specifically, the "Delete Collection" operation allows users to remove an entire collection from Qdrant. This is useful when you want to permanently delete all data associated with a particular collection, for example, when cleaning up unused or outdated datasets.
Practical scenarios include:
- Removing obsolete collections after a project ends.
- Cleaning up test collections created during development.
- Managing storage by deleting large collections no longer needed.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection to delete. Can be selected from a list of existing collections or specified manually by name. |
The "Collection Name" property supports two modes:
- From List: Select from searchable existing collections.
- By Name: Enter the collection name as a string.
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Qdrant REST API.
- The node expects the base URL of the Qdrant instance to be configured in the credentials.
- Network access to the Qdrant service endpoint is necessary.
Troubleshooting
Common Issues:
- Attempting to delete a collection that does not exist will likely result in an error.
- Insufficient permissions or invalid API credentials can cause authentication failures.
- Network connectivity issues may prevent communication with the Qdrant server.
Error Messages:
- Collection not found: Verify the collection name is correct and exists.
- Authentication failed: Check that the API key credential is valid and properly configured.
- Network errors/timeouts: Ensure the Qdrant server URL is reachable and stable.
Resolving these typically involves verifying input parameters, credentials, and network settings.