-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Expanding .output operator property information in TaskFlow tutorial doc
#19214
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
Expanding .output operator property information in TaskFlow tutorial doc
#19214
Conversation
| based tasks which need to be run first before a python-based task is run. | ||
| Adding dependencies to decorated tasks from traditional tasks | ||
| ------------------------------------------------------------- | ||
| The above tutorial shows how to create dependencies between TaskFlow functions. However, it is |
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.
Using the description "TaskFlow function" to be consistent with the description in the Concepts: TaskFlow doc. Let me know if there is a more succinct description we could use.
|
The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest main or amend the last commit of the PR, and push it with --force-with-lease. |
dstandish
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.
looks good but had a few suggestions
Closes: #9415, #12726
Adding more color and information about the
.outputproperty of operators in the TaskFlow tutorial doc. There are also small changes to keep spelling and descriptions consistent.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.