amoghrajesh opened a new pull request, #76968:
URL: https://github.com/apache/airflow/pull/76968
<!-- 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)
-->
related: #76806, #72100
Several provider docs still say a clear keeps the stored job id, so a task
whose job already succeeded returns the old result. That stopped being true
when a task is cleared in Airflow 3.4 (#72100), and stops being true when its
whole Dag run is cleared in 3.5 (#76806). A user who follows these pages
expects a cleared run to reuse a finished job, and pays for a second one
instead.
Each affected page now says that clearing a task deletes the stored state by
default (3.4+), and so does clearing its whole Dag run (3.5+), and that you can
choose to keep it. The operator pages add a table of what the next attempt does
for each job state, with a default clear and with task state kept:
| Job state | Default clear | Clear that keeps task state |
|---|---|---|
| Still running | Submits a new job. The first one keeps running. |
Reconnects to the running job. |
| Succeeded | Submits a new job. | Returns right away without starting
another one. |
| Failed | Submits a new job. | Submits a new job. |
Pages updated:
- Amazon: Glue, Redshift Data
- Databricks: `run_now`, `submit_run`
- Snowflake
- Apache Spark
- Common AI: durable execution "Clearing a task" section (the
`AgentOperator` docstring links to it), Strands, OpenAI Agents
- Hugging Face: datasets
Docs only. No code or behaviour change. Should merge after #76806.
---
* 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]
