July 30, 2023

tMySQLValidRows – Docs for ESB 7.x


Checks MySQL database rows against Data Quality patterns (regular

tMySQLValidRows allows you to extract DB rows that match
a given Data Quality pattern.

tMySQLValidRows Standard properties

These properties are used to configure tMySQLValidRows running in the Standard Job framework.

The Standard
tMySQLValidRows component belongs to the Data Quality and the Databases families.

This component is available in Talend Data Management Platform, Talend Big Data Platform, Talend Real Time Big Data Platform, Talend Data Services Platform, Talend MDM Platform and Talend Data Fabric.

Note: This component is a specific version of a dynamic database
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.

Basic settings


Select a type of database from the list and click

Validation type

Either Regex pattern
or DQ rule

  • Regex pattern
    : Validate data in the database against
    regex patterns.

  • DQ rule validation: Validate
    data in the database against DQ rules.

Regex pattern validation

  • Analyzed column: select from the
    schema list the column to analyze.

  • Custom pattern: select this check box to
    define manually your own customized regular expression against
    which you want to check the DB rows.
  • Patterns list: select from the pattern
    list the pattern against which you want to check the DB

DQ rule validation

  • DQ rule list: select from the list the
    rule against which you want to check the DB rows.

  • Query type: Either
    Built-in or

    1. Built-in: fill in manually the
      query statement or build it graphically using
    2. Repository: select the relevant
      query stored in the Repository.
      The Query field is filled in accordingly.
  • Guess query: click the Guess Querry button to
    generate the query which corresponds to your table schema in
    the Query field.

  • Guess schema: click the
    Guess Schema button to retrieve the
    schema from the table.

  • Query: enter your DB query paying
    particular attention to properly sequence the fields in
    order to match the schema definition.

Property type

Either Built-in or Repository.


Built-in: No property data stored


Repository: Select the repository
file where Properties are stored. The fields that come after are
pre-filled in using the fetched data.

DB Version

Select the MySQL version you are using.

Use existing connection

Select this check box and in the Component List click the relevant connection component to
reuse the connection details you already defined.

Note: When a Job contains the parent Job and the child Job, if you
need to share an existing connection between the two levels, for example, to share the
connection created by the parent Job with the child Job, you have to:

  1. In the parent level, register the database connection
    to be shared in the Basic
    view of the connection component which creates that very database

  2. In the child level, use a dedicated connection
    component to read that registered database connection.

For an example about how to share a database connection
across Job levels, see

Talend Studio
User Guide


Database server IP address.


Listening port number of DB server.


Name of the database.

Username and

DB user authentication data.

To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.

Schema and Edit

A schema is a row description, it defines the number of fields to
be processed and passed on to the next component. The schema is
either Built-in or stored remotely
in the Repository.


Built-in: You create and store
the schema locally for this component only. Related topic: see

Talend Studio User


Repository: You have already
created the schema and stored it in the Repository and thus reuse it
when needed. Related topic: see
Talend Studio User

Table Name

Enter the name of the table to be read.

Where clause

Enter a WHERE clause to define a row filter on the table.

You can use the WHERE clause to filter the rows you want to
analyze in the table. This WHERE clause enables you then to retrieve
valid and invalid data that match certain specified criteria or

Advanced settings

Additional JDBC Parameters

Specify additional connection properties for the DB connection you
are creating. This option is not available if you have selected the
Use an existing connection
check box in the Basic


You can press Ctrl+Space to
access a list of predefined global variables.

Enable stream

Select this check box to enables streaming over
buffering. This allows reading from large tables without consuming large
amount of memory in order to optimize the performance.

Trim all the String/Char columns

Select this check box to remove leading and trailing
whitespace from all the String/Char columns.

Trim column

Remove leading and trailing whitespace from defined


Clear the Trim all the String/Char
to enable Trim

tStatCatcher Statistics

Select this check box to collect log data at the component

Global Variables

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an

QUERY: the query statement being processed. This is a Flow
variable and it returns a string.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.


Usage rule

This component can be used as a start or intermediary step. It
requires an output flow.

Dynamic settings

Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

The Dynamic settings table is
available only when the Use an existing
check box is selected in the Basic settings view. Once a dynamic parameter is
defined, the Component List box in the
Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
and context variables, see Talend Studio
User Guide.

Related scenarios

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x