About the Databricks activities

Databricks activities for the Integration Service connector, for job orchestration, notebook management, Unity Catalog, Genie, and Vector Search.

注:

The Databricks connector is available as a preview feature.

Databricks activities enable you to automate a Databricks workspace over its REST API: submit and monitor notebook job runs, manage Unity Catalog volumes and functions, import and export notebooks, converse with Genie, and query Vector Search indexes.

動作のしくみ

To enable the outbound automation between UiPath and Databricks, the activities establish an authenticated connection using the UiPath Databricks connector. The connector calls the Databricks workspace REST API as a service principal, using OAuth 2.0 client credentials (machine-to-machine).

Building your first project requires completing the steps in the Databricks authentication guide from the connector documentation first.

Long-running operations

Several Databricks operations are asynchronous. The activities follow the Databricks API model for these:

• SQL — Execute a SQL Query waits synchronously for the duration set in Wait Timeout. For statements that run longer than that, setting Wait Timeout to 0s and On Wait Timeout to CONTINUE causes the activity to return a statement ID immediately, which can then be polled with Get SQL Statement Result.
• Jobs — Run a Job Now and Run a Notebook return a run ID immediately, which can be polled with Get a Job Run until the run reaches a terminal state; the result is then available through Get a Job Run Output.
• Genie — Start a Conversation and Create a Conversation Message return a message that is still being generated, which can be polled with Get a Conversation Message until its status is COMPLETED; the rows are then available through Get Genie Query Results.

Endpoints without a predefined activity

Use the Databricks HTTP Request activity to call any Databricks workspace REST API endpoint with the same connection.

トリガー

This connector does not support triggers.