-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add --exclude for source snapshot-freshness #2729
Comments
Historical note: this goes back to the implementation of snapshot-freshness, it was never in the original spec. I can't remember if that was by design, a "we'll do it later", or just accidental. I think fixing this will require edits in two places:
It's possible this is more complicated than I'm thinking, but I don't see why that would be. @jtcohen6 we should decide if source freshness deserves to get selectors, too - right now that's also not wired up (I think because |
Thanks for opening this, @tayloramurphy. Even if it isn't a frequent need, I'm definitely in favor of bringing @beckjake I think that feature parity with Side note: I know source configs today only contain
|
This just bit us - after posting this message about excluding a test provided by a Fivetran package which checks a table we aren't syncing, I thought I could maybe do |
👍 Would find this helpful |
Describe the feature
Add
--exclude
to source snapshot-freshnessDescribe alternatives you've considered
Not having this breaks the syntax model that's expected for basically every other dbt selection command.
Additional context
I'm on Snowflake, but should work for all.
Who will this benefit?
Evidently very few people are doing this, but I can share how we're wanting to use it. Basically, we're isolating our source extractions into separate dags with the following dbt plan:
As we're migrating to this pattern I want to be able to exclude from our main freshness dag the models I've already broken out, but I can't.
Are you interested in contributing this feature?
I can if you point me in the right direction!
The text was updated successfully, but these errors were encountered: