[Bug]: Open Execution is not working for the ETL Metadata Injection transform

[mattcasters]

Apache Hop version?

2.17.0

Java version?

openjdk 21.0.10 2026-01-20

Operating system

Linux

What happened?

The new possibility to look at the execution (results and active) of a sub-workflow or pipeline does't work for the ETL Metadata Injection transform.

Issue Priority

Priority: 3

Issue Component

Component: Hop Gui

[hansva]

ahhh, I forgot to test that one
.take-issue

[CarlosJuncher03]

Another problem I encountered is that, even with multiple threads running in the subpipeline, the screen to choose which threads to open is not displayed, as shown in the activity image at #5304. Has this been implemented yet?

[hansva]

I decided against the idea of showing a list of past executions; the main goal is to see what is happening during development, or drill down if something has failed during development. I added the row buffers to keep the data, so it makes tracking down issues simpler. If you want a full overview of past executions, we have the Execution Information perspective for that.

I sought a balance to not cannibalize on that feature and give the developer more insight. We could further harmonize both views in the future with incremental changes and improvements.

[CarlosJuncher03]

For example, I have 3 threads running simultaneously, each receiving a set of data parameters. Wouldn't it be possible to use the screen you added to the development activity, which shows the running threads and the parameters they receive, so I can access and view the flow? Because currently it only shows one, regardless of how many are running.

Note: The question is only to see what is currently running; what has already been executed or finished does not need to be displayed in the list.

[hansva]

I did not like yet another pop-up, and did not like the full design/developer experience. So I simplified it for now, as stated in the previous post, we can further build on this in the future.

[hansva]

MDI transform now also has the DrillDown enabled, small note when going to the execution you get the injected pipeline metadata. This means you can see all values that are actually being used inside the transforms.
Small downside, we open these pipelines in edit mode this means you could accidently overwrite your template if you make a change here.
An improvement I would like to do before 2.18 is have "Tab Types" you can't open a pipeline and the git info or the text version of that same pipeline at the same time because our tabmanager does not allow it. Maybe the executions should be opened in read-only mode as the executionviewer does.