Importing the actors data into Neo4j
Procedure
-
Double-click the first tFileInputDelimited component to open its Basic settings view on the Component tab.
-
In the File name/Stream field, specify
the path to the CSV file that describes the actors' names, the years they
were born in, and their roles in the movies.
The input CSV file used in this example is as follows:
Name;Born Keanu Reeves;1964 Laurence Fishburne;1961 Carrie-Anne Moss;1967
- In the Header field, specify the number of rows to skip as header rows. In this example, the first row of the CSV file is the header row.
-
Click the [...] button next to Edit schema to open the Schema dialog box, and define the input schema based on
the structure of the input file. In this example, the input schema is
composed of two columns, name and
born, both of type String.
When done, click OK to close the Schema dialog box and propagate the schema to the next component.
-
Click the first tNeo4jOutput component
and select the Component tab to open its
Basic settings view.
- Select the Use an existing connection check box to reuse the Neo4j database connection opened by the tNeo4jConnection component, which is the only connection component used in this example.
- Double-click the tNeo4jOutput component or click the Mapping button on the component's Basic settings view to open the index and relationship mapping editor.
-
With the name column selected from the
schema panel, click the Index creation tab,
click the [+] button to add a row in the
table, and create an index named name on
this column:
-
In the Name field, enter name between double quotation marks.
-
In the Key field, enter name between double quotation marks to give the index a key name.
Then click in the schema panel to validate your index creation, and click OK to close the mapping editor. -
- Select the Use label (Neo4j > 2.0) check box and enter Actors between double quotation marks in the Label name field so that the nodes to be created will be labeled Actors.
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 – please let us know!