NoOp (Generic Port) Won't connect to

[mwiegand]

Hi @qqilihq,

there is not NodePit label available it seems and I don’t know the handle from Daniel, hence pinging you.

The NoOp Node with the generic ports seems to be unable to connect when pressing CTRL + L. Though, this might be a Knime issue as Knime established other connections instead.

It might very well be related to that issue I just raised too:

Auto connect report port breaks other port connections

Hi, when I have a component or report node selected as the first one and press CTRL + L to establish all links, the sub-sequent data ports do get reconnected unintentionally breaking the workflow structure. Best Mike

Best
Mike

[qqilihq]

Hi Mike,

here’s Daniel’s handle @danielesser

I tried this locally in KNIME 5.3 and it seems to work fine - with plain or wrapped/meta nodes.

I could imagine that the “generic” port makes the “pathfinding” for KNIME more difficult.

Generally I would always recommend to use the NoOp (Configurable) and do an explicit typing of the ports (i.e. instead of “Generic Port” use the proper subtype such as e.g. “WebDriver Factory”). This prevents you from accidentally connecting incompatible ports (it requires a bit more configuration though and doesn’t allow to drop the node on an existing connection, that’s why we provide the untyped, generic version as well).

-Philipp