Defining the processing component - Cloud - 8.0

addComponent {
	setComponentDefinition {
		TYPE: "tMap",
		NAME: "tMap_1",
		POSITION: 480, 256
	}
}

In this example, the data type of the id and age columns is String in the input schemas while it's Integer in the output schema. Enable the automatic type conversion feature of the component and leave the other settings as default.

	setSettings {
		ENABLE_AUTO_CONVERT_TYPE : "true"
	}

In this example, the output flow is named out and it contains four columns:

• id, type Integer, two characters long

• full_name, type String

• age, type Integer, two characters long

• city, type String

	addSchema {
		NAME: "out",
		CONNECTOR: "FLOW",
		LABEL: "out"
		addColumn {
			NAME: "id",
			TYPE: "id_Integer",
			LENGTH: 2
		}
		addColumn {
			NAME: "full_name",
			TYPE: "id_String"
		}
		addColumn {
			NAME: "age",
			TYPE: "id_Integer",
			LENGTH: 2
		}
		addColumn {
			NAME: "city",
			TYPE: "id_String"
		}
	}

Node that the column definitions must be the same as those for the first tFileInputDelimited component.

	addMapperData {
		addInputTable {
			NAME: "row1"
			addColumn {
				NAME: "id",
				TYPE: "id_String"
			}
			addColumn {
				NAME: "name",
				TYPE: "id_String"
			}
			addColumn {
				NAME: "age",
				TYPE: "id_String"
			}
			addColumn {
				NAME: "city",
				TYPE: "id_String"
			}
		}
	}

Node that the column definitions must be the same as those for the second tFileInputDelimited component.

Note that this example defines a Left Outer Join. To define an Inner Join, add the ISINNERJOIN: true parameter in the addInputTable {} function.

		addInputTable {
			NAME: "row2"
			addColumn {
				NAME: "id",
				TYPE: "id_String"
				EXPRESSION: "row1.id"
			}
			addColumn {
				NAME: "family",
				TYPE: "id_String"
			}
		}

The column definitions must be the same as those defined in the schema settings. Note that the ID parameter is required, but it needs a value only when the output table uses a Repository schema.

Note that the full_name column is a combination of the name column of the main input flow and the family column of the lookup flow, with a space in between.

		addOutputTable {
			ID: "",
			NAME: "out"
			addColumn {
				NAME: "id",
				TYPE: "id_Integer",
				EXPRESSION: "row1.id"
			}
			addColumn {
				NAME: "full_name",
				TYPE: "id_String",
				EXPRESSION: "row1.name  + \" \" + row2.family"
			}
			addColumn {
				NAME: "age",
				TYPE: "id_Integer",
				EXPRESSION: "row1.age"
			}
			addColumn {
				NAME: "city",
				TYPE: "id_String",
				EXPRESSION: "row1.city "
			}
		}