-
Notifications
You must be signed in to change notification settings - Fork 16.4k
update xcom docs #46284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update xcom docs #46284
Conversation
|
When pushing multiple XCom values, we can still pull them using the 'return_value' key if we aren't explicitly pushing using a new key. So, we aren't exactly renaming anything here. Rather, we can now also pull using the keys within the returned XCom dictionary. |
RNHTTR
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be helpful to add a code snippet here demonstrating what you mean. Just by reading this, I'd have no idea how to actually implement this.
It would also probably be helpful to add additional context as to why someone would want to push multiple xcoms
…docs/fix_xcom_multiple
* update xcom docs * add example * add example * add multiple_outputs=True * use taskflow (cherry picked from commit 1648d7e) Co-authored-by: Kalyan R <kalyan.ben10@live.com>
* update xcom docs * add example * add example * add multiple_outputs=True * use taskflow (cherry picked from commit 1648d7e) Co-authored-by: Kalyan R <kalyan.ben10@live.com>
* update xcom docs * add example * add example * add multiple_outputs=True * use taskflow
* update xcom docs * add example * add example * add multiple_outputs=True * use taskflow
* update xcom docs * add example * add example * add multiple_outputs=True * use taskflow
minor rewrite of the sentence regarding pushing of multiple XComs