URI Format - 6.3

Talend Data Mapper User Guide

EnrichVersion
6.3
EnrichProdName
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
task
Design and Development
EnrichPlatform
Talend Studio
tdm://pathToMap?options		

The pathToMap is the fully qualified path to the map to invoke, where the first component is the project name. For example: //Examples/Maps/Java/AcmoPOToJava.

Table 1.  tdm Component Options

Name

Values

Required

Default

Description

exceptionThreshold

WARNING, ERROR, FATAL

no

FATAL

The value of the map execution status severity that will result in an exception being thrown.

outputTypeDefault, String, Byte Array, InputStreamnoDefault

The following output types are available:

  • Default: The default output is the same as the input, or Java if the map outputs Java.

  • String: Use this option if the data in the output column is to be a String.

  • Byte Array: Use this option if the data in the output column is to be a Byte array.

  • InputStream: Use this option if you are working with Talend Data Mapper metadata and the input is a stream.

projectArchives

List of String separated by commas

no

None

A list of URLs for the project archives that are required to execute the map. This includes the project that contains the map and any other required project (due to map or structure inheritance). The URL can have either a file scheme, or classpath . For the classpath scheme, the path of the URL is the project archive on the classpath.

projects

List of String separated by commas

no

None

A list of the names of the projects that are required to execute the map. This is used when the Mapper Runtime for Camel is being executed inside of Eclipse and you want to use the projects that are in the Eclipse workspace. If this is specified, the projectArchives option is not used.

log

string

no

 

Used to define runtime logging. This value is passed to the runtime to define the desired content for logging. Use infrequent to log only warnings or higher as well as startup/shutdown events. Use frequent to log a message about each transformation executed. Use all to get full debug tracing, which can be helpful in diagnosing problems.