tMarkLogicBulkLoad Standard properties

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

The Standard tMarkLogicBulkLoad component belongs to the Big Data and the Databases NoSQL families.

The component in this framework is available in all Talend products with Big Data and in Talend Data Fabric.

Basic settings

Property Type	Either Built-In or Repository. Built-In: No property data stored centrally. Repository: Select the repository file in which the properties are stored. The database connection fields that follow are completed automatically using the data retrieved.
Use an existing connection	Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined. Information noteNote: When a Job contains the parent Job and the child Job, do the following if you want to share an existing connection between the parent Job and the child Job (for example, to share the connection created by the parent Job with the child Job). In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection. 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 Sharing a database connection.
Host	Enter the IP address or hostname of the MarkLogic server.
Port	Enter the listening port number of the MarkLogic server.
Database	Enter the name of the MarkLogic database you want to use.
Username and Password	Enter the user authentication data to access the MarkLogic database. 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.
Load Folder	Specify the directory to the local files to be imported into the MarkLogic database.
DocId Prefixed As	Specify the prefix used to construct the URI of the imported files. For more information about the URI construction, see https://docs.marklogic.com/guide/ingestion/content-pump#id_14982.

Advanced settings

Additional MLCP Parameters	Specify additional options for the MLCP import command. For more information about the import options, see https://docs.marklogic.com/guide/ingestion/content-pump#id_63999.
Use external MLCP process	As the MarkLogic Content Pump (MLCP) program is required on the machine where you run your Job that involves this component, you can do either of the following: Keep this check box clear to use a built-in MLCP library when running this component to load data. In this case, your Job is memory demanding. If you need to use your own MLCP, that is to say, an MLCP external to Talend Studio, select this check box. In this case, your Job itself is not memory demanding but your MLCP process is. For further information about MLCP, see the related Marklogic documentation: Loading Content Using Marklogic Content Pump.
tStatCatcher Statistics	Select this check box to gather the Job processing metadata at the Job level as well as at each component level.

Additional MLCP Parameters

Specify additional options for the MLCP import command. For more information about the import options, see https://docs.marklogic.com/guide/ingestion/content-pump#id_63999.

Use external MLCP process

As the MarkLogic Content Pump (MLCP) program is required on the machine where you run your Job that involves this component, you can do either of the following:

Keep this check box clear to use a built-in MLCP library when running this component to load data. In this case, your Job is memory demanding.
If you need to use your own MLCP, that is to say, an MLCP external to Talend Studio, select this check box. In this case, your Job itself is not memory demanding but your MLCP process is.

For further information about MLCP, see the related Marklogic documentation: Loading Content Using Marklogic Content Pump.

tStatCatcher Statistics

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

Global Variables

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. 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.

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

Usage

Usage rule	This component can be used together with the tMarkLogicInput component to check if the files are imported as expected.
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 connection 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 settings and context variables, see Dynamic schema and Creating a context group and define context variables in it.
Limitation	The MarkLogic Content Pump (MLCP) tool needs to be installed on the machine where you run the Job that involves this component.

Usage rule

This component can be used together with the tMarkLogicInput component to check if the files are imported as expected.

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 connection 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 settings and context variables, see Dynamic schema and Creating a context group and define context variables in it.

Limitation

The MarkLogic Content Pump (MLCP) tool needs to be installed on the machine where you run the Job that involves this component.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here