xBis7 commented on PR #70351: URL: https://github.com/apache/airflow/pull/70351#issuecomment-5632847792
What is the goal of changing the exception class? Is it to take a step closer to cleaning up the `AirflowException` type or is it to make sure that when we get an error, it's easier to debug it? > because it will break the retry mechanism that is based on detecting the exception type. I've looked at the code and I don't think that there is an issue there. I don't see any check for `AirflowException`. But there is a good chance that users are wrapping the operator's `execute()` call with a `try - except AirflowException`. As far as users are concerned, this is a breaking change, just like @jason810496 said. If we can determine the goal for this change, then we can figure out what direction to follow. For example, if this change is going to happen across all operators then we might want to create a new class type extending `AirflowException` as already suggested. -- 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]
