-
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
Parity for source freshness task/command #2987
Comments
When running this command, I also think it should have a summary statement which it doesn't have right now (e.g. 10 models pass, etc.). Do you consider this part of parity or should it be a separate issue @jtcohen6? |
Good call @emilieschario! I think we could work that into this issue for now, and we'll split it out if we need to. In general, we don't make the same commitments today about log / stdout stability as we now do for artifacts and user-supplied code. There's a lot of little stdout things I'd like to tidy up or touch up, but they're not high-priority prerequisites for 1.0. |
|
@jtcohen6 2 quick questions:
|
|
@jtcohen6 |
@Kiollpt Yes, that should work now! Have you given it a try with a recent version of dbt (v0.21+)? |
@jtcohen6 It works well after I tried. |
Describe the feature
dbt source snapshot-freshness
is quite limited and a bit verbose relative to other dbt task-commands.Source freshness should support full node selection syntax, including things like:
--select tag:something
(Ability to run snapshot-freshness with tag selection #2369)--exclude
and--selector
(Add --exclude for source snapshot-freshness #2729)--select +downstream_resource
, i.e. check freshness of all sources upstream ofdownstream_resource
. I think this would be especially compelling for exposures!Should this be renamed to avoid confusion with
dbt snapshot
? I think yes, and it could be as simple as calling itdbt source freshness
instead—although that's not a verb! Open to suggestions.We'd obviously do the renaming in a way that's backwards-compatible. Ideally, we'd rename and add functionality in the same release.
Describe alternatives you've considered
Leaving
dbt source snapshot-freshness
as is: clunky to type, wonky to useAdditional context
Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here.
Who will this benefit?
All current and potential users of source freshness, which is a relatively underused + under-appreciated feature! Maybe in part because it feels a bit clunky :)
The text was updated successfully, but these errors were encountered: