Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
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.
Common scenarios include:
- Updating vector configurations to change how vectors are stored or indexed.
- Adjusting optimizer parameters to improve search speed or accuracy.
- Modifying HNSW (Hierarchical Navigable Small World) index parameters for better nearest neighbor search performance.
- Changing quantization settings to balance between storage size and precision.
- Enabling or tweaking strict mode for more controlled behavior.
Practical example: You have a collection storing image embeddings and want to update its HNSW index parameters to improve query latency based on new usage patterns. Instead of creating a new collection, you use this node operation to update those parameters directly.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The target collection to update. Can be selected from a list of existing collections or specified by name. |
| 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 in the collection. |
| Strict Mode Config | JSON object with strict mode configuration to update; if omitted, strict mode settings remain unchanged. |
Output
The node outputs JSON data representing the response from the Qdrant API after attempting to update the collection. This typically includes confirmation of the update or details about the updated collection configuration.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Qdrant instance via REST API.
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- The base URL of the Qdrant service must be set in the node credentials.
Troubleshooting
- Invalid Collection Name: If the specified collection does not exist, the API will return an error. Ensure the collection name is correct or select from the provided list.
- Malformed JSON Parameters: Providing invalid JSON in any of the config fields (vectors, optimizersConfig, etc.) will cause request failures. Validate JSON syntax before running.
- Insufficient Permissions: If the API key lacks permissions to update collections, the request will fail. Verify API credentials have appropriate rights.
- Network Issues: Connection errors may occur if the Qdrant service URL is incorrect or unreachable. Confirm network connectivity and URL correctness.
- Partial Updates: Omitting optional JSON config fields leaves those settings unchanged. To reset a setting, explicitly provide the desired value.