Skip to main content Skip to complementary content

Creating relationships in bulk



  1. Double-click the third tFileInputDelimited component to open its Component view.
  2. In the File name/Stream field, enter the path or browse to the CSV file that describes the actor-movie relationships.

    The input CSV file used in this example reads as follows:


    The double quotation marks on the role names are not mandatory. The value ACTED_IN is an user-defined relationship type that explains the relationship between the actors and the movies.

  3. Click the [...] button next to Edit schema to open the schema editor, and define the input schema based on the structure of the input file.

    In this example, the columns are from, role, to and type.

  4. Click OK to close this editor and accept the propagation of the schema to the next component.
  5. In the Field separator field, enter a comma (,) to replace the default semicolon (;).
  6. Double-click the tNeo4jBatchOutputRelationship component to open its Component view.
  7. Select the Use an existing connection check box to reuse the Neo4j database connection opened by the tNeo4jConnection component.
  8. Verify that the Shutdown after Job check box is clear.
  9. From the Field for relationship type drop-down list, select the column that provides the relationship types.
  10. From the Direction of the relationship drop-down list, select Outgoing.
  11. In the Start node of the relationship area, select the tNeo4jBatchOutput component that provides the index of the start nodes, which is the asActors index in this example from the first tNeo4jBatchOutput. Then from the Field name for the batch index drop-down list, select the column that provides the actor names as the start nodes.
  12. Repeat this action in the End node of the relationship area to select the asMovie index from the second tNeo4jBatchOutput and then select the column that provides the movie names as the end nodes.

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!