uranusjr edited a comment on issue #17752: URL: https://github.com/apache/airflow/issues/17752#issuecomment-904364486
Allowing a DAG to control when the next run should happen feels like the wrong abstraction to me. A BranchPythonOperator seems like a good way to go. With AIP-39 implemented, you may also use a custom timetable to query previous DAG run results to determine when the next DAG run should happen. The difference is to not put controlling logic on the *previous* run (which is difficult), but make the *next* run—either when the run happens as in BranchPythonOperator, or when the scheduler decides when the run should happen as in AIP-39 timetable—decide what to do. -- 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]
