h2oGPTeInstall

Overview

This node operation removes a size limit previously set on a specific collection within the system. Collections are used to group related documents, and sometimes they have a maximum total size limit for all documents combined. This operation lifts that restriction, allowing the collection to grow without a size cap.

Common scenarios where this is useful include:

• When you want to allow unlimited document storage in a collection after initially restricting it.
• When managing collections that dynamically grow and you no longer want to enforce size constraints.
• When preparing a collection for bulk imports or large-scale document ingestion without hitting size limits.

Practical example:

• You have a collection for project documentation with a 1GB size limit. After project expansion, you want to remove this limit to accommodate more files. Using this operation, you can remove the size limit from that collection by specifying its ID.

Properties

Output

The output of this operation is the full HTTP response returned by the API call to remove the size limit on the specified collection. The json field contains the parsed JSON response from the server, which typically confirms the success of the operation or provides relevant status information.

No binary data is involved in this operation.

Dependencies

• Requires an API key credential for authentication to the external service managing collections.
• The node sends an HTTP DELETE request to the endpoint /collections/{collection_id}/size_limit.
• The base URL and authentication headers must be configured properly in the node credentials.

Troubleshooting

• Invalid Collection ID: If the provided collection ID does not exist or is malformed, the API may return a 404 Not Found or 400 Bad Request error. Verify the collection ID is correct.
• Authentication Errors: Missing or invalid API key credentials will cause authorization failures (401 Unauthorized). Ensure valid credentials are configured.
• Permission Denied: If the user associated with the API key lacks permission to modify the collection, a 403 Forbidden error may occur. Check user permissions.
• Network Issues: Connectivity problems can cause request timeouts or failures. Confirm network access to the API endpoint.
• API Rate Limits: Excessive requests might trigger rate limiting. Implement retry logic or reduce request frequency if needed.

Links and References

• Collection Management API Documentation (replace with actual URL)
• Removing Size Limit Endpoint (replace with actual URL)