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.
Views
- This node has no views
Workflows
01_AnalyticsKNIME Hub- 01_AnalyticsKNIME Hub
- 01_Example_for_Using_PMML_for_Transformation_and_PredictionKNIME Hub
- 01_Model_Selection_SampledKNIME Hub
- 02_Scaling_Analytics_w_BigDataKNIME Hub
- 02_Scaling_Analytics_w_BigDataKNIME Hub
- 03_ZIP_Local_vs_remoteHTTPKNIME Hub
- 14_Reading local and remote compressed CSV filesKNIME Hub
AutoML - Preview (PMML)KNIME Hub- column_filter_(PMML)KNIME Forum
- column_filter(PMML)_excelKNIME Forum
- Guided_Analytics_with_Shared_ComponentsKNIME Hub
- k_005_pmml_modularKNIME Hub
Links
- No links available
Developers
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.