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 interfaces with Qdrant, a vector search engine and database. Specifically, the "Overwrite Payload" operation allows users to overwrite the payload data of points within a specified collection in Qdrant. This is useful when you want to replace existing metadata or attributes associated with certain points in a collection.
Common scenarios include:
- Updating metadata for specific points after reprocessing or enrichment.
- Correcting or standardizing payload data across selected points.
- Bulk replacing payloads based on filters or point IDs.
For example, if you have a collection of product vectors and want to update the product descriptions or categories stored as payloads, this operation lets you overwrite those fields efficiently.
Properties
Name | Meaning |
---|---|
Collection Name | Name of the collection in Qdrant where the points reside. |
Payload | The new payload values (in JSON format) that will overwrite the existing payloads of the selected points. |
Points | List of point IDs (as JSON array) to specifically overwrite payloads for. |
Filter | JSON object defining conditions to select points whose payloads should be overwritten. |
Key | A string path specifying where in the payload structure to assign the new payload values. |
Shard Key | JSON value specifying which shards to look into for the points; if omitted, all shards are searched. |
Wait | Boolean indicating whether to wait for the changes to be applied before continuing execution. |
Ordering | Defines ordering guarantees for the operation; options are: Weak, Medium, Strong. |
Output
The node outputs JSON data representing the result of the overwrite operation. This typically includes status information about the success or failure of the operation, and may contain details such as the number of points updated.
If binary data output is supported by other operations, it is not relevant here since this operation deals with JSON payload overwrites only.
Dependencies
- Requires an API key credential to authenticate with the Qdrant service.
- Needs the base URL of the Qdrant instance configured in credentials.
- The node depends on Qdrant's REST API to perform the overwrite payload operation.
Troubleshooting
Common issues:
- Incorrect collection name leading to "collection not found" errors.
- Malformed JSON in the Payload, Points, Filter, or Shard Key properties causing request failures.
- Insufficient permissions or invalid API key resulting in authentication errors.
- Specifying points or filters that do not match any points, resulting in no updates.
Error messages and resolutions:
- "Collection not found": Verify the collection name is correct and exists in Qdrant.
- "Invalid JSON format": Ensure all JSON inputs (Payload, Points, Filter, Shard Key) are properly formatted.
- "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has necessary permissions.
- "No points matched": Adjust the filter or points list to target existing points.
Links and References
- Qdrant Official Website
- Qdrant API Documentation
- n8n Documentation on Creating Custom Nodes