Skip to content

[BUG]: Reconciliation fails with UNRESOLVED_COLUMN error on Foreign Catalogs (Lakehouse Federation) #2366

@moomindani

Description

@moomindani

Category: Reconcile bug

Current Behavior

When running Lakebridge Reconcile with a Foreign Catalog (created via Lakehouse Federation) as the source, all report types (schema, data, row, all) fail with:

[UNRESOLVED_COLUMN.WITH_SUGGESTION] A column, variable, or function parameter
with name `full_data_type` cannot be resolved.

This is because DatabricksDataSource.get_schema() queries information_schema.columns using the full_data_type column, which is Databricks-specific and does not exist in Foreign Catalog's information_schema.

Expected Behavior

Reconcile should work with Foreign Catalogs as source/target, falling back to an alternative schema fetching method (e.g. DESCRIBE TABLE) when full_data_type is unavailable.

Steps To Reproduce

  1. Create a Foreign Catalog via Lakehouse Federation (e.g. PostgreSQL, Teradata)
  2. Configure Lakebridge Reconcile with data_source="databricks" using the Foreign Catalog as source
  3. Run reconcile with any report_type
  4. Schema fetch fails with UNRESOLVED_COLUMN error

Relevant log output

[UNRESOLVED_COLUMN.WITH_SUGGESTION] A column, variable, or function parameter
with name `full_data_type` cannot be resolved.
Did you mean one of the following? [`data_type`, ...]

Operating System: macOS
Version: latest via Databricks CLI (v0.12.2)

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions