vitorsantos-commits opened a new issue, #7734: URL: https://github.com/apache/hop/issues/7734
### Apache Hop version? hop-client-2.19.0-20260724.112758-1 ### Java version? jdk-21.0.10.7 ### Operating system Windows ### What happened? While a pipeline is running in Apache Hop using Hop GUI and the Local Pipeline Engine, it is possible to open a Filter Rows transform, change its condition, and click OK without stopping the execution. After the condition is changed, rows that have not yet been evaluated may use the new rule. Consequently, within the same pipeline execution, earlier rows can be routed according to the original condition, while later rows are routed according to the modified condition. Rows already processed or queued are not rerouted. Steps to reproduce: 1. Create a pipeline with a continuous or sufficiently slow input stream. 2. Add a Filter Rows transform with separate True and False destinations. 3. Start the pipeline using the Local Pipeline Engine. 4. While it is still running, open the Filter Rows transform. 5. Change the filter condition and click OK. 6. Observe that subsequent rows may begin following a different True or False route without restarting the pipeline. Expected behavior: The running execution should continue using the configuration captured when it started. Any modification made in Hop GUI should apply only to the next execution. Actual behavior: The active execution may begin using the modified condition, causing different rows from the same run to be evaluated using different rules. Is this intentional runtime reconfiguration functionality, or is it a bug caused by the active execution sharing mutable Filter Rows metadata with the editor? ### Issue Priority Priority: 3 ### Issue Component Component: Hop Gui -- 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]
