Our team creates personal schemas for users for development, such that when you’re iterating, you’re doing so against model versions in your own personal schema rather than what’s deployed and run by CI in staging/prod.
When starting development or attempting to run & test a model as part of reviews, it can be a very slow and painful experience if the model in question has a large DAG of upstream dependencies.
state-based selection can help during iteration, but doesn’t remove the initial overhead for development (and particularly if someone just wants to run or test a specific model as a one-off).
Alternatively I could think of creating our own
ref()override which perhaps based on some local config state could switch between referencing a dbt model or point at a specific exiting table.
I’m wondering if anyone has hit similar issues, and how you might have resolved this.