Skip to content
BENIBIX Learn

Unity Catalog

Data🧰 PlatformsData Platforms

Also known as Databricks Unity Catalog, Unity Catalog OSS

The list of all data in Databricks. It says who may use what.

Think of it like

It is like the front desk of a big hotel. It knows every room, and it decides who gets a key.

Example

A firm has ten Databricks workspaces. It sets access once in Unity Catalog. An analyst sees the same tables, with the same rights, in each one.

Why it matters

With no shared catalog, each workspace keeps its own rules. Over time, the rules drift apart.

Definition

Unity Catalog is the part of Databricks that guards the data. It keeps one list of all tables, files, models and other data, across every workspace. Each table has a three-part name: catalog, schema and table. Access is granted once, with SQL, and then holds in every workspace. It also tracks lineage, so you can see which tables and jobs feed which. There is an open source version too.

Example code

sql
GRANT SELECT ON TABLE main.sales.orders TO `analysts`;
One grant on a table. The name has three parts: main, then sales, then orders.
Unity Catalog is the middle band. Every way in on top passes through it.

Common mistake

Granting rights to single people. Grant to groups, so a new hire gets access by joining the group.

Key takeaways

  1. 1
    One list. All data across all workspaces.
  2. 2
    Three-part names. Catalog, schema, table.
  3. 3
    Access and lineage. Who may see it, and where it came from.