Over a million developers have joined DZone.

Neo4j 2.0.2 Maintenance Release

DZone's Guide to

Neo4j 2.0.2 Maintenance Release

· Java Zone ·
Free Resource

Download Microservices for Java Developers: A hands-on introduction to frameworks and containers. Brought to you in partnership with Red Hat.

Today we released the 2.0.2 maintenance release of Neo4j. This release comes with some critical stability improvements as well as a few small but handy Cypher type conversion functions. All Neo4j users are strongly recommended to upgrade to this release.

Head on over to http://www.neo4j.org/download to upgrade to Neo4j 2.0.2.

Neo4j 2.0.2 does not require any store-level upgrades from the previous 2.0.1 release.

Where in the Documentation Can I Learn More about Upgrades?

The Upgrade section of the Neo4j documentation can be found here, and also covers upgrades to 2.0.

The upgrade basically happens by starting your Neo4j data store (after making the backup) with Neo4j 2.0 and the configuration allow_store_upgrade=true enabled in the configuration file conf/neo4j.properties.

To avoid running into server startup issues as part of the upgrade, you can also use the neo4j-shell for that purpose. The command line call would then be:

bin/neo4j-shell -path data/graph.db -config conf/neo4j.properties.

Information On Upgrading From Neo4j 1.9

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 review the CHANGES.TXT file contained within the distribution.

For release notes for each version of Neo4j, head over to our release notes page at http://www.neo4j.org/release-notes
On behalf of the Neo4j team,
Kenny Bastani

Download Building Reactive Microservices in Java: Asynchronous and Event-Based Application Design. Brought to you in partnership with Red Hat


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}