[Bug]: Pipeline run configuration - Log rows feedback not working

[dave-csc]

Apache Hop version?

2.11.0

Java version?

17.0.2

Operating system

Linux

What happened?

Create a pipeline run configuration with the options Log rows feedback and Make this pipeline transactional enabled, and use it to launch a (sub-)pipeline.

I expected to read a line in the worklow/pipeline log every now and then, when (50.000) rows have been processed: instead, the output has no difference compared to a log without rows feedback enabled

Issue Priority

Priority: 3

Issue Component

Component: Pipelines

[sramazzina]

Hi @dave-csc I firstly want to say that the setting related to Log rows feedback is totally unrelated from having set Make this pipeline transactional flag enabled. That said, I made some simple tries using a Data grid and a Dummy connected together and I made this that way because Data Grid gives the kind of feedback you are looking for if the feedback flag is enabled in run configuration. Of course I checked the Log rows feedback in pipeline run configuration and set the Feedback size in rows to 2. The Data Grid produced 10 lines and I correctly had 5 lines of feedback

Can you please elaborate a bit more on your case or post a reproduction case? I personally not understood what you meant by saying "use it to launch a (sub-)pipeline."

Thank you very much for you clarifications

[dave-csc]

Hi @sramazzina,

what I tried to do is creating a new Pipeline run configuration with the Log rows feedback options enabled. You can then specify it as a "Run configuration" in a Pipeline action or in a Pipeline Executor transform: this way you should activate the log feedback only for what's inside the attached pipeline (leaving the standard log for the rest of the workflow/super-pipeline).

However, I tried to reproduce again the issue in Hop 2.11.0 and 2.12.0... and I haven't been able to: I don't know what has changed in the meantime, sorry :/

[hansva]

So this can be closed?

[dave-csc]

Close if you need to clean up the issues board... maybe I'll repost if I find again how to reproduce the bug, if there actually is.

Thanks for your support :)