Skip to main content

Component-specific settings for tFilterRow

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?

LOGICAL_OP

Use this parameter to define a logical operator to combine simple conditions and to combine the filter results of both modes if any advanced conditions are defined.

  • && (logical AND): returns the boolean value of true is returned if all conditions are true; otherwise false.

    For each two conditions combined using a logical AND, the second condition is evaluated only if the first condition is evaluated to be true.

  • || (logical OR): returns the boolean value of true if any condition is true; otherwise false.

    For each two conditions combined using a logical OR, the second condition is evaluated only if the first condition is evaluated to be false.

Yes

CONDITIONS {}

Use this Job script function to define as many simple conditions as needed.

Based on the logical operator specified, the conditions are evaluated one after the other in sequential order for each row. When evaluated, each condition returns the boolean value of true or false.

Each condition is composed of the following parameters:

  • INPUT_COLUMN: Use this parameter to specify the column of the schema the filter function is to be operated on.

  • FUNCTION: Use this parameter to specify a filter function.

    Depending the data type of the specified input column, the filter functions you can use vary.

    • To transform the input string to lower case:

      $source == null? false : $source.toLowerCase().compareTo($target) $operator 0

    • To transform the input string to upper case:

      $source == null? false : $source.toUpperCase().compareTo($target) $operator 0

    • To transform the first character of the input string to lower case:

      $source == null? false : $source.toLowerCase().charAt(0) $operator $target

    • To transform the first character of the input string to upper case:

      $source == null? false : $source.toUpperCase().charAt(0) $operator $target

    • To get the length of the input string:

      $source == null? false : $source.length() $operator $target

    • To perform an exact match on the input string:

      $source == null? false : $source.matches($target) $operator true

  • OPERATOR: Use this parameter to specify an operator to bind the input column with the target value.

    • ==: equals
    • !=: not equal to
    • >: greater than
    • <: lower than
    • >=: greater than or equal to
    • <=: lower than or equal to
  • RVALUE: Use this parameter to specify the filtered value.

Yes

USE_ADVANCED

Set this parameter to true to allow using advanced conditions, when the operations you want to perform cannot be carried out through the standard functions offered, for example, different logical operations in the same component.

By default, this parameter is set to false.

No

ADVANCED_COND

Use this parameter to specify one or more advanced conditions.

This parameter works only when the USE_ADVANCED is set to true.

In the case of multiple advanced conditions, use a logical operator between two conditions:

  • && (logical AND): returns the boolean value of true is returned if all conditions are true; otherwise false.

    For each two conditions combined using a logical AND, the second condition is evaluated only if the first condition is evaluated to be true.

  • || (logical OR): returns the boolean value of true if any condition is true; otherwise false.

    For each two conditions combined using a logical OR, the second condition is evaluated only if the first condition is evaluated to be false.

Yes when USE_ADVANCED is set to true

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!