To connect to an HDFS installation, select the Define a storage configuration component check box and then
select the name of the component to use from those available in the
This option requires you to have previously configured the connection
to the HDFS installation to be used, as described in the documentation
for the tHDFSConfiguration
If you leave the Define a storage
configuration component check box unselected, you can only
convert files locally.
Before you configure this component, you must have already added a
downstream component and linked it to the tHMapInput component, and retreived the schema from the
To configure the component, click the [...] button and, in the [Component
Configuration] window, perform the following actions.
Click the Select button next
to the Record structure field
and then, in the [Select a
Structure] dialog box that opens, select the map you
want to use and then click OK.
This structure must have been previously created in Talend Data Mapper.
Select the Input
Representation to use from the drop-down list.
Supported input formats are COBOL, EDI, Flat, IDocs, JSON and
Tell the component where each new record begins. In order for
you to be able to do so, you need to fully understand the
structure of your data.
Exactly how you do this varies depending on the input
representation being used, and you will be presented with one of
the following options.
Select an appropriate record delimiter for your data.
Note that you must specify this value without quotes.
lets you specify a separator indicator, such as
\n, to identify
a new line.
Supported indicators are \n for a Unix-type new
line, \r\n for
Windows and \r
for Mac, and \t
for tab characters.
lets you specify the initial characters that
indicate a new record, such as <root.
also supports new lines, \n for a Unix-type new line, \r\n for Windows and
\r for Mac, and
\t for tab
If your input representation is COBOL, define the
signature for the input record structure:
corresponds to the size in bytes of the smallest
record. If you set this value too low, you may
encounter performance issues, since the component
will perform more checks than necessary when
looking for a new record.
corresponds to the size in bytes of the largest
record, and is used to determine how much memory
is allocated to read the input.
corresponds to the size in bytes of the footer, if
any. At runtime, the footer will be ignored rather
than being mistakenly included in the last record.
Leave this field empty if there is no
Click the Configure button to open the [Edit Signature] window,
select the fields that define the signature of
your record input structure (that is, to identify
where a new record begins), update the Operation and Value columns as
appropriate, and then click OK to return to the [Component Configuration]
To test the signature with a sample file, click the [...] button, browse to the file you want
to use as a sample, and then click Open.
Testing the signature lets you check that the total number of
records and their minimum and maximum length corresponds to what
you expect based on your knowledge of the data. This step
assumes you have a local subset of your data to use as a
Click Run to test your
Map the elements from the input structure to the output
structure in the new map that opens, and then press Ctrl+S to save your map.
For more information on creating maps, see Talend Data Mapper User Guide.