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 update an existing collection in Qdrant, a vector search engine. It allows users to modify various configuration parameters of a collection such as vectors, optimizers, indexing settings, quantization, sparse vectors, and strict mode options. This is useful when you want to fine-tune or adjust the behavior and performance of your vector collection without recreating it.
Practical examples include:
- Updating vector parameters to change how vectors are stored or indexed.
- Adjusting optimizer configurations to improve query speed or accuracy.
- Modifying HNSW index parameters for better nearest neighbor search performance.
- Changing quantization settings to balance between storage size and precision.
- Enabling or tweaking strict mode to enforce stricter validation rules on the collection.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection to update. |
| Vectors | JSON object specifying vector parameters to update for each named vector in the collection. |
| Optimizers Config | JSON object with custom parameters for optimizers; if omitted, optimizer settings remain unchanged. |
| Params | JSON object with base parameters for the collection; if omitted, these remain unchanged. |
| HNSW Config | JSON object with HNSW index parameters to update; if omitted, HNSW settings remain unchanged. |
| Quantization Config | JSON object with quantization parameters to update; if omitted, quantization remains unchanged. |
| Sparse Vectors | JSON object specifying parameters to update for each sparse vector; if omitted, no changes made. |
| Strict Mode Config | JSON object with strict mode configuration updates; if omitted, strict mode settings remain unchanged. |
Output
The node outputs JSON data representing the result of the update operation on the collection. This typically includes confirmation of the update status and may contain the updated collection metadata or configuration details.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential to authenticate requests to the Qdrant service.
- Needs the Qdrant service URL configured in the credentials.
- The node depends on the Qdrant REST API being accessible and properly configured.
Troubleshooting
Common issues:
- Invalid or missing collection name will cause the update to fail.
- Malformed JSON in any of the configuration fields (vectors, optimizersConfig, etc.) can lead to errors.
- Attempting to update a non-existent collection will result in an error.
- Insufficient permissions or invalid API key will prevent successful updates.
Error messages and resolutions:
- "Collection not found" — Verify the collection name is correct and exists.
- "Invalid JSON format" — Check and correct the JSON syntax in the input fields.
- "Unauthorized" or "Authentication failed" — Ensure the API key credential is valid and has necessary permissions.
- "Bad Request" — Review the parameters sent; some may be incompatible or incorrectly structured.
Links and References
- Qdrant Official Website
- Qdrant API Documentation
- n8n Documentation (for general usage of the Qdrant node)