h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

This node operation creates a job to delete one or more collections identified by their unique IDs. It is useful in scenarios where you want to batch-delete multiple collections asynchronously, rather than deleting them one-by-one synchronously. This can help manage large-scale cleanup tasks or automate the removal of outdated or irrelevant collections in your system.

For example, if you have a list of collection IDs that are no longer needed, you can use this operation to create a deletion job that processes all those collections in the background, freeing up resources and keeping your data organized.

Properties

Name Meaning
Collection IDs IDs of collections to be deleted (string containing one or more collection IDs)

The property "Collection IDs" expects a string input representing the unique identifiers of the collections you want to delete. This is a required field.

Output

The output of this operation will typically include the response from the API indicating the status of the job creation for deleting collections. The json output field will contain details about the created job, such as its ID, status, and any relevant metadata returned by the server.

If the node supports binary data output, it would relate to any files or attachments associated with the job, but in this case, the operation deals with job creation and does not output binary data.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • The node sends a POST request to the endpoint /collections/delete_job with the collection IDs in the request body.
  • Proper permissions and access rights to delete collections on the target system are necessary.

Troubleshooting

  • Missing or invalid Collection IDs: Ensure that the "Collection IDs" property is provided and correctly formatted. Invalid or empty IDs will cause the job creation to fail.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions to perform deletion operations.
  • Permission denied: The user associated with the API key must have rights to delete the specified collections.
  • API endpoint errors: Network issues or server errors may prevent job creation. Check connectivity and server status.
  • Timeouts: Large deletion jobs might take time; ensure the system allows asynchronous job processing.

Links and References

  • Refer to the API documentation of the service managing collections for detailed information on the /collections/delete_job endpoint.
  • Consult your platform's user guide on managing collections and job operations for best practices.

Discussion