[GitHub] [airflow] baolsen edited a comment on issue #7585: [AIRFLOW-6944] Allow AWS DataSync to "catch up" when Task is already …

[GitBox <gi...@apache.org>]

baolsen edited a comment on issue #7585: [AIRFLOW-6944] Allow AWS DataSync to "catch up" when Task is already …
URL: https://github.com/apache/airflow/pull/7585#issuecomment-599491925
 
 
   Hi @feluelle / @nuclearpinguin , would appreciate a review :)
   
   One thing I am aware of - currently there are 2 wait loops:
   1. Wait for task to be able to be started - implemented in the DataSync Operator. 
   2. Wait for task execution to be completed - implemented in the DataSync hook. (Task execution is what you get from AWS after triggering a Task to start)
   
   What is your recommendation to standardise these? 
   I have no preference... Just don't want a Sensor because the Operator is currently self-contained in terms of creating/deleting/running tasks. I'd like to move both wait loops either into the hook or the operator, not sure where is typically the best place.

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


With regards,
Apache Git Services