One Import Tool to Rule them All
summary
Uniform YAML/JSON import specification that maps pluggable sources to node and relationship targets and runs unchanged against both neo4j-admin offline import and an Apache Beam runtime. It ships as a JVM library with a source-plugin hook (demoed with Parquet and BigQuery sources), declarative targets plus a query escape hatch, and an actions stage for Cypher post-processing. Demo imports the Sakila dataset end-to-end using a pre-release admin image, test assertions pass and generated DB files produce the expected nodes and relationships.
AI-written summary · about
chapters (6)
- 0:00Introduction and team
- 1:13Why import spec
- 5:53Import spec concepts
- 13:08Demo setup
- 26:12Apache Beam demo
- 29:03Future improvements
related talks
30mOne Configuration, Many Imports
42mNeo4j in the Cloud with NoCode Imports
15mAura Import: Anywhere, Anytime
25mBuilding an Entire Graph Application with Nodestream
08mInterview of Loïc Knuchel
28mNeo4j for Beginners: Pros and Cons, Based on Social Networks
36mVibing with Data -- Multi-Agent Data Modeling and Constructi...
21mSerious Network Analysis Using Hadoop & Neo4j