Closed garfieldthesam closed 1 year ago
Thanks for flagging this! No misunderstanding, there's a typo in the last variable: the B is missing, it should be upstream_prod_fallback
. I've fixed this on main and will create a new release soon. As long as tbl1
has been built in your dev environment, the package should work exactly as you expect.
Just FYI, upstream_prod_enabled
defaults to True
and should only need to be set if you want to temporarily disable the package globally.
This might be a misunderstanding of how the package works so please let me know if this is just an unsupported feature.
Using
dbt-bigquery
I have a config like this in myprofiles.yml
forupstream_prod
:Where
prod_schema_prefix
matches the prefix applied to the many prod schemas in our data warehouse (eg. there's my personal dev schemas likedbt_myname_staging
and prod schemas likeprod_schema_prefix_staging
).I have created a new table
tbl1
and updatedtbl2
to query fromtbl1
likefrom {{ ref("tbl1") }}
. When this compiles withupstream_prod_enabled: True
, it compiles asfrom None
.