Skip to main content

Preflight checks for Databricks

Before running the Databricks crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks will be completed:

JDBC

Schemas

Check successful

Check failed for $missingObjectName

Rest API (Unity Catalog)

User login/UC enabled

Check successful

❌ Source returned error

For example: {"error_code":"403","message":"Invalid access token."}

Catalog

Check successful

Check failed for $missingObjectName catalog

Databricks lineage and usage (miner)

Did you know?

Once you have crawled assets from Databricks, you can extract lineage and usage and popularity metrics.

Login

Check successful

Check failed

For example: {"error_code":"403","message":"Invalid access token."}

Lineage API

Check successful. Lineage API is enabled.

Check failed

For example: Lineage is not enabled for this Databricks account: 47258391-b3c8-4ff9-a0d9-5afc02443806

Query history API endpoint check

Check successful

Check failed