[Bug]: Pipeline action - record set forwarding issue /2
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### Apache Hop version?
2.10.0
### Java version?
17.0.2
### Operating system
Linux
### What happened?
(**UPDATE:** probably the issue is related to #4559, I got this in a scenario where the second pipeline doesn't save any valid row in `Copy rows to result`)
Create three pipelines as follows:
1. End the first pipeline with a `Copy rows to result` transform
2. In the second pipeline, start with a `Get rows from result` transform, add some other transforms to manipulate the metadata, and then end with a `Copy rows to result` transform
3. Start the third pipeline with a `Get rows from result` transform
Add those three pipelines in a workflow so that they're executed in the order described above.
The third transform will get the rows from the result of the first pipeline, instead of those of the second one.
No workarounds currently found
### Issue Priority
Priority: 2
### Issue Component
Component: Actions, Component: Hop Gui
Contributor guide
Research direction
Reproduce the three-pipeline workflow described in the issue using Copy rows to result and Get rows from result in Hop 2.10.0. Compare the rows received by the third pipeline after the second pipeline manipulates its metadata; done means the third pipeline receives the second pipeline's result rather than the first pipeline's rows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100