Numeric routine - 7.3

Talend Open Studio User Guide
Version
7.3
Language
English
Product
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Module
Talend Studio
Content
Design and Development
Last publication date
2023-10-11
Available in...

Open Studio for Big Data

Open Studio for Data Integration

Open Studio for ESB

The Numeric routine contains several functions which allow you to return whole or decimal numbers in order to use them as settings in one or more Job components.

You can access the numeric routine functions by double-clicking the Numeric node under the system routines folder in the Repository tree view. The Numeric routine contains several functions, notably sequence, random and convertImpliedDecimalFormat.

Function

Description

Syntax

sequence

Returns an incremental numeric ID.

Numeric.sequence("Parameter name", start value, increment value)

resetSequence

Creates a sequence if it doesn't exist and attributes a new start value.

Numeric.resetSequence (Sequence Identifier, start value)

removeSequence

Removes a sequence.

Numeric.removeSequence (Sequence Identifier)

random

Returns a random whole number between the maximum and minimum values.

Numeric.random(minimum start value, maximum end value)

convertImpliedDecimalFormat

Returns a decimal with the help of an implicit decimal model.

Numeric.convertImpliedDecimalFormat ("Target Format", value to be converted)

The three routines sequence, resetSequence, and removeSequence are closely related.

  • The sequence routine is used to create a sequence identifier, named s1 by default, in the Job. This sequence identifier is global in the Job.

  • The resetSequence routine can be used to initialize the value of the sequence identifier created by sequence routine.

  • The removeSequence routine is used to remove the sequence identifier from the global variable list in the Job.

Note: When using the tRunJob component, the sequence identifier is shared by the parent Job and all child Jobs across the whole JVM. You should use unique identifier if you do not want to use it globally.