Databricks Integration Discovered Resources

The Euno Databricks integration discovers and creates the following types of resources in your data catalog:

Resource Discovery Overview

The Databricks integration follows Unity Catalog's hierarchical discovery approach:

1. Databricks Workspace - The top-level workspace container

2. Databases (Catalogs) - Unity Catalog catalogs within the workspace

3. Schemas - Individual schemas within each catalog

4. Tables & Views - Data objects within each schema

5. Tags & Metadata - Governance information at all levels

Databricks Workspace

Resource Type: databricks_workspace

Represents the top-level Databricks workspace.

Properties

Property	Description	Example
name	Workspace name (custom name or hostname)	Analytics Workspace
type	Resource type	databricks_workspace
subtype	Resource subtype	databricks_workspace
database_technology	Platform	databricks

URI Pattern

platform.databricks.databricks_workspace.<hostname>

Example: platform.databricks.databricks_workspace.dbc-50e7cad0-c2f9.cloud.databricks.com

Unity Catalog Database (Catalog)

Resource Type: database

Represents a Unity Catalog catalog within the workspace.

Properties

Property	Description	Example
name	Catalog name	analytics_prod
type	Resource type	database
subtype	Resource subtype	database
database_technology	Platform	databricks
description	Catalog description/comment	Production analytics catalog
owner	The Catalog owner	[email protected]
created_at	Creation timestamp	2024-01-15T10:30:00Z
updated_at	Last modification timestamp	2024-03-01T15:45:00Z
created_by	Creator user	[email protected]
updated_by	Last modifier user	[email protected]
tags	Any Unity Catalog tags where the value is either NULL or empty	class.credit_card
meta	Any Unity Catalog tags where the value is not NULL or empty	{"department": "analytics"}

URI Pattern

databricks.<hostname>.<catalog_name>

Example: databricks.dbc-50e7cad0-c2f9.cloud.databricks.com.analytics_prod

System Catalogs Excluded

The following system catalogs are automatically excluded from discovery:

• system - Databricks system catalog

• samples - Sample datasets catalog

• hive_metastore - Legacy Hive metastore (when present)

Unity Catalog Schema

Resource Type: database_schema

Represents a schema within a Unity Catalog catalog.

Properties

Property	Description	Example
name	Schema name	customer_data
type	Resource type	database_schema
subtype	Resource subtype	database_schema
database_technology	Platform	databricks
description	Schema description/comment	Customer-related data tables
owner	Schema owner	[email protected]
created_at	Creation timestamp	2024-01-15T10:30:00Z
updated_at	Last modification timestamp	2024-03-01T15:45:00Z
created_by	Creator user	[email protected]
updated_by	Last modifier user	[email protected]
tags	Any Unity Catalog tags where the value is either NULL or empty	class.credit_card
meta	Any Unity Catalog tags where the value is not NULL or empty	{"department": "analytics"}

URI Pattern

databricks.<hostname>.<catalog_name>.<schema_name>

Example: databricks.dbc-50e7cad0-c2f9.cloud.databricks.com.analytics_prod.customer_data

System Schemas Excluded

The information_schema schema is automatically excluded from discovery.

Databricks Table, Views and Materialized Views

Resource Type: table

Represents a Databricks managed or external table.

Properties

Property	Description	Example
name	Table name	customers
type	Resource type	table
subtype	Resource subtype	base_table or view or materialized_view
description	Table description/comment	Customer information table
database_technology	Platform	databricks
schema	Schema name	customer_data
database	Catalog name	analytics_prod
owner	Schema owner	[email protected]
created_at	Creation timestamp	2024-01-15T10:30:00Z
updated_at	Last modification timestamp	2024-03-01T15:45:00Z
created_by	Creator user	[email protected]
updated_by	Last modifier user	[email protected]
tags	Any Unity Catalog tags where the value is either NULL or empty	class.credit_card
meta	Any Unity Catalog tags where the value is not NULL or empty	{"department": "analytics"}
sql_dialect	SQL dialect	databricks
materialized	False for views

URI Pattern

databricks.<hostname>.<catalog_name>.<schema_name>.<table_name>

Example: databricks.dbc-50e7cad0-c2f9.cloud.databricks.com.analytics_prod.customer_data.customers

Relationships

The Databricks integration discovers the following relationships between resources:

Parent-Child Relationships

The Databricks integration creates a clear hierarchical structure following Unity Catalog's three-level namespace:

• Databricks Workspace → Catalogs: Catalogs are considered children of their parent workspace

• Catalog → Schemas: Schemas are considered children of their parent catalog

• Schema → Tables & Views: Tables and views are considered children of their parent schema

Container Hierarchy

The complete container hierarchy follows this pattern:

Databricks Workspace
└── Catalog (Database)
    └── Schema
        ├── Table
        ├── View
        └── Materialized View

View Lineage

Databricks views have "upstream/downstream" relationships with other Databricks tables and views based on the SQL definition of the view. This lineage information helps understand data dependencies and impact analysis.