tNeo4jv4Output Standard properties
These properties are used to configure tNeo4jv4Output running in the Standard Job framework.
The Standard tNeo4jv4Output component belongs to the Big Data and the Databases NoSQL families.
The component in this framework is available in all subscription-based Talend products.
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 related fields that follow are completed automatically using the data retrieved. |
Connection URI |
Enter the connection URI. Click Connection URIs for related information. |
Username and Password |
Enter the username and the password for the Neo4j version 4.x database authentication. To enter the password, click the [...] button
next to the Password field to bring out the Enter a new
password dialog box, enter the password in the text field, and click
OK. Note that you can enter the password either in a JSON string
in the pure password mode or as a Java expression in the Java
mode. You can toggle between the two modes by clicking switch to
Java mode or switch to pure password mode on the top
of the text field.
Information noteNote:
|
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. When you create a Spark Job, avoid the reserved word line when naming the fields. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
|
Query |
Enter your Cypher query in double quotes. |
Set database name |
Select this option to specify the database by providing the database name in the Database name field. |
Send data as list |
Select this option to group incoming data into lists before sending the data to the Neo4j server. After selecting this option, you need to set the data list name in the Data list name field. |
Parameters |
Enter the query parameters and schema columns, which binds query parameters to schema columns. You need to fill this table only when the parameter names are not the same as the corresponding schema column names. Note that for query parameters whose names are neither the same as any schema column names nor bound to schema columns in this table, they will be set to null and the nodes will be created without any properties. |
Advanced settings
Max batch size |
Set the maximum number of lines allowed in each batch. Do not change the default value unless you are facing performance issues. Increasing the batch size can improve the performance but a value too high could cause Job failures. |
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 |
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 integer. 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 is used as an output component and it always needs an incoming link. |
Limitation | n/a |