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
On snowflake, dbt is incorrectly adding lowercase and uppercase versions of model names to the cache somehow. In particular, models added via add after a materialization is successfully executed are potentially the wrong case.
Issue description
dbt run twice on a snowflake project with casing set defaults (I think?) and lowercase model filenames. If you dump the cache after, you'll see both sets of entries in the cache - correctly uppercased from the initial population and incorrectly uppercased from the add calls.
Results
The cache should only think there's one set of names. On snowflake this is benign because we don't have any relations to drop anyway, but on postgres with odd casing choices (uppercase models + quoting=False) one can imagine problems
System information
Any dbt with caching (0.12+), any OS, any python.
The text was updated successfully, but these errors were encountered:
Issue
On snowflake, dbt is incorrectly adding lowercase and uppercase versions of model names to the cache somehow. In particular, models added via
add
after a materialization is successfully executed are potentially the wrong case.Issue description
dbt run
twice on a snowflake project with casing set defaults (I think?) and lowercase model filenames. If you dump the cache after, you'll see both sets of entries in the cache - correctly uppercased from the initial population and incorrectly uppercased from theadd
calls.Results
The cache should only think there's one set of names. On snowflake this is benign because we don't have any relations to drop anyway, but on postgres with odd casing choices (uppercase models + quoting=False) one can imagine problems
System information
Any dbt with caching (0.12+), any OS, any python.
The text was updated successfully, but these errors were encountered: