Description:
I was playing around with the Web UI of the joiner node and noticed that the current design is somewhat flawed when working with flow variables. Before, the selection of the columns was controlled by a stringlist that could be applied to both the leftColumnSelectionConfig/included_names
and rightColumnSelectionConfig/included_names
When opening the configure flow variables through Web UI, the old UI opens and I apply a previously created stringlist accordingly.
Contrary to the current UI, the node config does not give any indication that the left hand column selection is now controlled by a variable.
It turns out, that the flow variable is not even applied at all. When changing the input column to something I know will fail but should be overridden by the flow variable after all, actually fails which should not happen if the flow variable was actually applied.
Column3
here should contain some values, as per the joiner with the same settings but without flow variable applied.
Going back to the main config dialog, I noticed that each column is now individually controllable. But these can only be controlled by string variables. This is pretty conflicting with what the flow variables dialog gives.
This raises the question, which direction is KNIME going? What will be the final direction? Control each column individually or still have the option of a stringlist?
Actual results:
Stringlist flow variable not working. Cannot be applied in main dialog. Flow variables can only be applied to individual columns. All workflows and components containing a joiner that is controlled by this will be broken.
Expected results:
Stringlist flow variable applied correctly. Alignment between config dialog and configure flow variables dialog.
Attachments:
Webui_Joiner_Labs.knwf (99.2 KB)
Note: WF is saved in the âbrokenâ config. Incorrect column selection that should have been overriden by the flow variable.
OS:
Windows 10 Pro 64-bit (10.0, Build 19045)