You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/04/25 19:09:55 UTC

[GitHub] [airflow] casassg edited a comment on issue #8052: [AIP-31] Create XComArg model

casassg edited a comment on issue #8052:
URL: https://github.com/apache/airflow/issues/8052#issuecomment-619426981


   > it can be represented as Jinja template
   
   I do not agree on this. Why do we need to stick to Jinja templates? Seems we are trying to fit the new solution to the existing workaround, when we should think of this as a more generic solution. I dont see why we need a `ArgBase` class. Could you illustrate with an example?
   
   > Should "normal" operators be also XComArgs?
   
   No let's use https://github.com/apache/airflow/issues/8055 instead:
   
   ```python
   with DAG("example"):
       op1 = CreateClusterOperator("op", ...)
       op2 = RunJobOperator("op2", cluster_name=op1.output)
   
   # Or with custom XCom key
   
   with DAG("example"):
       op1 = CreateClusterOperator("op", ...)
       op2 = RunJobOperator("op2", cluster_name=op1.output["cluster_id"])
   ```


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