[Bug]: Execution Results Not Saved Properly
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### Apache Hop version?
2.12
### Java version?
17
### Operating system
Windows
### What happened?
Hi,
The following behavior was observed in the pipeline executor step:
1. If you set the hop to a step like the Dummy step, you have the option to pass the execution results there. If you select this option, the hop is correctly marked. However, once you save the pipeline, this setting is lost and the hop no longer passes the execution results. After reopening the Pipeline Executor and manually setting the step that should receive the execution results, everything works as expected.
2. When opening the Transformation Executor step and changing, for example, the step that should receive the execution results, the parameter values are automatically duplicated.
### Issue Priority
Priority: 2
### Issue Component
Component: Pipelines
Contributor guide
Research direction
Start by reproducing the behavior in the Pipeline Executor and Transformation Executor steps: save and reopen a pipeline, then change the step receiving execution results. Verify whether the receiver setting is preserved and whether parameter values are duplicated; done means both behaviors no longer occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100