You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't cause any big functional problems, such as selecting the wrong resources, because (I believe) selectors are re-parsed/rendered at runtime whenever a --selector flag is passed. It does matter, however, for saving the dict representation of selectors in manifest.json, which happens at parse time. That's increasingly important in a world where we support default selectors (#3448). It's quite confusing to update a yaml selector definition, dbt run --selector my_selector, see that it works, then check the manifest and see an outdated definition.
The text was updated successfully, but these errors were encountered:
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.
Describe the bug
If I change
selectors.yml
and no other files, I still see:This doesn't cause any big functional problems, such as selecting the wrong resources, because (I believe) selectors are re-parsed/rendered at runtime whenever a
--selector
flag is passed. It does matter, however, for saving the dict representation of selectors inmanifest.json
, which happens at parse time. That's increasingly important in a world where we support default selectors (#3448). It's quite confusing to update a yaml selector definition,dbt run --selector my_selector
, see that it works, then check the manifest and see an outdated definition.The text was updated successfully, but these errors were encountered: