Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node operation allows users to delete an existing index on a specific payload field within a collection in Qdrant, a vector search engine. Indexes on payload fields improve query performance and filtering capabilities, so deleting an index might be necessary when the index is no longer needed or if it needs to be recreated with different settings.
Common scenarios for this operation include:
- Removing obsolete or unused indexes to optimize storage and performance.
- Resetting or updating indexing strategies on payload fields.
- Managing collection schema dynamically based on evolving data requirements.
For example, if you have a collection of documents with a payload field "category" indexed for fast filtering, but later decide to remove that index because the filtering criteria changed, this operation will delete the index on the "category" field.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection containing the payload field whose index you want to delete. |
| Field Name | The name of the payload field where the index should be deleted. |
| Wait | Whether to wait for the deletion operation to complete before proceeding (true/false). |
| Ordering | Defines ordering guarantees for the operation; options are: Weak, Medium, Strong. |
Output
The node outputs JSON data representing the response from the Qdrant API after attempting to delete the payload index. This typically includes status information about the success or failure of the operation.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a Qdrant instance via its REST API.
- Requires an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the Qdrant service must be set in the node credentials.
Troubleshooting
Common issues:
- Incorrect collection or field names may cause the operation to fail because the specified index does not exist.
- Network connectivity problems or incorrect API credentials can prevent successful communication with the Qdrant server.
- Attempting to delete an index on a field that is not indexed will likely result in an error.
Error messages and resolutions:
- "Collection not found": Verify the collection name is correct and exists in Qdrant.
- "Index on field not found": Confirm the field name is correct and currently indexed.
- Authentication errors: Check that the API key or token is valid and properly configured in n8n.
- Timeouts or network errors: Ensure the Qdrant server is reachable and stable.