-
Notifications
You must be signed in to change notification settings - Fork 64
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
[Feature] Support Iceberg table format for dbt Snapshots #690
Comments
Hello @maurofloriano - I'm curious if you would be able to share why you would want to create dbt snapshots as iceberg table format? |
Hey! thanks for the reply. So, on our context, we plan to create anything as iceberg tables. So would be nice to create seeds, snapshots, tables all options that dbt have it, would be interesting in our usecase to make it available for users in iceberg format. |
Thanks @maurofloriano! At this time, we don't have plans to support snapshots but I'm very excited to see the community response and have more folks upvote for this feature so that we might add it to the roadmap. |
Hey @maurofloriano ! I had a customer of mine ask about the same possibility- materializing snapshots as iceberg tables. While we get this prioritized on our roadmap, you can take a look at an illustration of some working code that overrides the default snapshot materialization to achieve the same goal. See my gist for details. |
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Is this your first time submitting a feature request?
Describe the feature
During tests, verified that when trying to create a snapshot via dbt, even passing iceberg configurations, dbt create as simple table instead of creating as iceberg table.
Describe alternatives you've considered
Also add this feature for the flow that creates snapshot.
Who will this benefit?
Whoever is going to use iceberg tables as default in snowflake.
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: