Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIKE: external tables as model materialization #220

Closed
wants to merge 8 commits into from

Conversation

dataders
Copy link
Contributor

@dataders dataders commented May 21, 2024

alternative to #216

related: dbt-labs/dbt-snowflake#1058

@cla-bot cla-bot bot added the cla:yes label May 21, 2024
Copy link

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

{%- set identifier = model['alias'] -%}
{%- set full_refresh_mode = (should_full_refresh()) -%}

{%- set existing_relation = load_cached_relation(this) -%}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need help here understanding why existing_relation.type returns None when the existing relation is an External Table

@amychen1776
Copy link
Contributor

closing for now because we are revisiting our thoughts on external tables for now

@mikealfare mikealfare deleted the spike_run_external_materialization branch December 6, 2024 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants