Databricks icon

Databricks

Interact with Databricks API
Join our community

Actions42

Overview

This node integrates with the Databricks Unity Catalog API to manage volumes within a specified catalog and schema. Specifically, the Create Volume operation allows users to create a new volume in a chosen Unity Catalog schema. This is useful for organizing and managing data storage volumes in Databricks environments, enabling better data governance and access control.

Practical scenarios include:

  • Automating the creation of storage volumes as part of a data pipeline setup.
  • Managing data lifecycle by programmatically creating volumes for different projects or teams.
  • Integrating volume creation into CI/CD workflows for infrastructure as code.

Properties

Name Meaning
Catalog Select a Unity Catalog to work with. The list is dynamically loaded from your workspace.
Schema Select a schema within the chosen catalog.
Volume Select an existing volume (used for update or delete operations; not applicable here).
Volume Type The type of volume to create. Options: EXTERNAL or MANAGED.

Output

The node outputs JSON data representing the response from the Databricks API after attempting to create the volume. This typically includes details about the newly created volume such as its name, type, and metadata returned by the API.

If the operation succeeds, the output JSON will contain confirmation and details of the created volume. If there is an error, the output may contain error information depending on whether the node is configured to continue on failure.

Dependencies

  • Requires an active Databricks workspace with Unity Catalog enabled.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The node uses the Databricks REST API endpoint /api/2.1/unity-catalog/volumes for volume management.
  • Network connectivity to the Databricks instance is required.

Troubleshooting

  • Common issues:

    • Invalid or missing API token leading to authorization errors.
    • Specifying a catalog or schema that does not exist or is inaccessible.
    • Attempting to create a volume with a name that already exists.
    • Network connectivity problems preventing API calls.

  • Error messages:

    • API Error: 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
    • API Error: 404 Not Found: Verify that the specified catalog and schema names are correct.
    • API Error: 409 Conflict: A volume with the same name might already exist.
    • Network Error: No response received from server: Confirm network access to the Databricks host.

  • To resolve errors, ensure credentials are correctly set up, parameters are valid, and the Databricks workspace is accessible.

Links and References

Discussion