gitedmond commented on issue #40543:
URL: https://github.com/apache/airflow/issues/40543#issuecomment-5555016231
I tested the original scenario from this issue against current main
(9f978d30097b030bb68f24d88e9e1e3da11e0c99), and I could not reproduce the
reported behavior.
The regression test creates a serialized Dag with a three-item mapped
TaskGroup containing extract >> transform >> load, creates a real DagRun, and
verifies that all nine TaskInstance rows exist. It then calls the public
clearTaskInstances API using the same mapped-task marker sent by the UI.
I tested indexes 0, 1, and 2 in both directions:
• Clearing etl.extract[index] with downstream tasks included
returned and cleared only extract[index], transform[index], and load[index].
• Clearing etl.load[index] with upstream tasks included returned
and cleared only extract[index], transform[index], and load[index].
• Preview mode left all states unchanged.
• Actual clearing changed only the three TaskInstance rows
associated with the selected index.
All six parameterized cases passed against unchanged production code.
Since the original report used Airflow 2.7.0, the behavior appears to have
been corrected by subsequent mapped-task handling changes, although I have not
identified the exact fixing commit. This result does not imply that the
original report was user error.
Could a maintainer confirm whether this issue can be closed as already fixed
on current main? I can also provide the regression test if retaining explicit
coverage for this behavior would be useful.
--
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]
