Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node interfaces with Qdrant, a vector search engine, to manage collections and their data. Specifically, the "Check If Collection Exists" operation allows users to verify whether a collection with a given name already exists in the Qdrant instance. This is useful for workflows that need to conditionally create or update collections based on their existence.
Practical examples include:
- Before creating a new collection, check if it already exists to avoid duplication errors.
- Validate collection presence before performing operations like adding points or querying vectors.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection to check for existence |
Output
The node outputs JSON data indicating whether the specified collection exists. The exact structure typically includes a boolean field representing existence status. No binary data output is involved.
Example output JSON might look like:
{
"exists": true
}
Dependencies
- Requires an API key credential to authenticate with the Qdrant REST API.
- The node configuration must include the base URL of the Qdrant instance.
- Network access to the Qdrant service endpoint is necessary.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing a collection name that does not conform to Qdrant naming rules may result in errors.
- Network connectivity problems can prevent the node from reaching the Qdrant server.
Error messages:
- Authentication errors indicate invalid or missing API keys; verify credentials.
- HTTP 404 or similar errors may mean the Qdrant service URL is incorrect or the collection does not exist.
- Timeout errors suggest network issues; check connectivity and firewall settings.