[GitHub] [airflow] ricardogaspar2 edited a comment on issue #16618: Access specific values within an `XCom` value using Taskflow API

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

ricardogaspar2 edited a comment on issue #16618:
URL: https://github.com/apache/airflow/issues/16618#issuecomment-892728928


   > > It would also be great if there was a way of NOT creating the dependencies between tasks automatically.
   > > For cluster or job IDs (EMR, Databricks, etc) is very common, and having these dependencies created automatically doesn't make much sense.
   > 
   > Without a dependency then you might try to get a value out of XCom that hasn't been written yet!
   
   Makes sense.  I retire my comment then.
   I think I got used to see how DAGs are now rendered with this new XComs/TaskFlow API (using `.output`) . Before Airflow wasn't creating edges between the tasks that were using the values.
   Not part of this topic, but it would be cool to have a visual representation of the variable that is being passed, much like Dagster does in their UI. 


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