Airflow Task Dependency Order
Identify the mistake in an Airflow ETL dependency chain.
Codepython
# ETL pipeline: extract, then transform, then load
extract = PythonOperator(task_id="extract", python_callable=do_extract)
transform = PythonOperator(task_id="transform", python_callable=do_transform)
load = PythonOperator(task_id="load", python_callable=do_load)
load >> transform >> extract
What is wrong with the task dependency definition?