dbt seed fails on capital letters in dataset names about dbt-bigquery HOT 5 CLOSED

@caoilte Thank you for pointing this out, after trying to replicate your issue i'm wondering if you could give me a little more context? or additional config information in your projects.yml that might be pointing to a failing cause as we haven't been able to make capitals in either file name of a csv seed file or yml schema cause failure.

from dbt-bigquery.

Hi @McKnight-42 ,
Our steps were,

1. create a GBQ dataset (as part of a model) with a capitalised name (eg "caoilte_Bananas_raw"). This worked fine for a few weeks as a source.
2. create a seed which was assigned to dataset "caoilte_Bananas_raw". This failed with the above.

We never had a problem with capitals in the file names. It was always the dataset that it was assigned to which caused a problem.

However, we've also since banned capitalised letters in our dataset and table names to de-risk ourselves. So if you're unable to reproduce we won't be greatly inconvenienced at this point.

from dbt-bigquery.

@caoilte thank you for the furthered context so far we have tried the following please let me know if I've missed anything.

1. created a seed csv file named test.csv and tried it locally with a dbt seed which worked
2. changed name to Test.csv and tried again which also worked.
3. set up a seed configuration in project.yml for Test which also passed:
   dbt_project.yml

seeds:
    +schema: Test

dbt seed

1 of 1 START seed file dbt_user_Test.test................................... [RUN]
1 of 1 OK loaded seed file dbt_user_Test.test............................... [INSERT 1 in 3.44s]

on pass this also added the dataset dbt_user_Test to my bigquery project.
4. made sure file name and configure name were different which also worked with dbt seed
5. also tried creating a federated table and added it to big query as a table in a dataset and using it as a source for a seed which did not get picked up as the seed file itself wasn't a csv file. (dbt seed didn't fail here just didn't look at the .sql file)

from dbt-bigquery.

Yeah. I'm struggling to reproduce in a fresh project. Maybe there's something weird about our macro to use part of our resource paths as dataset names. happy to close.

from dbt-bigquery.

@caoilte alright, thank you for following up with us, I will close this issue for now if it or something similar comes up again please reach out.

from dbt-bigquery.