uranusjr commented on issue #18482: URL: https://github.com/apache/airflow/issues/18482#issuecomment-926182279
I remember chatting with another developer on this. Note that this seems to be problem specific to JDBC; after #16805 (the PR fixing #16564), most task errors can correctly be logged—but not JDBC. In fact, the JDBC error does not even go through the code path implemented in the PR; when using JDBCOperator, you get *no errors at all*, not the *Task failed with exception* message an exception would normally trigger (for example, the Postgres example above would emit this log). My current hypothesis is JDBC (or the operator/hook) is swallowing the exception somehow and the scheduler never actually received it, let alone logging. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
