-
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-3210] [Bug] Error using dbt list --select
when there is a cross-project model that is version=0
in the parent project
#8836
Comments
Just a little bit more context-- not every |
I was able to reproduce this error, but it was not restricted to models with version == 0, so I'm going to update the issue title. It was restricted to versioned models within the parent project though. Here's the line of code that ultimately threw the error:
ReprexParent project
name: "my_parent_project"
...
select 1 as id
models:
- name: dim_customers
access: public
versions:
- v: 1 Child project
select * from {{ ref('my_parent_project', 'dim_customers') }} Within the child project, try to do any selection with
Stacktrace
|
dbt list --select
when is a cross-project model that is versioned in the parent project
dbt list --select
when is a cross-project model that is versioned in the parent projectdbt list --select
when there is a cross-project model that is versioned in the parent project
Added a fix in #8915 for scenario where @dbeatty10 I'm unable to reproduce the behavior for |
dbt list --select
when there is a cross-project model that is versioned in the parent projectdbt list --select
when there is a cross-project model that is version=0
in the parent project
@aranke and I just finished pairing on this. Indeed, |
…8921) Co-authored-by: Kshitij Aranke <kshitij.aranke@dbtlabs.com>
…8922) Co-authored-by: Kshitij Aranke <kshitij.aranke@dbtlabs.com>
Is this a new bug in dbt-core?
Current Behavior
When you attempt to reference a model version 0, you get a stack trace error.
Expected Behavior
We should allow you to set model version to be 0.
Steps To Reproduce
v: 0
select * from {{ ref('example_hub', 'my_second_dbt_model', v=0) }}
dbt list --select anything
Outstanding question - is this only affecting cross-project refs? Or all refs to a model with
v: 0
?Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: