Adalennis opened a new issue, #9173: URL: https://github.com/apache/hop/issues/9173
### Apache Hop version? SNAPSHOT-20261021 ### Java version? Java 21 ### Operating system macOS ### What happened? Found while documenting the result of the Join action (#8970, sixth batch, PR #9118). When several parallel branches lead to a Join, only the result files and result rows of one branch reach the action after the Join. The others are dropped, and which branch is kept is not deterministic. **Reproduce:** Start → A (Create file a.txt, Add filename to result) and Start → B (Create file b.txt, Add filename to result), both with a success hop to Join, then an action that lists the result files. Run it a few times with hop-run: the result files hold one file, a.txt in 3 runs out of 5 and b.txt in the other 2, never both. The log order of A and B doesn't predict which one is kept. The same happens with result rows: with A giving 1 row and B giving 2 rows (Copy rows to result), the action after the Join gets 2 rows, not 3. **Cause:** `ActionJoin.execute()` reads the results of the previous actions (`getFinishedActionResult`) only to decide true/false and to count errors, and returns the `Result` it was started with. That is the result of the branch that claimed the Join (`claimJoinsToFollow` in `Workflow.java`), so the result files and rows of the other branches are never added. **Expected:** the Join passes on the result files and result rows of all the branches it waited for, for example by adding the files and rows of each finished predecessor's result, like the errors already are. The current behaviour is documented on the Join page (PR #9118), so the docs need an update when this is fixed. ### Issue Priority Priority: 3 ### Issue Component Component: Workflows -- 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]
