Merge Mapper (Basic)
-
For details on Document Mapper and Variable Mapper, refer to Document Mapper/Variable Mapper (Basic).
-
For details on properties, specification limits, and notes, refer to Merge Mapper (Details).
Merge Mapper
Merge Mapper is a converter to combine data read from multiple input source components in accordance with the mapping definition and write it to the subsequent components.
Merge Mapper can be used in Designer. Follow the instructions below to use it.
-
Place the component icon from the tool palette
Drag the icon on the canvas from “Conversion” - “Basic” - “Merge” in the tool palette.
-
Place a merge logic in the mapping canvas.
-
Map the loop point of the input source to the first handler of the merge logic.
= Hint =The specification method for loop point varies depending on the data model of input source schema.
= Remarks =For more details, refer to Loop point.
-
Select the element for the key for merging the input source and map it to the second handler of the merge logic.
-
Use the same method to map all the input sources to be merged.
-
Map from the merge logic to the loop point of the output target.
-
Map the elements to be output from input source to output target.
For an input/output schema of Document Mapper and an output schema of Merge Mapper, when data flow is removed, the schema that has been set will be retained. This schema is called "temporary schema".
The component icon name of temporary schema is displayed as "Temporary schema" to distinguish from normal schemas.
When Mapper is connected to another component through a data flow, the temporary schema reverts to a normal schema.
With the temporary schema, mapping links remain even if its corresponding data flow is removed, and you can edit the schema even if Mapper is not connected to a component.
For a Mapper schema without a temporary schema (input schema of Variable Mapper and Merge Mapper), when the data flow is removed, the schema will be cleared and the mapping links will be removed.
To edit a schema before setting a data flow, you can set a temporary schema manually.
Select [Set temporary schema] from the right-click menu.
Output processing data log function
The output processing data log function is a function to output data information processed with Mapper logics to the log.
Because this log is output in the order of internal processes of Mapper, you can see how the data conversion/processing is done in detail.
With this function, it is possible to create a conversion/processing while checking the operation of actual data, and therefore you can develop a mapping efficiently.
Targets for outputting log and the log levels are as follows:
|
Target |
Log level |
|---|---|
|
Input/output data of Mapper logic |
DEBUG |
|
Data output into output schema |
DEBUG |
The details of output contents are as follows:
Input/output data of Mapper logic
Input/output data of Mapper logic is output in DEBUG log level.
The format varies depending on the number of input handlers.
Mapper logic with no input handler
Format
[<Mapper logic name>] OUT=[<output data>]
Output example
[Single-line String Constant] OUT=[outputData]
Mapper logic with one input handler
Format
[<Mapper logic name>] IN=[<input data>] | OUT=[<output data>]
Output example
[Left String] IN=[SampleData] | OUT=[Sample]
Mapper logic with multiple input handlers
Format
[<Mapper logic name>] IN=[<input data 1>][<input data 2>]... | OUT=[<output data>]
Output example
[Concatenate] IN=[Sample][Data] | OUT=[SampleData]
Data output into output schema
Data output into output schema is output in DEBUG log level.
The format varies depending on whether the data model of output data is the table model type or the XML type.
Table model type
Format
column[<row number>,<column number>] IN=[<input data>]
Output example
column[2,1] IN=[SampleData]
The row number and column number start from 1.
XML type
Format
<Path in output schema> IN=[<input data>]
The attribute in output schema is output as "@<attribute name>".
The prefix of name space in output schema is output as "<prefix>:" before the element name and the attribute name.
Output example
/root/row/col IN=[SampleData]
/root/row/col/@attr IN=[SampleData]
/root/row/pre:col IN=[SampleData]
Notes
-
The If logic uses Mapper logics corresponding to Criterion for determination.
The input data for the if logic will be output as logs of Mapper logics used for Criterion.
Output example
[Single-line String Constant] OUT=[Sample]
[Single-line String Constant] OUT=[Data]
[Equal] IN=[Sample][Data] | OUT=[false]
[Single-line String Constant] OUT=[<output of when false>]
[If] OUT=[<output of when false>]
Specification limits
-
When the input handler type of Mapper logic is "Node set", the input data log will not be output.
-
When null is input in Mapper logic which has one or more input handlers, the input data might not be output.
-
Input/output data logs for the following Mapper logics are not output:
-
Merge
-
Or-Append Merge
-
Or-Integrate Merge
-
And-Append Merge
-
And-Integrate Merge
-
Left-Right-Join Merge
-
-
Others
-
Output by XPath Expression
-
-
-
Input data logs for the following Mapper logics are not output:
-
Branch
-
If
-
Switch
-
-
Number
-
To Number
-
Square Root Value
-
-
String
-
To String
-
-