@ashb As we are handling only OperationalError so this will handle only
"Exception raised for errors that are related to the database's operation and
not necessarily under the control of the programmer, e.g. an unexpected
disconnect occurs, the data source name is not found, a transaction could not
be processed, a memory allocation error occurred during processing, etc."
we think that these intermittent issues should not bring the whole scheduler
down.
Any other DB related issue will bring the scheduler down as they will come
under different class .
|__Error
|__InterfaceError
|__DatabaseError
|__DataError
|___OperationalError_
|__IntegrityError
|__InternalError
|__ProgrammingError
|__NotSupportedError
[ Full content available at:
https://github.com/apache/incubator-airflow/pull/3650 ]
This message was relayed via gitbox.apache.org for [email protected]
