Click the Select button next to the Record structure field and then, in the Select a Structure dialog box that opens, select the structure you want to use when converting your file 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 Avro, COBOL, EDI, Flat, IDocs, JSON and XML.
Select the Output Representation to use from the drop-down list. The choices available for the Output representation depend on what you choose for the Input representation.
Supported output formats are Avro, Flat, JSON and XML.
Click Next.
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.
Separator 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.
Start/End with lets you specify the initial characters that indicate a new record, such as <root, or the characters that indicate where a record ends. This can also be a regular expression.
Start with also supports new lines, \n for a Unix-type new line, \r\n for Windows and \r for Mac, and \t for tab characters.
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 sample.
Click Finish.
Minimum Record Size 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.
Maximum Record Size corresponds to the size in bytes of the largest record, and is used to determine how much memory is allocated to read the input.
With the Variable Blocked signature, each block is extracted as the Spark record. Each map execution processes an entire block and not an individual Cobol record, as with other Cobol signatures.
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 sample.
Footer Size 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 footer.
Click the Next button to open the Signature Parameters 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 Next.
In the Record Signature Test window that opens, check that your Records are correctly delineated by scrolling through them with the Back and Next buttons and performing a visual check, and then click Finish.
Create if you want the conversion process to create a new file.
Overwrite if you want the conversion process to overwrite an existing file.