tActionReject

Receives data rejected after Flow processing.

It is possible to add multiple tActionReject components
in an Integration Action, but all these components must have the same schema. Otherwise,
rejected rows will be mixed up and not easy to read.

This component is used with Integration Actions to output rejected data.

For further information about Integration Actions, see
Talend Studio Developer Guide.

tActionReject Standard properties

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

The Standard
tActionReject component belongs to the Talend Cloud family.

This component is available in the Palette of the
Integration
perspective of the Studio only if you have subscribed
to one of the
Talend Platform
solutions or Big Data
solutions.

Basic settings

Schema and Edit Schema	A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository. 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.
	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 Job designs. Related topic: see Talend Studio User Guide.

Schema and Edit
Schema

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

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.

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
Job designs. Related topic: see
Talend Studio

User Guide.

Advanced settings

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

Usage

Usage rule	This component is used with other components in the Talend Cloud family to design Integration Actions. These Integration Actions can then be published to the web application and used to design Flows in the Cloud.

Related scenario

For a related scenario, see Scenario 1: Filtering customer data (deprecated).

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 6.x

0 Comments

Inline Feedbacks

View all comments

tActionReject – Docs for ESB 6.x