DatabricksInstall

Overview

This node interacts with the Databricks API, specifically supporting multiple resources including Vector Search. For the Vector Search - Delete Index operation, it deletes a specified vector search index from the Databricks environment.

This operation is useful when you want to remove an existing vector search index that is no longer needed, for example, to clean up unused indexes or to reset your vector search setup.

Practical examples:

• Removing outdated or obsolete vector search indexes to free up resources.
• Deleting test indexes created during development or experimentation.
• Managing lifecycle of vector search indexes programmatically within an automated workflow.

Properties

The only required input property for this operation is the Index Name, which specifies the exact vector search index to be deleted.

Output

The output JSON structure typically contains the response from the Databricks API after attempting to delete the index. It will indicate success or failure of the deletion request.

Example output JSON might look like:

{
  "success": true,
  "message": "Index deleted successfully"
}

If an error occurs, the output will contain error details, such as HTTP status and error message.

No binary data output is expected for this operation.

Dependencies

• Requires an active connection to Databricks via an API authentication token (API key or bearer token).
• The node expects credentials containing the Databricks host URL and an access token.
• Proper permissions on the Databricks workspace to manage vector search indexes are necessary.

Troubleshooting

• Common issues:

  • Incorrect or misspelled index name causing "index not found" errors.
  • Insufficient permissions leading to authorization errors.
  • Network connectivity problems preventing API calls.
  • Expired or invalid API tokens causing authentication failures.

• Error messages and resolutions:

  • API Error: 404 Not Found — Verify the index name exists and is correctly spelled.
  • API Error: 401 Unauthorized — Check that the API token is valid and has sufficient privileges.
  • Network Error: No response received from server — Confirm network connectivity and Databricks endpoint availability.
  • Other API errors usually include a status code and message; consult Databricks API documentation for specific meanings.

• Enabling "Continue On Fail" in the node settings can help workflows proceed despite individual item errors, allowing error handling downstream.

Links and References

• Databricks Vector Search API Documentation (general reference for vector search operations)
• Databricks REST API Authentication
• n8n Documentation on Credentials