[Bug]: Java Filter / Filter Rows routing data to incorrect branch when Simple Mapping Transform used
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 216
Description
### Apache Hop version?
2.14.0
### Java version?
17
### Operating system
Windows
### What happened?
I have a JAVA Filter which condition [status.equals("need-db-call")] it routes the data to correct success branch when the condition is met successfully.
In case of false scenario i.e when filter condition is false, it routes the data to both success and false branch triggering simple pipeline transform which is not expected.
Note: Tried using Filter Rows transform, still see the same issue.
Simple Mapping Transform has a Table Input Transform to read certain values from DB and present them as Mapping Output, to be later used to set variables in main pipeline
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms
Contributor guide
Research direction
Start by reproducing the routing behavior with the Java Filter and Filter Rows transforms, including the Simple Mapping Transform and its Table Input and Mapping Output. Compare the success and false branches when the condition is false; done means only the expected branch receives the row and the behavior is covered by a regression test.
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
- Needs clarification
- Newbie friendliness
- 35/100