-
Notifications
You must be signed in to change notification settings - Fork 16.4k
docs(task-sdk): reorganize landing page into six core sections #52196
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
Conversation
092c4dc to
eb70f52
Compare
88ef0d3 to
fd59275
Compare
f58f14e to
0bed9ee
Compare
cmarteepants
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.
Great job! I think moving the architecture changes to Upgrade to Airflow 3 was the right call. I also like the addition of the Supervisor & Task Runner to the Task SDK docs. Beefs it up a bit, and feels like it reinforces the split.
amoghrajesh
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.
Good work on this @sunank200! I have some nits, but overall really like the way this one is being put together.
Shoutout to @TJaniF for the AF3 book as well, which provides a bulk of the content and images for this PR!
…Interface, DAG Authoring, Examples, Concepts, API Reference)
823a908 to
4657f55
Compare
Update task-sdk/docs/concepts.rst
4657f55 to
f755c43
Compare
…tions (apache#52196) docs(task-sdk): reorganize landing page into six core sections (cherry picked from commit 261d33d) Co-authored-by: Ankit Chaurasia <8670962+sunank200@users.noreply.github.com>
This PR reorganises and updates the content for task-sdk:
Landing page (task-sdk/docs/index.rst):
1. Introduction & Getting Started
2. Public Interface
3. DAG Authoring Enhancements
4. Example DAG References
5. Concepts
7. API References
Add concepts:
– Details task lifecycle: scheduling → execution → heartbeats → XCom communication → retries/teardown
– Supervisor & Task Runner
Move following to airflow 3
– Compares Airflow 2.x vs 3.x architectures
closes: #49627
related: #51590
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.