-
Notifications
You must be signed in to change notification settings - Fork 24
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
Exceptions don't tell you which sink caused the exception #128
Comments
Not fully solved by #129 but pretty close, we could probably close this, but it would be a good idea to review the code to see if we're catching most cases already or not, if not we should add some error handling |
Maybe meltano/sdk#1854 could help? Though this target is stuck on an older version of the SDK because the test factory changes broke tests here. |
I don't think we're calling a logger right now for most exceptions if we were I think your solution would do the trick. A "global" exception handler for the tap workflow could do the trick (I think?) |
Streams do log all unhandled errors so perhaps sinks should do something similar: https://github.com/meltano/sdk/blob/76625a81db8df02eafacd56d6e1313d32e3e7aa1/singer_sdk/streams/core.py#L1189-L1194 |
It would be extremely helpful if this included the sink (table) that had this happen at, when you have 100's of tables running it's hard to pinpoint where the error is coming from. Similar to #119
The text was updated successfully, but these errors were encountered: