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 the Qdrant vector search engine, specifically enabling users to delete specific keys from the payload of points stored in a collection. This operation is useful when you want to clean up or modify metadata associated with points without deleting the points themselves.
Typical use cases include:
- Removing outdated or sensitive information from point payloads.
- Cleaning up payload data after certain processing steps.
- Managing and maintaining the integrity of metadata in vector collections.
For example, if you have a collection of product vectors with various attributes stored as payload keys, and some attributes become irrelevant or incorrect, you can selectively remove those keys from the payloads of specified points.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection in which the points reside. |
| Keys | List of payload keys (attributes) to remove from the points' payloads. |
| Points | List of point IDs from which to delete the specified payload keys. If empty, other filters apply. |
| Filter | Conditions to select points for payload key deletion. Only points satisfying these conditions are affected. |
| Shard Key | Specifies shards to look into for points. If not set, all shards are searched. |
| Wait | Boolean flag indicating whether to wait for the changes to be applied before continuing. |
| Ordering | Defines ordering guarantees for the operation; options are Weak, Medium, or Strong consistency levels. |
Output
The node outputs JSON data representing the result of the delete payload operation. This typically includes confirmation of the operation's success and possibly metadata about how many points were affected.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a Qdrant service instance.
- Needs an API key credential for authenticating requests to the Qdrant API.
- The base URL of the Qdrant service must be configured in the node credentials.
Troubleshooting
Common issues:
- Incorrect collection name: Ensure the collection exists in Qdrant.
- Invalid point IDs or empty points list: Verify that the points specified exist and are correctly formatted.
- Malformed filter JSON: Filters must be valid JSON and conform to Qdrant's filtering schema.
- Insufficient permissions or invalid API key: Check that the API key has rights to modify the collection.
Error messages:
- "Collection not found": The specified collection does not exist.
- "Invalid filter format": The filter JSON is malformed or uses unsupported fields.
- "Unauthorized": API key is missing or invalid.
Resolving these usually involves verifying input parameters, ensuring correct credentials, and confirming the existence of collections and points.