Databricks icon

Databricks

Interact with Databricks API
Join our community

Actions42

Overview

This node integrates with the Databricks API, specifically supporting operations on various Databricks resources including Unity Catalog. For the Unity Catalog - Delete Function operation, it allows users to delete a function within a specified schema and catalog in their Databricks workspace.

Typical use cases include automating the management of Unity Catalog functions, such as cleaning up unused or obsolete functions programmatically as part of data governance or deployment pipelines.

Example scenario: A data engineer wants to remove a deprecated function from a Unity Catalog schema automatically after a new version is deployed, ensuring the environment stays clean without manual intervention.

Properties

Name Meaning
Catalog Select the Unity Catalog to work with. The list is dynamically loaded from your Databricks workspace.
Schema Select the schema within the chosen catalog where the function to be deleted resides.

Note: Both properties are required to specify the exact location of the function within Unity Catalog.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm success or provide error details if the deletion failed.

  • The json output field contains the response from the Databricks API related to the delete function request.
  • No binary data output is involved in this operation.

Dependencies

  • Requires an active Databricks API authentication token (API key or similar) configured in n8n credentials.
  • The node depends on the Databricks REST API endpoints for Unity Catalog, specifically those managing catalogs and schemas.
  • Network connectivity to the Databricks workspace endpoint is necessary.

Troubleshooting

  • Common issues:

    • Incorrect catalog or schema selection may cause the API to fail to find the function to delete.
    • Insufficient permissions on the Databricks workspace can lead to authorization errors.
    • Network issues or incorrect API host configuration can cause connection failures.

  • Error messages:

    • API Error: <status> <statusText>: Indicates the API responded with an error status code. Check that the catalog, schema, and function exist and that the API token has sufficient privileges.
    • Network Error: No response received from server: Suggests network connectivity problems or misconfigured API host URL.
    • Other generic errors will be logged with details; enabling "Continue On Fail" can help process multiple items even if some fail.

Links and References

Discussion