In a PMML document transformations applied to the data are documented in a transformation dictionary as so called derived fields. Those derived fields have a name, a reference to the transformed field and a transformation to be applied. This node merges the derived fields of two PMML document so that transformations documented in both are in the transformation dictionary of the new PMML document. The node takes all content from the second document and adds the transformations of the first to its transformation dictionary. Some checks ensure that the first port is the PMML with transformations that come after the ones in the first port. If a field, identified by its name, is present in the first PMML's data dictionary, it must be either in the second PMML's data dictionary or transformation dictionary. If a field is present in the second PMML's data dictionary but not in the first, the documents are incompatible. Additionally neither PMML can have a model.
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.
To use this node in KNIME, install the extension KNIME Modular PMML Nodes from the below update site following our NodePit Product and Node Installation Guide:
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 mail@nodepit.com.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.