You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/08/11 20:36:00 UTC

[GitHub] [airflow] malthe edited a comment on pull request #17545: Airflow exceptions pass-thru during "on_execute_callback"

malthe edited a comment on pull request #17545:
URL: https://github.com/apache/airflow/pull/17545#issuecomment-897133662


   @kaxil it's an option of course – as is subclassing and other ways to code around the problem. But I think there's a usability gain here that's worth considering because it's a pretty common problem and it can be known at the time of the DAG run whether or not to mark a task as skipped.
   
   You don't have that logic with a branching operator sitting in front of your task. It's also sort of wasteful I think to let an executor handle what the scheduler can do just as well.
   
   And what do you call your branching operator ... "check-if-saturday-task123". It doesn't seem particularly elegant to me.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org