Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
The node provides an interface to delete vectors from a specified collection in a Qdrant vector search engine. It allows users to remove vectors by specifying their names, point IDs, or applying filters to select points. This operation is useful for managing and maintaining the vector data stored in Qdrant collections, such as cleaning up outdated or irrelevant vectors.
Practical examples include:
- Removing specific vectors identified by their unique names from a collection.
- Deleting points that match certain filter criteria (e.g., metadata conditions).
- Targeting deletions within specific shards of a distributed collection.
- Waiting for the deletion operation to complete before proceeding with further workflow steps.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection from which vectors will be deleted. Can be selected from a list or entered manually. |
| Vector | A JSON array listing the names of vectors to delete. |
| Point IDs | A JSON array of point IDs to select for deletion. |
| Filter | A JSON object defining conditions to filter points that should be deleted. |
| Shard Key | A JSON value specifying which shards to search for points; if omitted, all shards are searched. |
| Wait | Boolean indicating whether to wait for the deletion changes to be applied before continuing. |
| Ordering | Defines the ordering guarantees for the operation; options are Weak, Medium, or Strong. |
Output
The node outputs JSON data representing the result of the delete vectors operation. This typically includes confirmation of the deletion request and any relevant status information returned by the Qdrant API. The output does not include binary data.
Dependencies
- Requires connection to a Qdrant vector search engine instance.
- Needs an API key credential configured in n8n for authenticating requests to the Qdrant REST API.
- The base URL of the Qdrant service must be set in the node credentials.
Troubleshooting
Common issues:
- Incorrect collection name may cause the operation to fail because the target collection does not exist.
- Malformed JSON in vector names, point IDs, or filter fields can lead to request errors.
- Specifying shard keys incorrectly might result in no points being found or deleted.
- Network or authentication errors if the API key or URL is misconfigured.
Error messages and resolutions:
- "Collection not found": Verify the collection name is correct and exists in Qdrant.
- "Invalid JSON format": Ensure JSON inputs for vectors, points, filter, and shardKey are properly formatted.
- "Unauthorized" or "Authentication failed": Check that the API key credential is valid and correctly set.
- Timeouts or network errors: Confirm network connectivity to the Qdrant instance and that the URL is reachable.