Merges flow variables into one stream. This node aggregates variables defined in different input connections into one variable connection. It does not modify variables but only merges them. This node can also be used as a common barrier point to control the execution order of nodes, i.e. nodes connected to the output port will not start executing until all upstream nodes have been executed. Note, if there are the same variables defined in different inputs, a special conflict handling is applied: The top most flow variable input port will take priority and override values on conflicting variable names. Otherwise, the priority order goes from the bottom to the top port. For example, port 3 will take priority over port 2. However, the first port will always take priority over all other ports.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.Try NodePit Runner!
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to email@example.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.