Release Date: 11/13/2015

Neo4j 2.2.7 is a maintenance release, with critical improvements.

Highlights

  • Fixes #5631MERGE with multiple labels respects uniqueness constraints
  • Fixes #5799 – to match variable length patterns of length one
  • Fixes neo4j-import handling of nodes with many labels, which might have been observed as an InvalidRecordException
  • neo4j-import treats extra data columns without a corresponding header as “bad”. New option --ignore-extra-columns to log those into the “bad” file
  • When stopping Neo4j, the timeout will no longer forcefully shut down the process (which would require recovery on next start). Instead, a warning is displayed and waiting will continue.
  • Within a cluster, slaves which fail to apply updates will kernel panic to prevent further updates attempts, which could cause other harm. Failure to apply a transaction may be caused by severe underlying problems, for example out of disk space.

Detailed Changes

For the complete list of all changes, please see the changelog.

Upgrading

All Neo4j users are recommended to upgrade to this release. Upgrading to Neo4j 2.2 (from Neo4j 2.1 or earlier) requires a migration to the on-disk store and can not be reversed. Please ensure you have a valid backup before proceeding. Production users of Neo4j 2.1, or earlier, should note that there will be configuration changes required and that applications will need to be updated to support authentication of database requests. Please see our Upgrading to Neo4j 2.2 FAQ for further details.

(Note: Neo4j 1.9 users may also upgrade directly to this release, and are recommended to do so carefully. We strongly encourage verifying the syntax and validating all responses from your Cypher scripts, REST calls, and Java code before upgrading any production system. For information about upgrading from Neo4j 1.9, please see our Upgrading to Neo4j 2 FAQ.)