Databricks

Overview

The node provides integration with the Databricks API, allowing users to perform various operations on different Databricks resources. Specifically, for the Unity Catalog resource and the Delete Volume operation, this node enables users to delete a specified volume within a given catalog and schema in Unity Catalog.

This is useful in scenarios where you need to programmatically manage storage volumes in your Databricks Unity Catalog environment, such as cleaning up unused volumes or automating infrastructure management tasks.

Example use case:

• Automatically deleting temporary or obsolete volumes after a data processing job completes.
• Managing storage resources by removing volumes that are no longer needed to optimize costs.

Properties

Output

The node outputs JSON data representing the result of the delete volume operation. Typically, this will include confirmation of the deletion or any relevant metadata returned by the Databricks API about the deleted volume.

If the node supports binary data output (not indicated here), it would represent any files or binary responses related to the operation, but for this operation, the output is expected to be purely JSON.

Dependencies

• Requires an active connection to the Databricks API.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The base URL for the Databricks instance must be set in the credentials.
• No additional external dependencies beyond the Databricks API.

Troubleshooting

• Common issues:

  • Invalid or missing API token: Ensure the API key/token is correctly configured in the node credentials.
  • Incorrect catalog, schema, or volume name: Verify that the names provided exist and are spelled correctly.
  • Insufficient permissions: The API token used must have permission to delete volumes in the specified Unity Catalog.
  • Network connectivity issues: Confirm that n8n can reach the Databricks API endpoint.

• Common error messages:

  • Authorization errors (e.g., 401 Unauthorized): Check API token validity and permissions.
  • Not found errors (e.g., 404 Not Found): The specified catalog, schema, or volume does not exist.
  • Validation errors: Input parameters may be missing or invalid; ensure all required fields are filled.

Resolving these typically involves verifying credentials, input values, and user permissions.

Links and References

• Databricks Unity Catalog Documentation
• Databricks REST API Reference
• n8n Documentation