Merge Mapper

Operation name

Merge

Function overview

Unites two or more input data.

Refer to "Basic Functions (Merge Mapper)" for details.

Properties(Property Inspector)

Basic settings

Item name	Required / Optional	Use of Variables	Description	Remarks
Name	Required	Not available	Specify the name to be used in the script canvas.
Input data	Required	Not available	Select the component that outputs the result data from [Set input data] screen.	In Merge Mapper, two or more input data can be specified. When [Input data] input field is double-clicked, [right button] is displayed. When right button is clicked, [Set input data.] screen is displayed.

Setting of input data

Item name	Required / Optional	Use of Variables	Description	Remarks
Input data	Required	Not available	Select the component that outputs the result data. Each row can be operated with the following buttons. [Add]: Add the row. [Up]: Raise one order of the row that has been selected above. (The order of the input schema on the Mapper editor changes places. ) [Down]: Lower one order of the row that has been selected as it is low.(The order of the input schema on the Mapper editor changes places. ) [Delete]: Delete the row.

Comment

Item name	Required / Optional	Use of Variables	Description	Remarks
Comment	Optional	Not available	You can write a short description of this mapper.

Input Output Schema

Mapper displays schemas used for both input source and target output. For a one-to-one correspondence between source and target fields, the map can be created just by simply connecting fields of the input and the output schema.
For some components it is created automatically, but for others it needs to be created manually.

See "Schema of adapter" for further details.

Mass data processing

When the component that did mass data processing is an input origin, Merge Mapper does mass data processing.

However, attention is necessary for use because of the performances more deteriorated than the usual memory processing.

When mass data is treated to secure the memory input data and the result data at the memory processing, it is necessary to secure the heap size of DataSpiderServer.

See Lax file for how DataSpiderServer heap size can be changed.

Note the usage rate of the memory so that the consumption rate of the memory when it executes it according to the number of data sources of the input origin may increase in Merge Mapper when you execute merging two or more data sources.

PSP Usage

PSP is not supported.

Available component variables

Component variable name	Description	Remarks
message_category	Stroes the category to which corresponding message code belongs to, when an error occurs.	The value defaults to null.
message_code	Stores its corresponding message code of occured error.	The value defaults to null.
message_level	Stores the severity of the corresponding message code of the occured error.	The value defaults to null.
error_type	Returns the error type when error occurred.	The value defaults to null. Error is represented in the format depicted below. Example:java.io.FileNotFoundException The message may vary depending on DataSpider Servista version.
error_message	Return the error message when error occurred.	The value defaults to null. The message may vary depending on DataSpider Servista version.
error_trace	Return trace information when error occurred.	The value defaults to null. The message may vary depending on DataSpider Servista version or the client application used.

Specification Limits

The conversion logic is done and the mapping cannot be done directly to the output schema.

The script variable and the component variable cannot be merged.

When the logic not used on the mapping canvas is left, it is not possible to process it normally.
Delete the logic not used from the mapping canvas. It makes an error of the compilation when executing it though it passes.

Table model type data such as CSV, variable length, or a database data which includes xml unsupported characters, therefore not convertible to XML documents, cannot be processed by mappers.

Merge Mapper does not support transactions. Therefore, the contents of database and file changed in the process before Merge Mapper are not able to be refered.

Modifications made to the schemas of the source and target components connected to a mapper are notified to reflect the changes to the mapper's input and output schema only if the data flow lines are drawn from/to the components.

For example, if the input source to a mapper is a Loop by Number of Data Operation, changing the data source to which the Loop by Number of Data Operation is performed on will not affect the Mapper's input schema.
Therefore schema needs to be manually loaded.

While having the Mapper which has several output destinations open, even if you load input schema to one of the output Mappers, the condition will not be copied to the other output Mappers. To apply the same condition to all the output Mappers, reopen the project, load input schema again while the source Mapper closed.

If you set a script variable in XML type to the output destination of Merge Mapper, and then change the script variable name by Project Explorer, it will not affect to the output schema. To reflect the changes, reopen the project.

If you set a component having an editable schema to the output destination of the Merge Mapper, and then change the schema of the merge Mapper by the variable Mapper, it will not affect to the output schema. To make changes, go to the output schema if the Merge Mapper.

If you load a different schema with attributes while a schema is defined, the order of the elements may not be maintained. In this case, please edit manually or reload the schema.

When a schema is loaded, it will not be notified to the component of the input/output destination.

There are cases where you cannot cut, copy or paste logic icons by shortcut key on a Mapping Canvas. Please try the right-click menu or the Designer menu.

When selecting several logic icons on a Mapping canvas and move those to a different place, there are cases where logic icons are placed offscreen. If so please check "Select All" to logic icons and move them on the screen.

Notes

The data model of output data always becomes XML type.
- Even if the schema of the table model is set to the output schema, it is necessary to set "/table/row" to the division passing when the data flow is pulled to the repetition processing (data number).
- The null value read from the data base etc. is converted into the dead letter character and output in the merge only application.
  Therefore, the result when null of the output value is checked with the following Document Mapper of merging etc. becomes "false".

The view of real-time execution doesn't change in the switch of the tab when two or more merging is started.
Click the icon of Merge in real time executed with the canvas of the corresponding script, and give focus.

When the uniting processing is done by Merge, the null character, the tab, and changing line included before and behind data can be deleted.
Refer to "Property reference" for details.

The new line character in the output is "LF".