Skip to main content

Handling a positional file based on a dynamic schema

This scenario applies to all Talend products.

For more technologies supported by Talend, see Talend components.

This scenario describes a four-component Job that reads data from a positional file, writes the data to another positional file, and replaces the padding characters with space. The schema column details are not defined in the positional file components; instead, they leverages a reusable dynamic schema. The input file used in this scenario is as follows:

id----name--------city--------
1-----Andrews-----Paris-------
2-----Mark--------London------
3-----Marie-------Paris-------
4-----Michael-----Washington--

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!