Release Date: 11 May 2017
We are very excited to introduce our landmark new release – Neo4j 3.2. We encourage everyone to try out all the new features. Neo4j 3.2 marks an expansion in global scale, performance and refinement. It signals that the next generation of graph-powered internet applications, generating personalized content or finding coordinated malfeasance, will span the globe.
- Enterprise Scale for Global Internet Applications
- Multi-Data Center Support, supporting globally distributed web and SaaS applications, spanning data centers and continents
- Enterprise Governance
- An add-on security module enabling Kerberos-based authentication
- A new schema constraint, Node Keys, enforces data quality rules that require uniqueness and existence within one or more node properties
dbms.listQueries()displays per-query resource statistics and lock wait times
- Performance Throughout the Native Graph Stack
- Initial version of a compiled Cypher runtime, improve speeds by ~300% for a subset of basic queries
- Native Label Indexes, replacing the previous Lucene-based equivalent, improves write speeds by 30% to 250% while maintaining fast label lookups
- New composite Indexes, improve performance and overall efficiency for schema indexes with more than one property
- Cypher’s Cost-based query optimizer now fully replaces the rule-based optimizer
- A new Cypher editor for the Neo4j Browser, introducing syntax highlighting and autocompletion
Detailed Changes and DocsFor the complete list of all changes, please see the changelog. Look for 3.2 Developer manual here, and 3.2 Operations manual here.
UpgradingWhen upgrading to Neo4j 3.2 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.2 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.2.
Known IssuesNeo4j Browser has been substantially rewritten, providing substantial improvements but also some regrettable regressions. Notably:
- Neo4j Browser 3.2 only supports the
boltprotocol. Support for
httpswill be restored in an upcoming patch release.
- Guides only support static content. Guides which rely on
angular.jscontrollers (such as the “Query Template”) will not work in Neo4j 3.2. We’re working on fresh capabilities for guides to allow dynamic features through an official public API. Stay tuned.