-
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
Better error handling for compilation exceptions in .yml files #2499
Labels
bug
Something isn't working
Milestone
Comments
3 tasks
beckjake
added a commit
that referenced
this issue
May 29, 2020
…errors add project names/filenames/values to rendering errors (#2499)
closed in #2501 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A malformed yml file can result in an error like:
Instead, this error should include information about the file in which the errant jinja code was found.
Steps To Reproduce
Create a .yml file with the contents:
Note that the columns entry is errantly indented under
meta
.Run
dbt ls
ordbt compile
to see the compilation exception.Expected behavior
I would expect to see the filename containing the errant code in the raised exception.
The output of
dbt --version
:The text was updated successfully, but these errors were encountered: