amoghrajesh opened a new pull request, #67376:
URL: https://github.com/apache/airflow/pull/67376
<!-- 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:
http://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.
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)
-->
closes #67324
### What
AIP-103 introduced task state and asset state but there are no example DAGs.
New users have no concrete reference for how to use these features correctly,
and the docs PR has no working code to link to.
I am adding two self-contained example DAGs to
`airflow-core/src/airflow/example_dags/`:
1. `example_task_state.py` — demonstrates the external job resumption
pattern. The task submits a job, stores the job ID in task state with
`NEVER_EXPIRE`, then deliberately fails on the first attempt. The retry reads
the job ID from task state and reattaches to the already-running job instead of
submitting a duplicate.
2. `example_asset_state.py` — demonstrates incremental watermarking with a
producer + consumer pair. The producer reads the last watermark from asset
state, fetches only new records, then advances the watermark. The consumer is
triggered by the asset event and reads asset state to inspect what was loaded.
Both DAGs are self-contained with no external dependencies and work out of
the box.
### Example run
Task state dag
<img width="2551" height="964" alt="image"
src="https://github.com/user-attachments/assets/f8f7433a-cc57-4e7d-8289-56a5e05e1a94";
/>
<img width="2551" height="964" alt="image"
src="https://github.com/user-attachments/assets/19ab3f34-3c64-480c-9eb1-f7be2ff1359e";
/>
Asset State dag
<img width="2551" height="964" alt="image"
src="https://github.com/user-attachments/assets/be8c18f6-78d3-4136-8593-f4b6c6653609";
/>
<img width="2551" height="964" alt="image"
src="https://github.com/user-attachments/assets/00b97ce1-1dfa-4cc9-b45a-d9c20dac0b9c";
/>
---
* 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]
