-
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-232] Setting enabled to False in schema config does not move model to disabled #3992
Comments
In addition, I don't think we ever remove models from 'disabled', which didn't matter that much without partial parsing, but probably should be fixed. And a model that starts out 'disabled' can now be subsequently enabled via patch config, so we need to apply patches to disabled nodes and put them in the right place. I'm actually wondering why we have a separate place for 'disabled' models and if it's necessary. It would be simpler to just change the config in the nodes and leave them where they are, skipping them for some purposes. I suspect some of that at least is already in place or the errors in this would be showing up. |
Leaving them in |
Hey team, looks like the following scenario is related ( A barebones project with 3 models: -- my_model.sql
select 1 as user
-- my_model_2.sql
select * from {{ ref('my_model') }}
-- my_model_3.sql
select * from {{ ref('my_model_2') }} A version: 2
models:
- name: my_model
- name: my_model_2
config:
enabled: false
- name: my_model_3
config:
enabled: false And a command like
|
@gshank Would you be able to take a look at the reproduction case @jeremyyeo laid out, when you get a chance? Since more folks have upgraded to v0.21+, we should expect to see more users trying |
Any update on this issue? My team is trying to move all our configs into the YAML files but are blocked by this bug. |
In the model node, NodeConfig.enabled equals False, but because the node isn't moved into the disabled dictionary, it doesn't have the correct error messages. Instead of the node is disabled messages, nodes referring to the disabled node cause an error "Model ... depends on a node named ... which was not found".
The text was updated successfully, but these errors were encountered: