-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support very long path names for compiled artifacts on Windows #2558
Comments
I believe this is pretty fixable! We need to prefix all our paths with |
Right on, thanks @beckjake! This one isn't really an 0.17.0 regression -- I'd be happy to do a cheapo version for 0.17.1 (that just catches the error and logs a warning) in the near-term, then do a more fundamental overhaul of windows pathing for our next scheduled feature release. What do you think? |
I think if we're catching this error, we might as well fix the path and try again, rather than log a warning. |
closed by #2566 |
Describe the bug
A user is reporting an issue when running
dbt compile
. The error is for a schema test .sql artifact, and it reads:My guess is that the full path to this file is too long, and Windows either truncates the file path, or does something else unexpected, when dbt tries to write out this sql file.
Instead, let's catch this error, log a warning, and move on. Alternatively if there's a way to increase the file path length on windows to beyond ~260 chars, we should do that.
This error may start happening for folks on 0.17.0 because we are now including more information (like the
schema.yml
file name) in the path for the.sql
artifact.Steps To Reproduce
dbt compile
on a project that would try to write a filepath > 260 chars longExpected behavior
The output of
dbt --version
:The operating system you're using: Windows 10 (Windows Server 2019)
The output of
python --version
: TBDThe text was updated successfully, but these errors were encountered: