[Task]: Document how Pipelines using Stream Lookup can run into deadlock

[gmitter-ef]

Apache Hop version?

2.6, 2.7, 2.8

Java version?

OpenJDK 11

Operating system

Windows

What happened?

It turned out that the problem of pipelines running into a deadlock, which is described in https://pentaho-public.atlassian.net/wiki/spaces/EAI/pages/386807182/Transformation+Deadlocks , also affects Apache Hop 2.6-2.8.

I tested the “Blocking Example - Stream Lookup" and “Blocking Example - Stream Lookup - Workaround 2” in the examples zip attached under the above link, by simply importing it via the very handy import tool to Apache Hop.

I would suggest to either fix it (if possible) or add documentation for this behaviour (could not find any).

BTW: I also posted this to the [email protected] mailing list.

Issue Priority

Priority: 3

Issue Component

Component: Pipelines

[hansva]

It's how the engine works, you are right it should be documented somewhere, and it isn't. Going to change this to a feature request for documentation.