-
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
[CT-1361] dbt CLI preview command #6087
Comments
hi @TylerHillery, thanks for opening this and working on it at the Coalesce hackathon! I wanted to let you (and anyone else reading) know that we're very interested in adding this new CLI command, but we won't be proceeding with the PR from the hackathon. the primary reason for this is that for v1.4 we're refactoring our internal Python APIs, notably reworking the CLI into a new framework -- so we'd need to merge this and then completely redo it anyway if you or anyone is interested in contributing this once we have a bit more concrete next steps from the CLI rework, let us know! otherwise it's something we'll get in ourselves |
@lostmygithubaccount Thanks for letting me know! Once you have more concrete steps I would definitely like to help out |
Going to close this issue in favor of a newer one, with more specificity on the implementation we'll be pursuing: #6359 @TylerHillery Would be happy to have your thoughts there on some of the open questions! |
Is this your first time submitting a feature request?
Describe the feature
Be able to run
dbt preview my_dbt_model
to show the results of the model in the terminal similar to the preview functionality in dbt cloud.Describe alternatives you've considered
No response
Who will this benefit?
dbters who live in the CLI. Being able to preview the results of a model before it materializes in the database can be helpful to see if the output matches the user's expected behavior.
Are you interested in contributing this feature?
Yes, working on it for the hackathon project
Anything else?
I have a GitHub discussion open about this feature request.
The text was updated successfully, but these errors were encountered: