Today, information_schema does not work as expected when the name of a catalog is changed, as the catalog-specific views are written at create time and not updated. While I'm pursuing that fix internally, switching over to system for all information_schema queries will fix this. Unclear yet whether this will have any performance or governance implications (testing currently), though since all of the catalog-specific views reference system under the hood, I wouldn't expect any.
Checklist
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.
Resolves #691
Description
Today, information_schema does not work as expected when the name of a catalog is changed, as the catalog-specific views are written at create time and not updated. While I'm pursuing that fix internally, switching over to system for all information_schema queries will fix this. Unclear yet whether this will have any performance or governance implications (testing currently), though since all of the catalog-specific views reference system under the hood, I wouldn't expect any.
Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.