Compatibility with dbt-fusion

[matt-winkler]

Describe the feature

Ensure dbt-external-tables is compatible with the new dbt-fusion engine.

Describe alternatives you've considered

Bad alternative: Guide end users to code their own macros / custom materializations to implement the same functionality in dbt-external-tables.

Additional context

All databases supported by dbt-fusion:

• Snowflake
• Bigquery
• Databricks
• Redshift

NOTE: this list will evolve as more supported databases come online. The concept of using external tables may not apply for all database back ends.

Who will this benefit?

Users who leverage dbt in conjunction with reading data from tables external to, but accessible from, the data warehouse back end (e.g. data residing in S3, GCS, ACS)

[matt-winkler]

@dataders I think we're in a holding pattern until the linked issues above are resolved. Agree?

[dataders]

@matt-winkler this is definitely on hold until after Coalesce.

that said, Snowflake seems to be in good working order? I might ask to see if there's users who might want to take this branch for a spin.

also i just added more sub issues that are more docs related that anyone could pick up

[matt-winkler]

@dataders I was seeing a similar data type / column issue at the dbt test step on snowflake as for bigquery. So don't think we're quite there yet on that adapter.

[dbeatty10]

Here's the error I'm seeing when running the last step of the integration_tests for Snowflake.

I'll open an issue in the dbt-fusion repo if I can't find one.

$ dbt test --target snowflake                       

dbt-fusion 2.0.0-preview.72
   Loading profiles.yml
   Loading packages.yml
 Analyzing [━━                  ] 2/21 1 succeeded | 19 in-progress
   test:0726cb6195 [0.0s], test:4cc843fd7b [0.0s], test:7897e6d554 [0.0s], test:f58da458ba [0.0s], test:2e95e54680 [0.0s], test:c9b77c1fc1 [0.0s], test:38bbc25113 [0.0s], ...   panic: panicked at crates/dbt-tasks/src/runnable/test.rs:202:25:
Failed to receive task result for test.dbt_external_tables_integration_tests.source_equality_snowflake_exte_ac4584a424af72e8d0c4c4ebff35fbef.c9b77c1fc1
panic: panicked at crates/dbt-tasks/src/runnable/test.rs:202:25:
 Analyzing [━━━━━━━╾            ] 8/21 7 succeeded | 13 in-progress
   test:0726cb6195 [0.0s], test:4cc843fd7b [0.0s], test:7897e6d554 [0.0s], test:f58da458ba [0.0s], test:2e95e54680 [0.0s], test:c9b77c1fc1 [0.0s], test:38bbc25113 [0.0s], ...

And here's the content of logs/dbt.log:

==================== 2025-12-05 15:38:07.454292 | 019aef29-d4d9-7473-be47-9ef6adc54cc4 ====================
dbt-fusion 2.0.0-preview.72
   Loading profiles.yml
   Loading packages.yml
15:38:07.886174 [error]: dbt0227: No column EMAIL_ALIAS found. Available are A.EMAIL, A.LAST_NAME, A.VALUE, A.FIRST_NAME, A.ID
  --> target/generic_tests/source_equality_snowflake_exte_4f65b193d12c321b4a0b50f88d8bb8cc.sql:1:1 (target/compiled/generic_tests/source_equality_snowflake_exte_4f65b193d12c321b4a0b50f88d8bb8cc.sql:23:39)
15:38:07.886231 [error]: dbt0227: No column EMAIL_DOMAIN found. Available are A.email_domain, A.EMAIL, A.LAST_NAME, A.FIRST_NAME, A.ID, A.VALUE
  --> target/generic_tests/source_equality_snowflake_exte_ac4584a424af72e8d0c4c4ebff35fbef.sql:1:1 (target/compiled/generic_tests/source_equality_snowflake_exte_ac4584a424af72e8d0c4c4ebff35fbef.sql:23:46)