Actions26
- Collection Actions
- Payload Actions
- Point Actions
- Search Actions
- Vector Actions
Overview
This node integrates with Qdrant, a vector search engine, to delete points from a specified collection. The "Delete Points" operation allows users to remove one or more points identified by their IDs or filtered by specific conditions within a collection. This is useful for managing and maintaining the dataset in Qdrant by removing outdated, irrelevant, or incorrect data points.
Practical scenarios include:
- Cleaning up a collection by deleting points that no longer meet certain criteria.
- Removing specific points by their IDs after they have been deprecated or replaced.
- Managing shards explicitly when working with large distributed collections.
Properties
| Name | Meaning |
|---|---|
| Collection Name | Specifies the target collection from which points will be deleted. Can be selected from a list or entered by name. |
| Point IDs | JSON array of point IDs to delete. Only these points will be removed if specified. |
| Filter | JSON object defining conditions to select points for deletion. Only points matching this filter will be deleted. |
| Shard Key | JSON specifying particular shards to look into for points. If omitted, all shards are searched. |
| Wait | Boolean indicating whether to wait for the deletion changes to complete before proceeding. Defaults to true. |
| Ordering | Defines the ordering guarantees for the operation. Options: Weak, Medium, Strong. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation of the deletion request and possibly metadata about the operation's success or failure. There is no indication that binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Qdrant REST API.
- Needs the base URL of the Qdrant instance configured in the credentials.
- The node depends on Qdrant's REST API being accessible and properly configured.
Troubleshooting
Common Issues:
- Incorrect collection name or non-existent collection will cause the operation to fail.
- Malformed JSON in the Point IDs, Filter, or Shard Key fields can lead to errors.
- Insufficient permissions or invalid API credentials will prevent successful deletion.
- Specifying shard keys incorrectly may result in no points being found or deleted.
Error Messages:
- Errors related to authentication usually indicate missing or invalid API credentials.
- Validation errors often arise from improper JSON formatting in input properties.
- "Collection not found" or similar messages suggest the collection name is incorrect or does not exist.
Resolutions:
- Verify the collection name exists and is correctly spelled.
- Ensure JSON inputs are valid and properly structured.
- Confirm API credentials are set up and have necessary permissions.
- Check shard key values against the collection's shard configuration.