Table Manipulator

Options

Use existing RowID

Check this box if the RowIDs from the input tables should be used for the output tables.If unchecked, a new RowID is generated. The generated RowID follows the schema "Row0", "Row1" and so on.

Prepend table index to RowID

Only enabled if the existing RowIDs are used. If checked, a prefix is prepended to the RowIDs that indicates which table the row came from. The format of the prefix is "Table_0_", "Table_1_", and so on.

Take columns from

Only relevant when several input tables are available. Specifies which set of columns is considered for the output table.
Note:
This setting has special implications if you are changing the input table without reconfiguring the node. If Intersection is selected, any column that moves into the intersection during execution will be considered to be new, even if it was previously part of the union of columns.

• Union: Any column that is part of any input table is considered. If an input table is missing a column, it is filled up with missing values.
• Intersection: Only columns that appear in all input tables are considered for the output table.

Enforce types

Controls how columns whose type changes are dealt with. If selected, the mapping to the KNIME type you configured is attempted. The node will fail if that is not possible. If unselected, the KNIME type corresponding to the new type is used.

Transformations

This option allows modifying the structure of the output table. It supports reordering, filtering and renaming columns. It is also possible to change the type of the columns. Whether and where to add unknown columns during execution is specified via the special entry Any unknown column.
Note:
The transformation matching during execution is based on name. That means if there was a column [A, Integer] during configuration in the dialog and this column becomes [A, String] during execution, then the stored transformation is applied to it. For filtering, ordering and renaming, this is straight forward. For type mapping the following is done: If there is an alternative converter to the specified KNIME type, then this converter is used, otherwise we default to the default KNIME type for the new type. In our example we might have specified that [A, Integer] should be mapped to Long. For the changed column [A, String] there is no converter to Long, so we default back to String and A becomes a String column in the output table.

Views

This node has no views

Workflows

• _Atelier 01KNIME Hub
• 0. Lubes_Sales_Pred-ModelNodePit Space
• 0. Lubes_Sales_Pred-ModelNodePit Space
• 00 Main MenuKNIME Hub
• 00 Main MenuKNIME Hub
• Show all 1309 workflows

Links

• Unsupported Column Type - String V. Databy HansS on 2021-06-22

  forum.knime.com/p/127223
• String Manipulation (Multi Column) errorby HansS on 2024-12-04

  forum.knime.com/p/275739
• Componente para mapeo de camposby jmgor on 2022-01-02

  forum.knime.com/p/143267

Developers