Release Date: 21 May 2015
Neo4j 2.2.2 is a maintenance release, with critical improvements.
Notably, this release:
- Provides support for running Neo4j on Oracle and OpenJDK Java 8 runtimes
- Resolves an issue that prevented the Neo4j Browser from loading in the latest Chrome release (43.0.2357.65).
- Corrects the behavior of the
:play sysinfo) browser directive.
- Improves the import tool handling of values containing newlines, and adds support for skipping duplicate nodes in the input data.
- Resolves a number of critical issues with the 2.2 Cypher compiler, which affect validity of queries and correctness of results.
- Improves recovery after a non-clean shutdown, by applying outstanding transactions in batch.
- Improves write performance for label creation, by batching label scan index writes initiated in concurrent transactions.
- Resolves a logging issue in Neo4j Desktop, that could result in duplicated logging output after multiple restarts.
- Resolves a logging issue in Neo4j Enterprise, that could result in excessive logging during network outages (Neo4j Enterprise).
- Resolves an issue in the automatic configuration of the HPC cache, whereby systems with large amounts of memory would result in an error when trying to allocate an excessively large cache array (Neo4j Enterprise).
- Ensures HA cluster instances abort after a first attempt to join a cluster containing an unrecognized database, instead of continually re-attempting to join (Neo4j Enterprise).
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.)
For a full summary of changes in this release, please review the CHANGES.TXT file contained within the distribution.