Release Notes > Connector and connectivity issues > Databricks Connector
  

Databricks Connector

Fixed issues

The tables in this section describe recent fixed issues for Databricks connector in Metadata Command Center. Not all monthly releases include fixed issues.
April 2025 fixed issues
Issue
Description
SCAN-18686
When you run a job to extract lineage from a Unity Catalog source, the job succeeds with the following error in the debug logs: samples.accuweather.forecast_daily_calendar_metric
SCAN-17815
Metadata extraction jobs fail with a null point exception.
This issue occurs when a notebook refers to another notebook with an incorrect relative path.
MDP-5953
When you run a data profiling job on tables from multiple databases, the job fails.
This issue occurs when you do not specify the catalog source name in the connection properties.
February 2025 fixed issues
Issue
Description
SCAN-14903
When you extract metadata from a large number of views, the job fails with the following error: Out of Memory
SCAN-13823
When you run a catalog source job with the PySpark module and you use the net.snowflake.spark.snowflake.Utils.runQuery method, Data Governance and Catalog doesn't display the lineage and generates the following error: Unable to resolve sc._jvm.net
April 2024 fixed issues
Issue
Description
CDGC-61037
When you run data profiling tasks on delta tables of a Databricks catalog source that contains column names starting with numbers, the profiling task fails with the following error: UNRESOLVED_COLUMN.WITH_SUGGESTION
SCAN-360
When you run a Databricks Notebook catalog source job which calls a notebook located inside the "/Workspace" folder, and the job doesn't provide the "/Workspace" prefix, the job fails with the unknown notebook error.