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 2020/06/15 06:53:09 UTC

[GitHub] [airflow] afsalabdup opened a new issue #9298: To put a task ON HOLD

afsalabdup opened a new issue #9298:
URL: https://github.com/apache/airflow/issues/9298


   Description: To put a future instance task ON HOLD.
   
   There is a requirement where you want to put a task named 'task3' on hold, so that once the DAG is triggered, all upstream tasks would start running but when it reaches 'task3', task3 should go "ON HOLD" state, so that downstream of task3 would not start running. If we can do that through CLI by providing future execution id then it would be great.
   
   Currently I can mark a task to success through CLI by providing future execution id, but the issue is when I mark task3 to success, downstream tasks will start running immediately because downstream will check if its upstream task3 is success or not. I want to put task3 to ON HOLD so that it's downstream won't trigger by itself.
   
   


----------------------------------------------------------------
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.

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

[GitHub] [airflow] eladkal commented on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
eladkal commented on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-986569295


   To my understanding a possible solution is to change the `On`/`Off` from DAG level to Task level.
   So a DAG would be considered ON if at least one of it’s task is ON. Even assuming this is feasible it brings many challenges for example how would dag timeout behave if some tasks are on hold?


-- 
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

[GitHub] [airflow] malthe edited a comment on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
malthe edited a comment on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-986574890


   I think that's probably the best you can do yes. After each DAG run, use the `on_failure_callback` and `on_success_callback` methods to disable the DAG model (i.e., put it into "off" state).


-- 
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

[GitHub] [airflow] boring-cyborg[bot] commented on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-643939494


   Thanks for opening your first issue here! Be sure to follow the issue template!
   


----------------------------------------------------------------
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.

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

[GitHub] [airflow] malthe commented on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
malthe commented on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-986562766


   And perhaps add optional operator option `email_on_hold` to be able to send an e-mail when a task is put on-hold.


-- 
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

[GitHub] [airflow] shamsuvs commented on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
shamsuvs commented on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-822369069


   Is this feature available now?
   


-- 
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.

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

[GitHub] [airflow] malthe edited a comment on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
malthe edited a comment on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-986574890


   I think that's probably the best you can do yes. After each DAG run, use the `on_failure_callback` and `on_success_callback` methods to disable the DAG model (i.e., put it into "off" state).
   
   The challenge with task-level "ON HOLD" is for example, how long do you keep the DAG run active before giving up.


-- 
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

[GitHub] [airflow] malthe commented on issue #9298: To put a task ON HOLD

Posted by GitBox <gi...@apache.org>.
malthe commented on issue #9298:
URL: https://github.com/apache/airflow/issues/9298#issuecomment-986574890


   I think that's probably the best you can do yes. After each DAG run, use the `on_failure_callback` and `on_success_callback` methods to disable the DAG model (i.e., put it into "off" state).


-- 
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