August 17, 2023

tCombinedSQLFilter – Docs for ESB 5.x

tCombinedSQLFilter

tCombinedSQLFilter_icon32_white.png

tCombinedSQLFilter Properties

Component family

ELT/CombinedSQL

 

Function

tCombinedSQLFilter allows you to
alter the schema of a source table through column name mapping and
to define a row filter on that table. Therefore, it can be used to
filter columns and rows at the same time. This component has
real-time capabilities since it runs the data filtering on the DBMS
itself.

Purpose

Helps to filter data by reorganizing, deleting or adding columns
based on the source table and to filter the given data source using
the filter conditions.

Basic settings

Schema and Edit
schema

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.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:

  • View schema: choose this option to view the
    schema only.

  • Change to built-in property: choose this option
    to change the schema to Built-in for local
    changes.

  • Update repository connection: choose this option to change
    the schema stored in the repository and decide whether to propagate the changes to
    all the Jobs upon completion. If you just want to propagate the changes to the
    current Job, you can select No upon completion and
    choose this schema metadata again in the [Repository
    Content]
    window.

Click Sync columns to retrieve
the schema from the previous component connected in the Job.

 

 

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

 

 

Repository: You have already
created the schema and stored it in the Repository. You can reuse it
in various projects and Jobs. Related topic: see Talend Studio User
Guide
.

 

Logical operator between conditions

Select the logical operator between the filter conditions defined
in the Conditions panel.

Two operators are available: Or,
And.

 

Conditions

Select the type of WHERE clause along with the values and the
columns to use for row filtering.

 

 

Input Column: Select the column
to filter in the list.

 

 

Operator: Select the type of the
WHERE clause: =, < >,
>
, <,
>=, <=, LIKE,
IN, NOT
IN
, and EXIST
IN
.

 

 

Values: Type in the values to be
used in the WHERE clause.

 

 

Negate: Select this check box to
enable the condition that is opposite to the current setting.

 

Use custom SQL

Customize a WHERE clause by selecting this check box and editing
in the SQL Condition field.

Advanced settings

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a
Job level as well as at each component level.

Global Variables

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

QUERY: the SQL 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 +
Space
to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio
User Guide.

Usage

This component is an intermediary component. The use of the
corresponding connection and commit components is recommended when
using this component to allow a unique connection to be open and
then closed during the Job execution.

Limitation

n/a

Related Scenario

For a related scenario, see Scenario: Filtering and aggregating table columns directly on the DBMS.


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