kacpermuda opened a new pull request, #74752:
URL: https://github.com/apache/airflow/pull/74752

    <!-- 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
   -->
   
   Task loops are new, and OpenLineage events need to describe them from day 
one. Inside a loop the iteration of a
   task was invisible: `taskInstance.map_index` is only set for mapped tasks 
and the runId is the attempt UUID, so
   iterations of one task looked identical, and nothing verified that runIds 
stay consistent across START and
   COMPLETE, retries, map indexes and iterations.
   
   - `taskInstance` facet gets `loop_index` and `loop_max_iterations`. Loop 
groups expose `max_iterations`,
     `has_until`, `gate_task_id` and `terminal_task_id` in `task_group` and in 
`AirflowJobFacet.taskGroups`.
   - The manual state change path passes its computed position to the facet, 
and `TaskInstanceInfo` no longer
     raises for a stored task instance it can't place.
   - `OpenLineageTestOperator` checks runId integrity by default: one job and 
attempt per runId, a complete
     START and COMPLETE/FAIL lifecycle, and one runId per attempt.
   - New example Dags for retries, a rescheduled sensor, and loops with a plain 
task, a retried loop task and a
     retried mapped loop task (Airflow 3.4+).
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (Claude Code)
   
   Generated-by: Claude Code (Sonnet 5.5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   
   * 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]

Reply via email to