How is Unity Catalog different from the Hive Metastore?

Hive Metastore is legacy — table-level ACLs only, no lineage, no cross-workspace sharing. Unity Catalog is the next-generation governance layer — fine-grained (row, column) access, automated lineage, search, and centralised across the account.

Unity Catalog in Databricks: Governance Guide

Q: What is Unity Catalog in Databricks?

Unity Catalog is Databricks' unified governance solution for data and AI. It provides a single place to manage tables, files, functions, and ML models — with fine-grained access control, automated lineage, search, and cross-workspace sharing.

Q: What are the three-level namespace in Unity Catalog?

Unity Catalog uses a 3-level namespace: catalog.schema.table (e.g., main.sales.orders). Each level can have its own access policies. This is more flexible than the legacy database.table structure.

Q: Does Unity Catalog support row-level and column-level security?

Yes — Unity Catalog supports row filters and column masks (masking policies). For example, you can mask PII columns to non-privileged users and apply row filters based on region.

Q: Does Unity Catalog provide data lineage?

Yes — Unity Catalog captures automatic column-level lineage across Spark jobs, Delta Live Tables, and SQL warehouses. Lineage flows upstream and downstream.

Q: Is Unity Catalog free?

Yes — Unity Catalog is included free with all Databricks deployments (AWS, Azure, GCP). Premium features like column-level lineage are included in the platform.

Unity Catalog in Databricks — Quick Answer

Unity Catalog is Databricks\' unified governance solution for data and AI. It provides a single place to manage tables, files, functions, and ML models — with fine-grained access control, automated lineage, search, and cross-workspace sharing. It replaces the Hive Metastore as the default governance layer and is included free with every Databricks deployment.

Unity Catalog — Three-Level Namespace

Unity Catalog uses a 3-level namespace:

catalog.schema.table Example: main.sales.orders main.marketing.customer_segments sandbox.dev.experimental_features

Level	Purpose
Catalog	Top-level grouping — typically per environment (main, dev, sandbox) or domain
Schema	Logical grouping of tables — like a database in PostgreSQL
Table	The actual table or view

Each level can have its own access policies. This makes it easy to isolate environments (dev vs prod) and apply governance by domain.

Feature	Hive Metastore (Legacy)	Unity Catalog
Granularity	Database + Table	Catalog + Schema + Table
Access Control	Table-level ACLs only	Row + Column-level filters/masks
Lineage	None	Automatic column-level lineage
Cross-Workspace Sharing	Manual	Delta Sharing native
Search	None	Built-in tag + text search
External Integrations	Limited	Power BI, Tableau, MLflow, Lakehouse Federation

Feature

Hive Metastore (Legacy)

Unity Catalog

Granularity

Database + Table

Catalog + Schema + Table

Access Control

Table-level ACLs only

Row + Column-level filters/masks

Lineage

None

Automatic column-level lineage

Cross-Workspace Sharing

Manual

Delta Sharing native

Search

None

Built-in tag + text search

External Integrations

Limited

Power BI, Tableau, MLflow, Lakehouse Federation

-- Row filter: only show rows for user's region CREATE FUNCTION sales.filter_region(region STRING) RETURN IF(is_account_group_member('sales_americas'), TRUE, region = 'apac'); ALTER TABLE sales.orders SET ROW FILTER sales.filter_region(region); -- Column mask: hide salary from non-privileged users CREATE FUNCTION sales.mask_salary(salary DECIMAL(10,2)) RETURN IF(is_account_group_member('hr_managers'), salary, '****'); ALTER TABLE hr.employees ALTER COLUMN salary SET MASK sales.mask_salary;

Integration	What It Does
MLflow	Register and govern ML models in Unity Catalog
Power BI / Tableau	Direct query Unity Catalog tables via partner connect
Lakehouse Federation	Query PostgreSQL, MySQL, Snowflake, BigQuery without copies
Delta Sharing	Share data with external organisations
Databricks SQL	Native governance for ad-hoc SQL queries

Integration

What It Does

MLflow

Power BI / Tableau

Direct query Unity Catalog tables via partner connect

Lakehouse Federation

Query PostgreSQL, MySQL, Snowflake, BigQuery without copies

Delta Sharing

Share data with external organisations

Databricks SQL

Native governance for ad-hoc SQL queries

Step 1 — Inventory: Run a script to list all tables in the legacy metastore. Group by database and identify ownership.
Step 2 — Catalogue Mapping: Map legacy databases to Unity Catalog schemas. For example, prod.sales.orders → main.sales.orders.
Step 3 — Permissions Translation: Convert legacy GRANT statements to Unity Catalog ACLs. Map users to groups via SCIM.
Step 4 — External Locations: Configure storage credentials and external locations for S3/ADLS access.
Step 5 — Cutover: Migrate table-by-table with a parallel-run period. Update notebook references from hive_metastore.db.table to main.db.table.
Step 6 — Decommission: Once everything runs on Unity Catalog, disable Hive Metastore.

A full migration takes 2–4 weeks for a medium data team. Unity Catalog tools (terraform-databricks-uc) automate much of this.

Pitfalls

Avoid these traps when adopting Unity Catalog:

Skipping catalog per environment: One catalog for everything is a governance nightmare. Use separate catalogs for prod, dev, sandbox.
Not tagging tables: Tags power search and policy. Tables without tags are invisible to the data discovery workflow.
Over-granting access: Grant only what is needed. "ALL PRIVILEGES" on a catalog is rarely justified.
Ignoring audit logs: Every access is logged. Review the audit log monthly for unexpected access patterns.
Mixing Hive Metastore and Unity Catalog: Mixing the two creates governance gaps. Migrate fully or stay fully legacy.

Quick Reference — Cheatsheet

catalog.schema.table is the 3-level namespace — use it for env isolation.
Row filters and column masks implement row/column-level security.
Automatic column-level lineage flows across all jobs.
Delta Sharing enables secure cross-org data exchange.
Unity Catalog is free — included with all Databricks deployments.

Frequently Asked Questions

What is Unity Catalog in Databricks?

Databricks' unified governance for data and AI — fine-grained access, lineage, search, cross-workspace sharing.

How is Unity Catalog different from Hive Metastore?

Hive Metastore is legacy — table-level ACLs only, no lineage. Unity Catalog is next-gen with row/column security, sharing, and lineage.

What are the three-level namespace in Unity Catalog?

catalog.schema.table (e.g., main.sales.orders). Each level can have its own access policies.

Does Unity Catalog support row-level and column-level security?

Yes — row filters and column masks via SQL functions.

Does Unity Catalog provide data lineage?

Yes — automatic column-level lineage across Spark, DLT, and SQL warehouses.

Is Unity Catalog free?

Yes — included free with all Databricks deployments.

Unity Catalog in Databricks: Governance Explained

Unity Catalog in Databricks — Quick Answer

Unity Catalog — Three-Level Namespace

Related Articles

DP-203 Certification Cost and What Replaced It

Grok 4.7 Launches at $2 per Million Tokens

Meta Connect 2026: Muse Watermelon, Open Weights - Preview

Databricks Invests $350M in Singapore, to Train 20,000

Try It in the Browser

Unity Catalog vs Hive Metastore

Unity Catalog Key Features

Row-Level and Column-Level Security Example

Unity Catalog Integrations

Unity Catalog Best Practices

Common Unity Catalog

Real-World Example — Migrating to Unity Catalog