Qdrant

Overview

The node provides an interface to update vectors in a Qdrant collection. It allows users to specify a collection and update multiple points within that collection by providing their IDs and new vector values. This operation is useful when you want to modify existing vector embeddings stored in a Qdrant database, for example, to refine search results or update data representations after retraining models.

Common scenarios include:

• Updating vector embeddings of documents or items in a vector search engine after reprocessing or improving the embedding model.
• Correcting or refining specific points' vectors without recreating the entire collection.
• Managing vector data dynamically in applications like recommendation systems, semantic search, or anomaly detection.

Practical example:
You have a collection of product embeddings used for similarity search. After updating your embedding model, you want to update the vectors of certain products to reflect the new embeddings without affecting other data.

Properties

Output

The node outputs JSON data representing the result of the update operation. Typically, this includes confirmation of successful updates or any errors encountered. The exact structure depends on the Qdrant API response but generally confirms which points were updated.

If binary data output is supported (not indicated here), it would represent raw data related to the update operation, but this node primarily deals with JSON vector data.

Dependencies

• Requires connection to a Qdrant instance via its 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's credential configuration.

Troubleshooting

• Invalid Collection Name: If the specified collection does not exist, the node will fail. Ensure the collection name is correct and exists in Qdrant.
• Malformed Points JSON: The points property must be valid JSON with correct structure (id and vector). Invalid JSON or missing fields will cause errors.
• Shard Key Issues: Specifying an incorrect shard key may lead to no points being found or updated.
• API Authentication Errors: Missing or invalid API credentials will prevent communication with Qdrant.
• Ordering Parameter Misuse: Using an unsupported ordering option might cause the request to fail; use only the provided options (Weak, Medium, Strong).
• Timeouts: If Wait is true and the operation takes too long, timeouts may occur depending on network conditions or server load.

To resolve these issues:

• Verify collection existence and spelling.
• Validate JSON syntax and structure for points and shard key.
• Check API credentials and permissions.
• Use supported values for ordering.
• Consider setting Wait to false if timing out.

Links and References

• Qdrant Official Website
• Qdrant REST API Documentation
• n8n Documentation