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

[Feature] Specifying select fields in .yml for snapshots #11180

Open
3 tasks done
asarraf opened this issue Dec 30, 2024 · 2 comments
Open
3 tasks done

[Feature] Specifying select fields in .yml for snapshots #11180

asarraf opened this issue Dec 30, 2024 · 2 comments
Labels
enhancement New feature or request triage

Comments

@asarraf
Copy link

asarraf commented Dec 30, 2024

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

With the new way of creating and maintaing Snapshots, I see that there isn't a way to specify the list of columns that we want want to provide.
This issue is to add a functionality to accept select as one of the items in the yml that can be used to do a
select col1, col2.. from model

instead of creating a ephemeral model and then doing select *

Describe alternatives you've considered

No response

Who will this benefit?

This will help whoever is using the DBT latest version so that they don't have to maintain an ephemeral models as well in the repository.

Are you interested in contributing this feature?

Yes, I am stilll learning.

Anything else?

References -> https://docs.getdbt.com/docs/build/snapshots#configuring-snapshots

@asarraf asarraf added enhancement New feature or request triage labels Dec 30, 2024
@jeremyyeo
Copy link
Contributor

The recommendation is to use an ephemeral (where you can specify the columns you need from your source) and snap that instead 😊

@asarraf
Copy link
Author

asarraf commented Jan 2, 2025

Yes, I am suggesting if we want to use a materialized table with only a specific set of columns w/o any ephemeral model, the --select could be quite beneficial. Why create one more model, if we can add select columns. Seems more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage
Projects
None yet
Development

No branches or pull requests

2 participants