Connect Databricks to Uplyst
Approved Databricks tables and views can supply lakehouse data to Uplyst through SQL access. Curated records are mapped to business entities and relationships, bringing analytical calculations into the same context as operational events.
The Databricks SQL Statement Execution API runs statements on SQL warehouses and exposes execution status and results. The chosen catalog, schema, tables and compute endpoint define the dataset available to the integration.
From lakehouse tables to business relationships
Catalog and schema names identify the source dataset. Customer, product and order identifiers relate its records to business entities across applications. Both remain useful: one explains where information originated, while the other connects it to an operational decision.
Historical dimensions, nested fields, currencies and timestamps keep their meaning when mapped into the business model. This lets teams relate an event to the product, customer or contract definition that applied at the time.
| Lakehouse data | Business relationship |
|---|---|
| Customer and product dimensions | Common entities across applications |
| Order and inventory facts | Fulfilment and availability |
| Historical validity periods | Definitions in effect when an event occurred |
| Catalog, schema and table | Traceable source dataset |
Incremental updates from Delta tables
Delta change data feed exposes inserts, updates and deletes with a change type, commit version and timestamp. It supports batch and streaming reads for tables where the feature is enabled.
The initial dataset and subsequent changes need a consistent processing position. Change history is subject to retention, so recovery after a long interruption can require a fresh read of the current table.
Access for automated workloads
Databricks supports OAuth for automated tools and applications. A service principal can represent the integration, with access to the workspace, SQL warehouse and data objects it needs.
Unity Catalog permissions control access to governed data. The connection's identity and resource permissions are configured for the selected workspace and business datasets.
Operational decisions informed by lakehouse data
Supply chain teams can relate curated demand and inventory data to current orders and shipment events. Customer teams can connect analytical segments or activity measures to service and commercial records.
A shared business model makes those relationships available across functions. Dataset freshness and source history provide the context needed to interpret changes in the operational picture.
