[BUG]: Views migration should not throw blocking errors

[nkvuong]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Customer is currently migrating tables & views within a single database. Some views are referring to tables in other databases, and therefore should be skipped, instead of throwing errors such as below

Expected Behavior

No response

Steps To Reproduce

No response

Cloud

AWS

Operating System

macOS

Version

latest via Databricks CLI

Relevant log output

No response

[ericvergnaud]

@nkvuong from the snapshot I'm not seeing the problematic table, can you provide a better one ?

[ralphkootker]

I'm migrating the hive_metastore to Unity Catalog for one of our customers.
This customer has many databases in the HMS and we have only selected 1 database to migrate first.

This database has views, and the customers practice prescribes using views when querying cross database. As we migrate just 1 database to UC and not all, the view will become a bit messy.

The error thrown is not straightforward and context about cross database reference would be helpful.

Workaround: For now, we will recreate the views manually, temporary points to objects in the HMS as well as Unity Catalog until the migration is completed in full.

[ericvergnaud]

Could be a duplicate of #1798, which is already fixed. Can you check ?

[nfx]

Please upgrade to the latest version. It seems that the version you're referring is too old.