amoghrajesh opened a new pull request, #71863:
URL: https://github.com/apache/airflow/pull/71863
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
### What
There was a slight gap in our docs - core docs were not missing the content
for durable execution but they were missing the word being stated explicitly.
`resumable-tasks.rst` already covered all of this, but core called the concept
"Resumable Tasks" while 7 provider pages (Glue, Redshift Data, Databricks
run_now and submit_run, BigQuery, Snowflake, KPO) use "Durable execution" as a
section heading. In core docs, the phrase appeared exactly twice, both
mid-paragraph, both buried inside a subsection about clearing tasks. So a site
search for "durable execution" returned provider pages and nothing conceptual.
I propose we add a new "Durable execution" section in `resumable-tasks.rst`,
placed right after the failure-mode intro and before the three approaches,
carrying some layering: durable execution is the outcome, task state store is
the mechanism. It also names the provider ecosystem explicitly so someone
landing there understands why provider pages use that heading.
Added a ref target so provider docs can link straight to the definition
later, and a paragraph in `task-state-store.rst` binding it from the other
direction.
Another benefit of this is that the "three approaches" now reads as three
ways to achieve durable execution rather than three unrelated options, which is
the framing that's worth addressing.
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
