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
This node provides an interface to Qdrant, a vector search engine and database. Specifically, the "Delete Payload Index" operation allows users to delete an index on a specified field within a collection in Qdrant. This is useful when you want to remove indexing on certain payload fields to optimize storage or change query behavior.
Common scenarios include:
- Removing obsolete or unused indexes from collections to improve write performance.
- Adjusting the schema of your vector database by deleting indexes on fields that are no longer queried.
- Managing and maintaining collections dynamically as data evolves.
Example: If you have a collection storing product vectors with indexed fields like "category" or "brand," and you decide to stop indexing "brand" for faster writes, you can use this operation to delete the index on the "brand" field.
Properties
| Name | Meaning |
|---|---|
| Collection Name | The name of the collection in Qdrant where the payload index should be deleted. |
| Field Name | The name of the payload field whose index you want to delete. |
| Wait | Boolean flag indicating whether to wait for the deletion operation to complete before continuing. |
| 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.
- Needs an API key credential configured in n8n for authenticating requests to Qdrant.
- The base URL of the Qdrant service must be set in the credentials.
Troubleshooting
Common issues:
- Incorrect collection or field names will cause the operation to fail because the specified index does not exist.
- Network connectivity problems or incorrect API credentials will prevent successful communication with Qdrant.
- Setting
Waitto true may cause delays if the Qdrant server takes time to process the deletion.
Error messages:
- "Collection not found" — Verify the collection name is correct and exists in Qdrant.
- "Index on field not found" — Check that the field name is correctly spelled and that an index exists on it.
- Authentication errors — Ensure the API key credential is valid and has sufficient permissions.