Databricks

Steps to prepare and connect to Databricks

Lightup account setup: Databricks

Make sure that your Databricks workspace meets the following requirements, and gather the following information:

Step 1: Get a personal access token

Lightup connects to a Databricks All Purpose Compute Cluster using a personal access token. If you don't already have one, you can generate one in Databricks on the Access Tokens tab of the User Settings page.

16001600

Step 2: Get connection details for the compute cluster

  1. Click compute iconcompute icon Compute in the sidebar.

  2. Choose a cluster to connect to.

  3. Navigate to Advanced Options.

  4. Click on the JDBC/ODBC tab.

  5. Copy the Server Hostname and HTTP Path field values.

Step 3: Get a Databricks personal access token

  1. Open your Databricks workspace.
  2. Click User Settings IconUser Settings Icon Settings in the lower left corner of your Databricks workspace.
  3. Click User Settings.
  4. Go to the Access Tokens tab.
  5. Click the Generate New Token button.
  6. Optionally enter a description (comment) and lifetime.
10001000
  1. Click the Generate button.
  2. Copy the generated token and store in a secure location.

Step 5. Get your Server Hostname and HTTP Path

Do one of the following:

  • If you're using a SQL endpoint:

    1. Click Endpoints IconEndpoints Icon SQL Endpoints in the sidebar.
    2. Choose an endpoint to connect to.
    3. Navigate to the Connection Details tab.
    4. Copy the Server Hostname and the HTTP Path.\
  • If you're using a compute cluster:

    1. Click compute iconcompute icon Compute in the sidebar.
    2. Choose a cluster to connect to.
    3. Navigate to Advanced Options.
    4. Click on the JDBC/ODBC tab.
    5. Copy the Server Hostname and the HTTP Path.

Query governance

Databricks datasources support Query date range limit and Query history. For steps, see Set query governance settings for a datasource.

Connector settings

  • Workspace URL - The Server Hostname of the compute cluster
  • HTTP Path - The HTTP Path of the compute cluster.
  • Token - The personal access token

Did this page help you?