Release Date: 31 August 2016
Neo4j 2.3.7 is a maintenance release with critical improvements.
Highlights
- Open indexes in read only mode in case database started in read only mode to prevent cases when usage of interrupts will result in deleted index (not applicable to ha setup)
- Automatically rebuild indexes that fail to open on startup.
- Allow node id reuse using ‘dbms.ids.reuse.types.override’ setting in Enterprise Edition
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.3 (from Neo4j 2.2 or earlier) requires a migration to the on-disk store and cannot 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.3 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.3 FAQ.)