Neo4j Versions Save

Graphs for Everyone

3.3.0-beta01

6 years ago

Release Date: 09/14/2017

Neo4j 3.3.0-beta01 is the first beta release of the upcoming Neo4j 3.3.

Highlights

Fusion index default for new indexes
Introducing procedures for manual indexes
Driver upgrade and small improvements to Neo4j Browser
Detailed Changes and Docs

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

Look for 3.3 Developer manual here, and 3.3 Operations manual here.

Using pre-GA early access releases

Pre-GA releases of Neo4j are provided under our User Experience Improvement Program (UXIP), intended for evaluation purposes only. Use of this release implies acceptance of the UXIP terms, which include allowing passive reporting about usage. Of course, we would also love to hear active feedback about your experience.

3.2.0-alpha08

7 years ago

Kernel

Overwriting property with same value no longer generates write command #9056
More scalable index logging #9063
Allow skip bad entries logging during import #9103

Cypher

Improved cypher execution speed on variable length queries where only the distinct pairs of start and end node are of interest. One query to benefit would be MATCH (a)-[*4..5]->(b) RETURN DISTINCT a, b. #9062
Allow more granular configuration of literals extraction #9093
It is no longer possible to CREATE or DROP composite uniqueness constraints. To enforce composite uniqueness, we refer to the new NODE KEY constraint. #9135
Use getDegree instead of expansion #9139
Correct query type for procedures #9143
Handle Ands with single value #9149
Predicates on shortest path and optional match #9156

Packaging

Removed neo4j-shared.sh. Functionality is now included in all wrapper scripts directly #9083

Security

Added new role Editor that is allowed to read and write data but not allowed to create new tokens. #9081

Causal Clustering

Improve transaction streaming #9070

Tools

Added --version argument to neo4j-admin and neo4j commands #9102
Renamed neo4j-admin version to neo4j-admin store-info #9126

Misc

Show allocated memory and page hits/faults in dbms.listQueries #9037
Neo4j now exits with code 0 for SIGINT and SIGTERM #9108
- systemd will no longer report neo4j as failed after you do systemctl stop neo4j.
- Hitting Ctrl-C when running neo4j console will no longer exit with error if shutdown was performed gracefully.

3.1.0

7 years ago

We are very excited to introduce our landmark new release – Neo4j 3.1. We encourage everyone to download 3.1.0 and try out all the new features from here.

Neo4j 3.1 adds a new state-of-the-art clustering architecture and new security architecture to meet enterprise requirements for scale and security. This new release extends the comprehensive set of graph functionality for which Neo4j is best known and builds upon the new Official Language Drivers introduced in Neo4j 3.0.

Highlights

New Clustering Technology based on state-of-the-art RAFT protocol:

Cluster-aware stack with built-in load balancing
Causal consistency enabling applications to decide on cost/consistency tradeoff at query time

New Security Foundation ensuring that authenticated users and applications can perform only authorized actions on data graph stored in Neo4j:

Role-Based Access Control for built-in native and federated users (via LDAP connector)
Sub-graph authorization via User-Defined Procedures
Query listing and termination using :queries command in Neo4j Browser
Security event logging

Database Kernel and Operations Advances:

New execution guard to terminate long-running, end-user queries
Ability to reallocate space from deleted records while the cluster is online
New command line tools: cypher-shell and improved neo4j-admin

Schema Viewer: Displays the graph model at the current point in time
IBM Power8 CAPI Flash Support: Enables ultra-large in-memory graphs

Detailed Changes

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

Upgrading

When upgrading to Neo4j 3.1 for the first time, be sure to read the current upgrade instructions in the Neo4j Operations Manual, as there are additional steps and considerations.

Neo4j 3.1 supports direct upgrades from all 2.x releases (recommended to be on latest patch). Pre-2.x users need to upgrade to 2.x before upgrading to 3.1.

3.1.0-M12-beta2

7 years ago

This is the second preview of the upcoming Neo4j 3.1 release. We encourage everyone to download 3.1.0-BETA2 and try out all the new features .

Highlights

Neo4j 3.1 has been feature complete since Beta 1. Thanks to your feedback, beta 2 includes bug fixes and refinements, but no significant changes or additions.

Detailed Changes

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

Upgrading

When upgrading to Neo4j 3.1 for the first time, be sure to read the current upgrade instructions in the Neo4j Operations Manual, as there are additional steps and considerations.

Neo4j 3.1 supports direct upgrades from all 2.x releases (recommended to be on latest patch). Pre-2.x users need to upgrade to 2.x before upgrading to 3.1.

3.1.0-M09

7 years ago

Release Date: 09/16/2016

Neo4j 3.1.0-M09 is a beta release offering early access to features which are under active development.

Highlights

(Enterprise Ed.) Security:

Introduce custom caching for authorization and authentication info
Expose cache expiration setting in neo4j.conf Support the ability for client applications to specify which authorizing realm to use when logging in #7877

Other:

Introduced neo4j-admin dump and load commands. This can be used for offline backup or moving databases from one Neo4j instance to another.
Introduced user-defined functions
Introduced procedure dbms.functions which lists all functions
Introduced procedures db.resampleIndex(index) and db.resampleOutdatedIndexes() to schedule resampling of indexes. A specific index is specified with a string in the form :<label>(<property>) (for example db.awaitIndex(":Person(name)"), instead of by passing label and property as separate parameters

Detailed Changes and Docs

For the complete list of all changes, please see the changelog.
Look for Beta docs here

Using a Milestone

Milestone releases of Neo4j are provided under our User Experience Improvement Program (UXIP), intended for evaluation purposes only. Use of a milestone implies acceptance of the UXIP terms, which include allowing passive reporting about usage. Of course, we would also love to hear active feedback about your experience.

As beta software, milestones are not appropriate for production use. There is no supported upgrade path, and the features and APIs may change before being finalized (hopefully reflecting your feedback).

2.3.7

7 years ago

Release Date: 08/31/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.)

3.1.0-M10

7 years ago

Release Date: 10/04/2016

Neo4j 3.1.0-M10 is a beta release offering early access to features which are under active development.

Highlights

Security (Enterprise Edition)

All security related events are now logged to the new security.log file
Introduced support custom security plugins for authentication and authorization
Automatically reload auth files from disk every 5 seconds to enable external changes and externally driven cluster synchronisation
Added procedures for killing queries

Kernel (Enterprise Edition)

Enhance high limit record format allowing for many more relationship types than before. This requires setting dbms.allow_format_migration=true config for stores using this format

Cypher

User Defined Functions and procedure for listing them
Several Bugfixes around IN and slices and type-checking

Other

Check-consistency, neo4j-backup and import csv tools now can be invoked from neo4j-admin script. The previous method of calling above tools will be deprecated
Debian packages now provide upgrade instructions when upgrading from 2.x to 3.x

Detailed Changes and Docs

For the complete list of all changes, please see the changelog.
Look for Beta docs here

Using a Milestone

3.0.6

7 years ago

Release Date: 09/16/2016

Neo4j 3.0.6 is a maintenance release, with important improvements.

Highlights

Several improvements to Debian packaging in upgrading from 2.x and 3.x
(Enterprise only) Bumps store version in high-limit format. Requires setting dbms.allow_format_migration=true if using previous version high-limit format store
Update ha component lifecycle to make sure we have only one active update puller on slaves. Fixes problem introduced in 3.0.5

Detailed Changes

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

Upgrading

Note:Upgrading to this version of Neo4j may change the internal ids of relationships, which can invalidate any manually maintained relationship references whether in an external system or stored within Neo4j as a property value. Plan to verify and recreate any such storage after the upgrade.

Please read the upgrading section of the Neo4j Operations Manual for details.

3.1.0-BETA1

7 years ago

Release Date: 10/13/2016

We are very excited to introduce a preview of our landmark new release – Neo4j 3.1 – coming out soon. We encourage everyone to download 3.1.0-BETA1 and try out all the new features from here.

Neo4j 3.1 adds a new state-of-the-art clustering architecture and new security architecture to meet enterprise requirements for scale and security. This new release extends the comprehensive set of graph functionality for which Neo4j is best known and builds upon the new Official Language Drivers introduced in Neo4j 3.0.

Highlights

New Clustering Technology based on state-of-the-art RAFT protocol:

Cluster-aware stack with built-in load balancing
Casual consistency enabling applications to decide on cost/consistency tradeoff at query time

New Security Foundation ensuring that authenticated users and applications can perform only authorized actions on data graph stored in Neo4j:

Role-Based Access Control for built-in native and federated users (via LDAP connector)
Sub-graph authorization via User-Defined Procedures
Query listing and termination using :qs command in Neo4j Browser (to be renamed to :queries)
Security event logging

Database Kernel and Operations Advances:

New execution guard to terminate long-running, end-user queries
Ability to reallocate space from deleted records while the cluster is online
New command line tools: cypher-shell and improved neo4j-admin

Schema Viewer: Displays the graph model at the current point in time
IBM Power8 CAPI Flash Support: Enables ultra-large in-memory graphs

Detailed Changes

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

Upgrading

When upgrading to Neo4j 3.1 for the first time, be sure to read the current upgrade instructions in the Neo4j Operations Manual, as there are additional steps and considerations.

Neo4j 3.1 supports direct upgrades from all 2.x releases (recommended to be on latest patch). Pre-2.x users need to upgrade to 2.x before upgrading to 3.1.

3.0.0-RC1

8 years ago

Neo4j 3.0.0-RC1 is a release candidate offering early access to features which are under active development.

Highlights

Mixed use of CALL within Cypher statements.
Revised namespace for some built-in Procedures.
Neo4j Browser now includes Neo4j Sync, a companion cloud service for saving scripts and graph style sheets
Significant modifications to configuration settings
All logging is more uniform in format and configuration.
Windows command-line and Powershell API have been simplified, introducing some incompatibility with previous versions.

Detailed Changes

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

Using a Release Candidate

Release candidates are like Milestone releases of Neo4j, which are provided under our User Experience Improvement Program (UXIP), intended for evaluation purposes only. Use of a release candidate implies acceptance of the UXIP terms, which include allowing passive reporting about usage. Of course, we would also love to hear active feedback about your experience.

As beta software, release candidates are not appropriate for production use. There is no supported upgrade path, and while the features and APIs have been finalized, changes may still occur to correct errors (hopefully reflecting your feedback).

Download

You can download Neo4j 3.0-RC1 or use one of the other distribution mechanism (debian package, homebrew etc). Please check out our Blog post with more details and also links to the most recent binary protocol drivers.

Feedback, please!

Use this release candidate to help us test Neo4j thoroughly so that we can provide an amazing and stable release. We’d love to hear from you on our public Slack or via e-mail: [email protected].