uranusjr commented on PR #25604: URL: https://github.com/apache/airflow/pull/25604#issuecomment-1216149195
> WDYT about allowing `operator.output(key=...)`? Doesn’t this conflict with using `op.output` as a property though? It’s possible but quite difficult to implement `output` as both an XComArg and callable. Maybe `op.get_xcom(key=...)` (or something like that) would be easier. The general direction feels like a good idea to me though. I also plan to add some mechanism in #25661 to avoid exposing the bracket syntax: 1. Keep `XComArg(...)` and the return value of `@task` work as-is (so any existing code depending on the bracket syntax continues to work) 2. Introduce a new XComArg class that _does not_ provide the bracket syntax, and use that in `output` and `get_xcom()` etc. Does this sound like a good plan? -- 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]
