uranusjr opened a new issue, #50004:
URL: https://github.com/apache/airflow/issues/50004

   ### Apache Airflow version
   
   3.0.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When selecting “External conditions” in the graph view, outlets are attached 
incorrectly.
   
   With a dag of three tasks, each outputs to an asset:
   
   <img width="761" alt="Image" 
src="https://github.com/user-attachments/assets/bada69b1-e5ae-427b-93f3-c6a81900d8f3";
 />
   
   This is confusing since outlets `a1` and `a2` are on tasks `t1` and `t2`, 
but they are instead attached to `t3`.
   
   ### What you think should happen instead?
   
   The outlets should be attached to the correct task instead.
   
   Alternatively, since dependencies only matter at the _dag_ level, the 
outlets should be attached on the _dag_ instead. This would match the “All Dag 
Dependencies” view:
   
   <img width="696" alt="Image" 
src="https://github.com/user-attachments/assets/0f72810e-74f1-42b6-a9df-d876d9367cec";
 />
   
   ### How to reproduce
   
   ```python
   from airflow.providers.standard.operators.empty import EmptyOperator
   from airflow.sdk import DAG, Asset
   
   a1 = Asset("a1")
   a2 = Asset("a2")
   a3 = Asset("a3")
   
   with DAG("wrong-graph", is_paused_upon_creation=False):
       t1 = EmptyOperator(task_id="t1", outlets=[a1])
       t2 = EmptyOperator(task_id="t2", outlets=[a2])
       t3 = EmptyOperator(task_id="t3", outlets=[a3])
       t1 >> [t2, t3]
   ```
   
   ### Operating System
   
   Irrelevant
   
   ### Versions of Apache Airflow Providers
   
   Irrelevant
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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

Reply via email to