tNeo4jv4Output Standard properties

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, and then in the pop-up dialog box enter the password between double quotes and click OK to save the 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. 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:

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

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.

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

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 further information about variables, see Talend Studio User Guide.

Usage rule