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, to perform various operations on collections and points within those collections. The "Check Collection Exists" operation specifically checks whether a collection with a given name exists in the Qdrant instance. This is useful for workflows that need to verify the presence of a collection before performing further actions such as querying or updating data.
Practical examples:
- Before inserting new points into a collection, ensure the collection exists to avoid errors.
- Validate user input by checking if the specified collection is available.
- Automate maintenance tasks that depend on the existence of certain collections.
Properties
| Name | Meaning |
|---|---|
| Collection Name | Name of the collection to check |
Output
The output JSON contains information indicating whether the specified collection exists. Typically, this would be a boolean field or an object confirming the presence or absence of the collection. The exact structure depends on the underlying API response but generally includes:
- A flag or status indicating existence (e.g.,
exists: trueorexists: false).
No binary data output is expected from this operation.
Dependencies
- Requires connection to a Qdrant instance via an API key credential.
- The node expects the base URL of the Qdrant service to be configured in the credentials.
- Network access to the Qdrant API endpoint is necessary.
Troubleshooting
Common issues:
- Incorrect collection name spelling will result in a false negative (collection reported as not existing).
- Misconfigured credentials or incorrect base URL will cause connection failures.
- Network issues can prevent the node from reaching the Qdrant service.
Error messages:
- Authentication errors indicate invalid or missing API credentials; verify and update the API key.
- Connection timeouts suggest network problems or incorrect service URL; check connectivity and configuration.
- Unexpected responses may occur if the Qdrant API version changes; ensure compatibility.