Skip to main content

Component-specific settings for tSortRow

The following table describes the Job script functions and parameters that you can define in the setSettings {} function of the component.

Function/parameter Description Mandatory?

CRITERIA {}

Use this function to define the sort rules. Each sort rule is composed of three parameters:

  • COLNAME: Use this parameter to specify the schema column to sort.
  • SORT: Use this parameter to specify the sort type, in accordance with the type of the input column:
    • alpha: alphabetic order
    • num: numeric order
    • date: chronological order
  • ORDER: Use this parameter to specify the sort order:
    • asc: ascending order
    • desc: descending order

Note that multiple sort rules are prioritized as per the order they are defined.

Yes

EXTERNAL

Set this parameter to true to customize the memory used to temporarily store output data.

By default, this parameter is set to false.

No

TEMPFILE

Use this parameter to specify the location where the temporary files should be stored.

The default directory is <studio_install_dir>/workspace/temp, where <studio_install_dir> is your Talend Studio installation directory.

This parameter works only when EXTERNAL is set to true.

No

CREATEDIR

Set this parameter to true to create the temporary file directory if it does not exist.

By default, this parameter is set to true.

This parameter works only when EXTERNAL is set to true.

No

EXTERNAL_SORT_BUFFERSIZE

Use this parameter to specify the buffer size, namely the number of rows that can be buffered in the memory before a temporary file is generated on the hard disk.

The default value is 1000000.

This parameter works only when EXTERNAL is set to true.

No

TSTATCATCHER_STATS

Set this parameter to true to gather the processing metadata at the Job level as well as at each component level.

By default, this parameter is set to false.

No

LABEL

Use this parameter to specify a text label for the component.

No

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!