Privileges Required to use Databricks Connector
To use Databricks, you need one of the following:
scheduler-administrator
orredwood-administrator
role.scheduler-user
orredwood-login
role in combination with the following system-wide, partition-wide or object-level privileges.
Built-in Roles
- The
scheduler-administrator
orredwood-administrator
built-in role provides full control over Databricks. - The
scheduler-viewer
built-in role provides read-only access to Databricks.
Creating, Modifying, and Deleting Databricks Connections
You need all of the following privilege ranks to be able to create, modify, and delete Databricks:
- View or any other rank - on the Redwood_Databricks application.
- View or any other rank - on the Redwood_DatabricksConnectionConstraint constraint.
- View or any other rank - on the Redwood_DatabricksConnection extension point.
- View or any other rank - on the Redwood_Connections extension point.
- View or any other rank - on the existing process server and queue for the connection, if applicable.
- Create - on process server and queue, if these need to be created.
- Edit - on DBKConnection if you want to be able to manage all Databricks connections.
Using Databricks
- View or any other rank - on the Redwood_Databricks application.
- View or any other rank - on the Redwood_DatabricksConnectionConstraint constraint.
- View or any other rank - on the Redwood_DatabricksConnection extension point.
- View - on DBKConnection, EXTConnection, EXTObjectRefs, and EXTCertificate.
- View - on the component's process server.
- JobAdministrator - on the component's queue.
- View - on REDWOOD.Redwood_Databricks library.
- Submit - on process definitions you wish to use.