Skip to main content Skip to complementary content

tNeo4jv4ImportTool Standard properties

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

The Standard tNeo4jv4ImportTool 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 related fields that follow are completed automatically using the data retrieved.

Neo4j Home

Enter the Neo4j installation path.

Database name

Enter the name of the database to be created.

Nodes

Provide the CSV files that contain the data to import into the nodes and assign labels to nodes.

  • Path to file: enter the path to the CSV file to be read in double quotation marks. To import data from multiple CSV files, add a row for each of the CSV files.
  • Label(s) for nodes (optional): enter labels for the node in double quotation marks. As prompted, label is optional for node.

A valid CSV file have a header that contains at least the ID column and the LABEL column. See CSV header format for related information.

Skip duplicate nodes

Select this option to import only the first records among the records with the same record ID in a CSV file.

If this option is not selected, an import operation will fail if the CSV file contains records with the same IDs.

Relations

Enter the paths to relationship files in rows of this table. A relationship file contains the information about node entity relationships to be imported. To enter multiple relationship files, add a row for each of the relationship files in the table.

A valid relationship file have a header that contains three fields: START_ID, END_ID, and TYPE. See CSV header format for related information.

Skip bad relationship

Select this option to skip the invalid relationship items in the relationship CSV files specified in the Relation table.

A relationship item is invalid if its START_ID or END_ID fields does not exist in the existing nodes.

Advanced settings

tStatCatcher Statistics

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

Force overwrite database content

Select this option to overwrite the database if the database already exists.

Custom CSV Format

Select this option to customize CSV file format.
  • Delimiter: enter the character that you want to use as the delimiter in the field.
  • Array delimiter: enter the character that you want to use as the array delimiter in the field.
  • Quotation character: enter the character that you want to use as the quotation character in the field.
  • Encoding: enter the name of the encoding that you want to use in the field.

Verbose

Select this option to have additional import information displayed.

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.

Usage

Usage rule

This component is to be used standalone in a subJob to load data in bulk from given CSV files that have been created with specific structure.

For further information about the CSV structure required by Neo4j Import Tool, see Import.

You can use tFileOutputDelimited to create the CSV files to be used.

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 – let us know how we can improve!

Leave your feedback here