databricks as ingestion source type

datahub-project · Dec 11, 2023 · bfd5a53 · bfd5a53
1 parent 796a537
commit bfd5a53
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/metadata-ingestion/setup.py b/metadata-ingestion/setup.py
@@ -395,6 +395,7 @@
     "powerbi-report-server": powerbi_report_server,
     "vertica": sql_common | {"vertica-sqlalchemy-dialect[vertica-python]==0.0.8.1"},
     "unity-catalog": databricks | sql_common | sqllineage_lib,
+    "databricks": databricks | sql_common | sqllineage_lib,
     "fivetran": snowflake_common,
 }
 

diff --git a/metadata-ingestion/src/datahub/ingestion/source/source_registry.py b/metadata-ingestion/src/datahub/ingestion/source/source_registry.py
@@ -14,3 +14,12 @@
     "mssql-odbc",
     "mssql",
 )
+
+# Use databricks as alias for unity-catalog ingestion source.
+# As mentioned here - https://docs.databricks.com/en/data-governance/unity-catalog/enable-workspaces.html,
+# Databricks is rolling out Unity Catalog gradually across accounts.
+# TODO: Rename unity-catalog source to databricks source, once it is rolled out for all accounts
+source_registry.register_alias(
+    "databricks",
+    "unity-catalog",
+)