-
Notifications
You must be signed in to change notification settings - Fork 908
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
Clearer underlying dataset issues #3971
Comments
It is unclear why those logs don't show tracebacks. Anyway, the current implementation of Lines 192 to 202 in adfc593
|
They must be in the |
Thank you @datajoely! Could you please provide some more context on what AWS service was used to run kedro pipeline? We would like to check if the service is filtering the error messages as it seems like we always showcase the entire error log. |
I've asked the user to comment here to double check, but I think it was:
|
First, I amend my comment above: the traceback is there ( The problem of |
In #2943 we partly addressed the issue of unclear errors with datasets. Yet we have a bit more evidence about this still being a problem. The user was getting
but the actual underlying error was:
Another internal user reported this today. |
Description
A user reported that Kedro was unable to read the CSV, they get the following logs in AWS:
The "No columns to parse from file" is being thrown by the underlying pandas implementation in this file
It would be helpful if Kedro could bubble up that the error is thrown in
pandas.io.parsers.python_parser
so that it is clear where the issue lies. The error above, mentionskedro.io.core.DatasetError
is it not possible to do the same?The text was updated successfully, but these errors were encountered: