Skip to main content

Retrieving bufferized data

This scenario describes a Job that retrieves bufferized data from a subJob and displays it on the console.

For more technologies supported by Talend, see Talend components.

  • Drop the following components from the Palette onto the design workspace: tFileInputDelimited and tBufferOutput.

  • Select the tFileInputDelimited and on the Basic Settings tab of the Component view, set the access parameters to the input file.

  • In the File Name field, browse to the delimited file holding the data to be bufferized.

  • Define the Row and Field separators, as well as the Header.

  • Click [...] next to the Edit schema field to describe the structure of the file.

  • Describe the Schema of the data to be passed on to the tBufferOutput component.

  • Select the tBufferOutput component and set the parameters on the Basic Settings tab of the Component view.

Information noteNote:

Generally speaking, the schema is propagated from the input component and automatically fed into the tBufferOutput schema. But you can also set part of the schema to be bufferized if you want to.

  • Drop the tBufferInput and tLogRow components from the Palette onto the design workspace below the subJob you just created.

  • Connect tFileInputDelimited and tBufferInput via a Trigger > OnSubjobOk link and connect tBufferInput and tLogRow via a Row > Main link.

  • Double-click tBufferInput to set its Basic settings in the Component view.

  • In the Basic settings view, click [...] next to the Edit Schema field to describe the structure of the file.

  • Use the schema defined for the tFileInputDelimited component and click OK.

  • The schema of the tBufferInput component is automatically propagated to the tLogRow. Otherwise, double-click tLogRow to display the Component view and click Sync column.

  • Save your Job and press F6 to execute it.

The standard console returns the data retrieved from the buffer memory.

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 – let us know how we can improve!