det101 opened a new issue, #17748:
URL: https://github.com/apache/dolphinscheduler/issues/17748

   ### Search before asking
   
   - [x] I had searched in the 
[DSIP](https://github.com/apache/dolphinscheduler/issues/14102) and found no 
similar DSIP.
   
   
   ### Motivation
   
   Current dependency mode configuration in frontend cannot connect the 
backfill dependency enabling action with downstream workflows. We want to 
improve the rerun workflow so that it correctly triggers the downstream 
workflows after backfill, supporting two dependency modes.
   
   ### Design Detail
   
   - Add implementation for frontend dependency mode switching
   - Support both Basic Mode (trigger only direct downstream workflows) and 
All-Level Mode (recursively trigger all dependency levels).
   - Implement traversal logic (BFS/DFS) for recursive triggering, with 
protection against cycles and duplicate triggering.
   - Update UI to reflect mode and ensure users can select preferred behavior.
   - Add tests for both triggering modes.
   
   ### Compatibility, Deprecation, and Migration Plan
   
   This improvement does not introduce breaking changes to existing workflows, 
but recursive triggering should be idempotent to prevent duplicate executions. 
Cycle detection will be implemented to protect against circular dependencies.
   
   ### Test Plan
   
   - Verify direct and recursive triggering work correctly for various workflow 
dependency graphs.
   - Add automated tests on workflow DAGs for both dependency modes.
   - Manual test for large-scale workflow with complex dependencies to ensure 
reliability and performance.
   - Test cycle detection and duplicate triggering prevention.
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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