tNeo4jRow Standard properties

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.

DB version

Select the Neo4j version you are using.

When you are using Neo4j version 3.2.X, this component works in the remote mode only. Therefore, if you want to reuse a connection to Neo4j V3.2.X from tNeo4jConnection, ensure that you have selected the Remote server check box and properly configured the connection.

Do not use a 2.X.X version and a 3.X.X version in the same Job. Otherwise, class conflict issues occur.

Neo4j version 2.X.X is compatible only with Java 7 or higher but it offers support of advanced features such as node labels.

This list is not shown if the Use an existing connection check box is selected.

Upon selecting a database version, you will be prompted to install the corresponding database driver JAR files if not yet installed. For details, see Installing external modules.

Remote server

Select this check box if you use a Neo4j remote server, and specify the root URL in the Server URL field.

This check box appears only if you do not select the Use an existing connection check box and you are not using Neo4j V3.2.X. With V3.2.X, this component supports the remote mode only.

Database path

If you use Neo4j in embedded mode, specify the directory to hold your data files. If the specified directory does not exist, it will be created.

This field appears only if you do not select the Use an existing connection check box or the Remote server check box.

Shutdown after job

Select this check box to shutdown the Neo4j database connection when no more operations on Neo4j are going to be performed after the current component.

Alternatively, you can use tNeo4jClose to shutdown the database.

This avoids errors such as "Id file not properly shutdown" at next execution of Jobs involving Neo4j.

This check box is available only if the Use an existing connection check box is not selected.

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.

Built-In: You create and store the schema locally for this component only.

Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are integers or functions, ensure that these default values are not enclosed within quotation marks. If they are, you must remove the quotation marks manually.

For more information, see Retrieving table schemas.

Query

Enter your Cypher query in double quotes. If you have some parameters corresponding to the input schema columns, declare them with curly brackets ({}) and map them in the Parameters table.

Parameters

Click the [+] button to add parameters corresponding to your Cypher query and map them with the input schema columns.

• Parameter name: Type in the name of your parameter, in double quotes.
• Parameter value: Select the schema column you want to map your parameter with.

Die on error

This check box is selected by default. Clear the check box to skip the row on error and complete the process for error-free rows.

tStatCatcher Statistics

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

Commit every

Enter the number of rows to be completed before committing batches of nodes together the database. This option ensures transaction quality (but not rollback) and, above all, better performance at execution.

This option is only supported by the embedded mode of the database. You cannot make transactions in REST mode, that is to say, not on a remote server in the deprecated 2.X.X versions.

Global Variables

NB_NODE_INSERTED: the number of nodes inserted. This is an After variable and it returns a long.

NB_RELATIONSHIP_INSERTED: the number of relationships inserted. This is an After variable and it returns a long.

NB_PROPERTY_UPDATED: the number of properties updated. This is an After variable and it returns a long.

NB_NODE_DELETED: the number of nodes deleted. This is an After variable and it returns a long.

NB_RELATIONSHIP_DELETED: the number of relationships deleted. This is an After variable and it returns a long.

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 rule