Actions26
- Delete Collection
- Get Collection
- Check Collection Exists
- Create Collection
- Update Collection
- Retrieve Point
- Retrieve Points
- Upsert Points
- Delete Points
- Update Vectors
- Delete Vectors
- Set Payload
- Overwrite Payload
- Delete Payload
- Clear Payload
- Batch Update Points
- Scroll Points
- Count Points
- Query Points
- Query Batch Points
- Query Points Groups
- Matrix Pairs
- Matrix Offsets
- Payload Facets
- Create Payload Index
- Delete Payload Index
Overview
The node provides an interface to Qdrant, a vector search engine and database. Specifically, the "Delete Points" operation allows users to delete points (data entries) from a specified collection in Qdrant. This is useful for managing and cleaning up data by removing unwanted or obsolete points based on their IDs or filter criteria.
Common scenarios include:
- Removing outdated or irrelevant vectors from a collection.
- Cleaning up test or temporary data after processing.
- Managing data lifecycle by deleting points that meet certain conditions.
Example: A user wants to delete specific points identified by their IDs from a collection named "products_vectors" to remove discontinued products from the search index.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection from which points will be deleted. |
| Points | A JSON array listing the IDs of points to delete explicitly. |
| Filter | A JSON object specifying conditions to select points for deletion (only points matching these). |
| Shard Key | A JSON value specifying which shards to look into for points; if omitted, all shards are searched. |
| Wait | Boolean indicating whether to wait for the deletion changes to complete before continuing. |
| Ordering | Defines ordering guarantees for the operation; options are "Weak", "Medium", or "Strong". |
Output
The output contains a json field with the result of the delete operation. Typically, this includes confirmation of the deletion request and possibly metadata about the operation's success or status.
If the node supports binary data output, it would represent any binary response from Qdrant, but for this operation, the focus is on JSON responses confirming deletion.
Dependencies
- Requires connection to a Qdrant instance via an API URL and an API key credential configured in n8n.
- The node depends on the Qdrant REST API to perform operations.
- Proper network access and authentication credentials must be set up in n8n for successful communication.
Troubleshooting
Common issues:
- Incorrect collection name leading to "collection not found" errors.
- Invalid point IDs or malformed JSON in the "Points" or "Filter" fields causing request failures.
- Insufficient permissions or invalid API credentials resulting in authorization errors.
- Network connectivity problems preventing access to the Qdrant server.
Error messages and resolutions:
- "Collection not found": Verify the collection name is correct and exists in Qdrant.
- "Invalid JSON format": Ensure the JSON input for points, filter, or shard key is well-formed.
- "Unauthorized" or "Authentication failed": Check API key credentials and permissions.
- Timeouts or connection errors: Confirm network connectivity and Qdrant server availability.
Links and References
- Qdrant Official Website
- Qdrant API Documentation
- n8n Documentation (for general usage guidance)