Today we’re releasing the latest version of the 2.0 series of Neo4j, version 2.0.1. For more details on Neo4j 2.0.0 see the December release blog post .
This is a maintenance release and has no new features although it contains significant stability and performance improvements.

We’ve made some improvements to the way updates are propagated around an HA cluster and have improved stability when instances join, leave or fail in an HA cluster.

A performance issue when creating unique constraints has been addressed and there have also been changes to Cypher –  to allow it to support double literals in exponent form and UTF-8 characters in identifiers. Issues around Cypher index lookup have also been addressed.

All Neo4j users are strongly recommended to upgrade to this release. Neo4j 2.0.1 does not require any store-level upgrades from the previous 2.0.0 release. You can download from the Neo4j web site.

For information about upgrading from Neo4j 1.9 or earlier, please see our Upgrading to Neo4j 2.0 FAQ .

For a full summary of changes in this release, please see the release notes .

For the Neo4j team

Mark Needham

Want to learn more about graph databases? Click below to get your free copy of O’Reilly’s Graph Databases ebook and discover how to use graph technologies for your application today.

Download My Ebook



davidsblog says:

This change appears to break my query: <br /><br />&gt; WITH count(DISTINCT total) AS tots, timestamp() AS time<br />&gt; MATCH (ia:Ingredient)&lt;-[:HAS_INGREDIENT]-(recab:Recipe)-[recHasB:HAS_INGREDIENT]-&gt;(ib:Ingredient)<br />&gt; WHERE id(ia)=5167<br />&gt; WITH DISTINCT ib AS idB, count(DISTINCT recab) AS recAB , count(DISTINCT recHasB) AS recB, tots, time<br />&gt;

jake george says:

Data Modeling Online Training<br />Click Here For Enquiry –<br />Chapter 1: Data Modeling Concepts<br /> Data Modeling Development Cycle<br /> Data Modeling Standards<br /> Steps to Create a Data Model<br /> Data Modeler Role<br /> Enterprise Data Modeling<br /> Conceptual Data Modeling

Leave a Reply

Your email address will not be published. Required fields are marked *