tMDMInput Standard properties

Property Type

Either Built in or Repository.

Built-in: No property data stored centrally

Repository: Select the repository file where properties are stored. The fields that follow are completed automatically using the fetched data

Schema and Edit Schema

A schema is a row description, it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote 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: The schema will be created and stored for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Repository: The schema already exists and is stored in the repository. You can reuse it in various projects and jobs. For more information about a component schema in its Basic settings tab, see Basic settings tab.

MDM version

By default, Server 6.0 is selected. Although it is recommended to migrate existing Jobs for this new version, the Server 5.6 option is available to ease the process of the migration of your Jobs so as to keep them working without modification with a 6.0 server. To do so, an option on the server must be enabled to accept and translate requests from such Jobs.

URL

Type in the URL to access the Talend MDM Server.

Username and Password

Type in user authentication data for the Talend MDM Server

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

Entity

Type in the name of the business entity that holds the data you want to read.

Data Container

Type in the name of the data container that holds the data you want to read.

Type

Select Master or Staging to specify the database on which the action should be performed.

Use multiple conditions

Select this check box to filter the data using certain conditions.

• Xpath: Enter between quotes the path and the XML node to which you want to apply the condition.

• Function: Select an operator to be used from the list. The following operators are available:

  • Contains: Returns a result which contains the word or words entered. Note that full text search does not support special characters, for example, @, #, $.
  • Contains the sentence: Returns one or more results which contain the sentence entered.
  • Joins With: This operator is reserved for future use.
  • Starts With: Returns a result which begins with the string entered.
  • Equal: Returns a result which matches the value entered.
  • Not Equal: Returns a result of any value other than the null value and the value entered.
  • is greater than: Returns a result which is greater than the numerical value entered. Applies to number fields only.
  • is greater or equal: Returns a result which is greater than or equal to the numerical value entered. Applies to number fields only.
  • is lower than: Returns a result which is less than the numerical value entered. Applies to number fields only.
  • is lower or equal: Returns a result which is less than or equal to the numerical value entered. Applies to number fields only.
  • whole content contains: Performs a plain text search using the specified Xpath field in the selected data container. If you enter an empty string "" in the Xpath field and select whole content contains from the Function list, searches will be performed in all the fields of all entities in the selected data container.
  • is empty or null: Returns an empty field or a null value.

  Before using the conditions, bear in mind the following:

  • Depending on the type of field the Xpath points to, only certain operators apply. For example, if the field is a boolean, only the Equal or Not Equal operators are appropriate.

  • Searches in the master database support both full text search and standard SQL search, while searches in the staging database only support standard SQL search. For more information about how to manage database search modes, see Managing database search modes.

  • Standard SQL search considers the search content as an integrate phrase to be matched, while full text search interprets the search content as a phrase which contains multiple words, and the records that match any of the words will be returned. For example, if the search content is "test first name", full text search considers it as three independent words "test", "first", and "name", while standard SQL search considers it as one phrase "test first name".

  • The operator Not Equal does not support multi-occurrence fields or complex type fields.

• Value: Enter between inverted commas the value you want to use. Note that if the value contains XML special characters such as /, you must also enter the value in single quotes ("'ABC/XYZ'") or the value will be considered as an XPath.

• Predicate: Select a predicate from the drop-down list.

  The predicates none (default), or, and, and Not are now available for use. The other predicates are reserved for future.

  • none (default): is interpreted as and by default.
  • or: returns a record if any of the conditions separated by it is true.
  • and: returns a record if all the conditions separated by it are true.
  • Not: returns a record if the condition on which it is defined is not true.
  Information noteNote: The or predicate is interpreted only if it is defined on all conditions, except the last condition. Otherwise the or predicate is always interpreted as and. For more information, see the related description of behaviors of filters using multiple conditions and predicates in Talend MDM on Talend Help Center (https://help.talend.com).

If you clear this check box, you have the option of selecting particular IDs to be displayed in the ID value column of the IDS table.

Skip Rows

Enter the number of lines to be ignored.

Max Rows

Maximum number of rows to be processed. If Limit = 0, no row is read or processed.

Die on error

Select this check box to skip the row in error and complete the process for error-free rows. If needed, you can retrieve the rows in error via a Row > Rejects link.

Batch Size

Number of lines in each processed batch.

Loop XPath query

The XML structure node on which the loop is based.

Mapping

Column: reflects the schema as defined in the Edit schema editor.

XPath query: Type in the name of the fields to extract from the input XML structure.

Get Nodes: Select this check box to retrieve the Xml node together with the data.

tStatCatcher Statistics

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

Global Variables

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.

NB_LINE: the number of rows processed. This is an After variable and it returns an integer.

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 more information about variables, see Using contexts and variables.

Usage rule

Use this component as a start component. It needs an output flow.

If an MDM entity has a large number of foreign key fields, it may take you a long time to query data records that pertain to the entity using the tMDMInput component.

For more information about the workaround, see the article How to read data effectively that pertains to an MDM entity with many foreign key fields.

You can increase the timeout values for a Job using this component to help process a large number of data records. For more information, see advanced execution settings for JVM parameters in the article Timeout values for a Job using MDM components.