-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CT-524] [Bug] Issue co-locating models and seeds in the same directory #5120
Comments
@azhard thanks for taking the time to submit a ticket and give some great details on reproducibility! I was able to reproduce this behavior. I have a few questions:
While I was able to reproduce this, I am still working on tracking down the reason for this unexpected behavior. I did discover a workaround that would at least allow you to move forward while I track this down. If you delete all the |
Hey @emmyoop thanks for the response, to answer your questions:
Gave the workaround a try but looks like getting a success will require a lot of manual tweaks cause of all the source dependencies for the model |
For some file categories we use an "all_source_paths" method which collects a number of directories from seed-paths, model-paths, snapshot-paths, analysis-paths and macro-paths. When two of them are the same the parsing code reads (and attempts to parse) them twice. |
Would the fix here be something as simple as making this line return a list of unique elements? |
Yes. That's what the pull request does :) #5176 |
Amazing - thanks for the quick turnaround! |
Is there an existing issue for this?
Current Behavior
I’m trying to set the seed-paths to my models folder exactly like described in the docs but getting an error:
Seems like this should be relatively straightforward, not sure why it’s identifying the same source as a duplicate of itself. Relevant parts of the dbt_project.yml file:
Expected Behavior
dbt is able to run (and compile) normally as it did before changing the
seed-paths
.Steps To Reproduce
No response
Relevant log output
What database are you using dbt with?
BigQuery
Additional Context
No response
The text was updated successfully, but these errors were encountered: