Neo4j 2.1 – Graph ETL for Everyone
From the post:
It’s an exciting time for Neo4j users and, of course, the Neo4j team as we’re releasing the 2.1 version of Neo4j! You’ve probably already seen the amazing strides we’ve taken when releasing our 2.0 version at the start of the year, and Neo4j 2.1 continues to improve the user experience while delivering some impressive under-the-hood improvements, and some interesting work on boosting Cypher too.
Easy import with ETL features directly in Cypher
Graphs are everywhere, but sometimes they’re buried in other systems and legacy databases. You need to extract the data then bring it into Neo4j to experience its true graph form. To help you do this, we’ve brought bulk load functionality directly into Cypher. The new LOAD CSV clause makes that a pleasant and simple task, optimized for graphs around millions scale – the kind of size that folks typically encounter when getting started with Neo4j.
Err, but the line:
You need to extract the data then bring it into Neo4j to experience its true graph form.
isn’t really true is it?
In other words, to process a graph with Neo4j, you have to extract, transform and load the date into Neo4j. Yes?
That is if I could address the data in situ (in its original place) and add the properties I need to process it as a graph, no extraction, transformation and loading are necessary.
Yes?
Not to downplay the usefulness of better importing, if your software requires it, but we do need to be precise about what is being described.
There are other new features and improvements so download a copy of Neo4j 2.1 today!