Deprecations, additions and compatibility

This section list all of the features that have been removed, deprecated, added, or extended in different Cypher^® versions. Replacement syntax for deprecated and removed features are also indicated.

Version 4.0

Removed features

Feature Details

Feature	Details
Function Removed `rels()`	Replaced by relationships().
Function Removed `toInt()`	Replaced by toInteger().
Function Removed `lower()`	Replaced by toLower().
Function Removed `upper()`	Replaced by toUpper().
Function Removed `extract()`	Replaced by list comprehension.
Function Removed `filter()`	Replaced by list comprehension.
Functionality Removed For Rule planner: `CYPHER planner=rule`	The `RULE` planner was removed in 3.2, but still possible to trigger using `START` or `CREATE UNIQUE` clauses. Now it is completely removed.
Functionality Removed Explicit indexes	The removal of the `RULE` planner in 3.2 was the beginning of the end for explicit indexes. Now they are completely removed, including the removal of the built-in procedures for Neo4j 3.3 to 3.5.
Functionality Removed For compiled runtime: `CYPHER runtime=compiled`	Replaced by the new `pipelined` runtime which covers a much wider range of queries.
Clause Removed `CREATE UNIQUE`	Running queries with this clause will cause a syntax error. Running with `CYPHER 3.5` will cause a runtime error due to the removal of the rule planner.
Clause Removed `START`	Running queries with this clause will cause a syntax error. Running with `CYPHER 3.5` will cause a runtime error due to the removal of the rule planner.
Syntax Removed `MATCH (n)-[:A\|:B\|:C {foo: 'bar'}]-() RETURN n`	Replaced by `MATCH (n)-[:A\|B\|C {foo: 'bar'}]-() RETURN n`.
Syntax Removed `MATCH (n)-[x:A\|:B\|:C]-() RETURN n`	Replaced by `MATCH (n)-[x:A\|B\|C]-() RETURN n`.
Syntax Removed `MATCH (n)-[x:A\|:B\|:C*]-() RETURN n`	Replaced by `MATCH (n)-[x:A\|B\|C*]-() RETURN n`.
Syntax Removed `{parameter}`	Replaced by $parameter.

Function Removed

rels()

Replaced by relationships().

Function Removed

toInt()

Replaced by toInteger().

Function Removed

lower()

Replaced by toLower().

Function Removed

upper()

Replaced by toUpper().

Function Removed

extract()

Replaced by list comprehension.

Function Removed

filter()

Replaced by list comprehension.

Functionality Removed
For Rule planner:

CYPHER planner=rule

The RULE planner was removed in 3.2, but still possible to trigger using START or CREATE UNIQUE clauses. Now it is completely removed.

Functionality Removed
Explicit indexes

The removal of the RULE planner in 3.2 was the beginning of the end for explicit indexes. Now they are completely removed, including the removal of the built-in procedures for Neo4j 3.3 to 3.5.

Functionality Removed
For compiled runtime:

CYPHER runtime=compiled

Replaced by the new pipelined runtime which covers a much wider range of queries.

Clause Removed

CREATE UNIQUE

Running queries with this clause will cause a syntax error. Running with CYPHER 3.5 will cause a runtime error due to the removal of the rule planner.

Clause Removed

START

Running queries with this clause will cause a syntax error. Running with CYPHER 3.5 will cause a runtime error due to the removal of the rule planner.

Syntax Removed

MATCH (n)-[:A|:B|:C {foo: 'bar'}]-() RETURN n

Replaced by MATCH (n)-[:A|B|C {foo: 'bar'}]-() RETURN n.

Syntax Removed

MATCH (n)-[x:A|:B|:C]-() RETURN n

Replaced by MATCH (n)-[x:A|B|C]-() RETURN n.

Syntax Removed

MATCH (n)-[x:A|:B|:C*]-() RETURN n

Replaced by MATCH (n)-[x:A|B|C*]-() RETURN n.

Syntax Removed

{parameter}

Replaced by $parameter.

Deprecated features

Feature Details

Feature	Details
Syntax Deprecated `MATCH (n)-[rs*]-() RETURN rs`	As in Cypher 3.2, this is replaced by: `MATCH p=(n)-[*]-() RETURN relationships(p) AS rs`
Syntax Deprecated `CREATE INDEX ON :Label(prop)`	Replaced by `CREATE INDEX FOR (n:Label) ON (n.prop)`.
Syntax Deprecated `DROP INDEX ON :Label(prop)`	Replaced by `DROP INDEX name`.
Syntax Deprecated `DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS NODE KEY`	Replaced by `DROP CONSTRAINT name`.
Syntax Deprecated `DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS UNIQUE`	Replaced by `DROP CONSTRAINT name`.
Syntax Deprecated `DROP CONSTRAINT ON (n:Label) ASSERT exists(n.prop)`	Replaced by `DROP CONSTRAINT name`.
Syntax Deprecated `DROP CONSTRAINT ON ()-[r:Type]-() ASSERT exists(r.prop)`	Replaced by `DROP CONSTRAINT name`.

Syntax Deprecated

MATCH (n)-[rs*]-() RETURN rs

As in Cypher 3.2, this is replaced by:

MATCH p=(n)-[*]-() RETURN relationships(p) AS rs

Syntax Deprecated

CREATE INDEX ON :Label(prop)

Replaced by CREATE INDEX FOR (n:Label) ON (n.prop).

Syntax Deprecated

DROP INDEX ON :Label(prop)

Replaced by DROP INDEX name.

Syntax Deprecated

DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS NODE KEY

Replaced by DROP CONSTRAINT name.

Syntax Deprecated

DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS UNIQUE

Replaced by DROP CONSTRAINT name.

Syntax Deprecated

DROP CONSTRAINT ON (n:Label) ASSERT exists(n.prop)

Replaced by DROP CONSTRAINT name.

Syntax Deprecated

DROP CONSTRAINT ON ()-[r:Type]-() ASSERT exists(r.prop)

Replaced by DROP CONSTRAINT name.

Restricted features

Feature Details

Feature	Details
Function Restricted `length()`	Restricted to only work on paths. See length() for more details.
Function Restricted `size()`	No longer works for paths. Only works for strings, lists and pattern expressions. See size() for more details.

Function Restricted

length()

Restricted to only work on paths. See length() for more details.

Function Restricted

size()

No longer works for paths. Only works for strings, lists and pattern expressions. See size() for more details.

Updated features

Feature Details

Feature	Details
Syntax Extended `CREATE CONSTRAINT [name] ON ...`	The create constraint syntax can now include a name.

Syntax Extended

CREATE CONSTRAINT [name] ON ...

The create constraint syntax can now include a name.

New features

Feature Details

Feature	Details
Functionality New Pipelined runtime: `CYPHER runtime=pipelined`	This Neo4j Enterprise Edition only feature involves a new runtime that has many performance enhancements.
Functionality New Multi-database administration	New Cypher commands for administering multiple databases.
Functionality New Security administration	New Cypher commands for administering role-based access-control.
Functionality New Fine-grained security	New Cypher commands for administering dbms, database, graph and sub-graph access control.
Syntax New `CREATE INDEX [name] FOR (n:Label) ON (n.prop)`	New syntax for creating indexes, which can include a name.
Syntax New `DROP INDEX name`	New command for dropping an index by name.
Syntax New `DROP CONSTRAINT name`	New command for dropping a constraint by name, no matter the type.
Clause New `WHERE EXISTS {...}`	Existential sub-queries are sub-clauses used to filter the results of a `MATCH`, `OPTIONAL MATCH`, or `WITH` clause.
Clause New `USE neo4j`	New clause to specify which graph a query, or query part, is executed against.

Functionality New
Pipelined runtime:

CYPHER runtime=pipelined

This Neo4j Enterprise Edition only feature involves a new runtime that has many performance enhancements.

Functionality New
Multi-database administration

New Cypher commands for administering multiple databases.

Functionality New
Security administration

New Cypher commands for administering role-based access-control.

Functionality New
Fine-grained security

New Cypher commands for administering dbms, database, graph and sub-graph access control.

Syntax New

CREATE INDEX [name] FOR (n:Label) ON (n.prop)

New syntax for creating indexes, which can include a name.

Syntax New

DROP INDEX name

New command for dropping an index by name.

Syntax New

DROP CONSTRAINT name

New command for dropping a constraint by name, no matter the type.

Clause New

WHERE EXISTS {...}

Existential sub-queries are sub-clauses used to filter the results of a MATCH, OPTIONAL MATCH, or WITH clause.

Clause New

USE neo4j

New clause to specify which graph a query, or query part, is executed against.

Version 3.5

Deprecated features

Feature Details

Feature	Details
Functionality Deprecated Compiled runtime: `CYPHER runtime=compiled`	The compiled runtime will be discontinued in the next major release. It might still be used for default queries in order to not cause regressions, but explicitly requesting it will not be possible.
Function Deprecated `extract()`	Replaced by list comprehension.
Function Deprecated `filter()`	Replaced by list comprehension.

Functionality Deprecated
Compiled runtime:

CYPHER runtime=compiled

The compiled runtime will be discontinued in the next major release. It might still be used for default queries in order to not cause regressions, but explicitly requesting it will not be possible.

Function Deprecated

extract()

Replaced by list comprehension.

Function Deprecated

filter()

Replaced by list comprehension.

Version 3.4

Feature	Type	Change	Details
Spatial point types	Functionality	Amendment	A point — irrespective of which Coordinate Reference System is used — can be stored as a property and is able to be backed by an index. Prior to this, a point was a virtual property only.
point() - Cartesian 3D	Function	Added
point() - WGS 84 3D	Function	Added
randomUUID()	Function	Added
Temporal types	Functionality	Added	Supports storing, indexing and working with the following temporal types: Date, Time, LocalTime, DateTime, LocalDateTime and Duration.
Temporal functions	Functionality	Added	Functions allowing for the creation and manipulation of values for each temporal type — Date, Time, LocalTime, DateTime, LocalDateTime and Duration.
Temporal operators	Functionality	Added	Operators allowing for the manipulation of values for each temporal type — Date, Time, LocalTime, DateTime, LocalDateTime and Duration.
toString()	Function	Extended	Now also allows temporal values as input (i.e. values of type Date, Time, LocalTime, DateTime, LocalDateTime or Duration).

Feature

Type

Change

Details

Spatial point types

Functionality

Amendment

A point — irrespective of which Coordinate Reference System is used — can be stored as a property and is able to be backed by an index. Prior to this, a point was a virtual property only.

point() - Cartesian 3D

Function

Added

point() - WGS 84 3D

Function

Added

randomUUID()

Function

Added

Temporal types

Functionality

Added

Supports storing, indexing and working with the following temporal types: Date, Time, LocalTime, DateTime, LocalDateTime and Duration.

Temporal functions

Functionality

Added

Functions allowing for the creation and manipulation of values for each temporal type — Date, Time, LocalTime, DateTime, LocalDateTime and Duration.

Temporal operators

Functionality

Added

Operators allowing for the manipulation of values for each temporal type — Date, Time, LocalTime, DateTime, LocalDateTime and Duration.

toString()

Function

Extended

Now also allows temporal values as input (i.e. values of type Date, Time, LocalTime, DateTime, LocalDateTime or Duration).

Version 3.3

Feature Type Change Details

Feature	Type	Change	Details
`START`	Clause	Removed	As in Cypher 3.2, any queries using the `START` clause will revert back to Cypher 3.1 `planner=rule`. However, there are built-in procedures for Neo4j versions 3.3 to 3.5 for accessing explicit indexes. The procedures will enable users to use the current version of Cypher and the cost planner together with these indexes. An example of this is `CALL db.index.explicit.searchNodes('my_index','email:me*')`.
`CYPHER runtime=slotted` (Faster interpreted runtime)	Functionality	Added	Neo4j Enterprise Edition only
max(), min()	Function	Extended	Now also supports aggregation over sets containing lists of strings and/or numbers, as well as over sets containing strings, numbers, and lists of strings and/or numbers

START

Clause

Removed

As in Cypher 3.2, any queries using the START clause will revert back to Cypher 3.1 planner=rule. However, there are built-in procedures for Neo4j versions 3.3 to 3.5 for accessing explicit indexes. The procedures will enable users to use the current version of Cypher and the cost planner together with these indexes. An example of this is CALL db.index.explicit.searchNodes('my_index','email:me*').

CYPHER runtime=slotted (Faster interpreted runtime)

Functionality

Added

Neo4j Enterprise Edition only

max(), min()

Function

Extended

Now also supports aggregation over sets containing lists of strings and/or numbers, as well as over sets containing strings, numbers, and lists of strings and/or numbers

Version 3.2

Feature Type Change Details

Feature	Type	Change	Details
`CYPHER planner=rule` (Rule planner)	Functionality	Removed	All queries now use the cost planner. Any query prepended thus will fall back to using Cypher 3.1.
`CREATE UNIQUE`	Clause	Removed	Running such queries will fall back to using Cypher 3.1 (and use the rule planner)
`START`	Clause	Removed	Running such queries will fall back to using Cypher 3.1 (and use the rule planner)
`MATCH (n)-[rs*]-() RETURN rs`	Syntax	Deprecated	Replaced by `MATCH p=(n)-[*]-() RETURN relationships(p) AS rs`
`MATCH (n)-[:A\|:B\|:C {foo: 'bar'}]-() RETURN n`	Syntax	Deprecated	Replaced by `MATCH (n)-[:A\|B\|C {foo: 'bar'}]-() RETURN n`
`MATCH (n)-[x:A\|:B\|:C]-() RETURN n`	Syntax	Deprecated	Replaced by `MATCH (n)-[x:A\|B\|C]-() RETURN n`
`MATCH (n)-[x:A\|:B\|:C*]-() RETURN n`	Syntax	Deprecated	Replaced by `MATCH (n)-[x:A\|B\|C*]-() RETURN n`
User-defined aggregation functions	Functionality	Added
Composite indexes	Index	Added
Node Key	Index	Added	Neo4j Enterprise Edition only
`CYPHER runtime=compiled` (Compiled runtime)	Functionality	Added	Neo4j Enterprise Edition only
reverse()	Function	Extended	Now also allows a list as input
max(), min()	Function	Extended	Now also supports aggregation over a set containing both strings and numbers

CYPHER planner=rule (Rule planner)

Functionality

Removed

All queries now use the cost planner. Any query prepended thus will fall back to using Cypher 3.1.

CREATE UNIQUE

Clause

Removed

Running such queries will fall back to using Cypher 3.1 (and use the rule planner)

START

Clause

Removed

Running such queries will fall back to using Cypher 3.1 (and use the rule planner)

MATCH (n)-[rs*]-() RETURN rs

Syntax

Deprecated

Replaced by MATCH p=(n)-[*]-() RETURN relationships(p) AS rs

MATCH (n)-[:A|:B|:C {foo: 'bar'}]-() RETURN n

Syntax

Deprecated

Replaced by MATCH (n)-[:A|B|C {foo: 'bar'}]-() RETURN n

MATCH (n)-[x:A|:B|:C]-() RETURN n

Syntax

Deprecated

Replaced by MATCH (n)-[x:A|B|C]-() RETURN n

MATCH (n)-[x:A|:B|:C*]-() RETURN n

Syntax

Deprecated

Replaced by MATCH (n)-[x:A|B|C*]-() RETURN n

User-defined aggregation functions

Functionality

Added

Composite indexes

Index

Added

Node Key

Index

Added

Neo4j Enterprise Edition only

CYPHER runtime=compiled (Compiled runtime)

Functionality

Added

Neo4j Enterprise Edition only

reverse()

Function

Extended

Now also allows a list as input

max(), min()

Function

Extended

Now also supports aggregation over a set containing both strings and numbers

Version 3.1

Feature Type Change Details

Feature	Type	Change	Details
`rels()`	Function	Deprecated	Replaced by relationships()
`toInt()`	Function	Deprecated	Replaced by toInteger()
`lower()`	Function	Deprecated	Replaced by toLower()
`upper()`	Function	Deprecated	Replaced by toUpper()
toBoolean()	Function	Added
Map projection	Syntax	Added
Pattern comprehension	Syntax	Added
User-defined functions	Functionality	Added
CALL...YIELD...WHERE	Clause	Extended	Records returned by `YIELD` may be filtered further using `WHERE`

rels()

Function

Deprecated

Replaced by relationships()

toInt()

Function

Deprecated

Replaced by toInteger()

lower()

Function

Deprecated

Replaced by toLower()

upper()

Function

Deprecated

Replaced by toUpper()

toBoolean()

Function

Added

Map projection

Syntax

Added

Pattern comprehension

Syntax

Added

User-defined functions

Functionality

Added

CALL...YIELD...WHERE

Clause

Extended

Records returned by YIELD may be filtered further using WHERE

Version 3.0

Feature Type Change Details

Feature	Type	Change	Details
`has()`	Function	Removed	Replaced by exists()
`str()`	Function	Removed	Replaced by toString()
`{parameter}`	Syntax	Deprecated	Replaced by $parameter
properties()	Function	Added
CALL [...YIELD]	Clause	Added
point() - Cartesian 2D	Function	Added
point() - WGS 84 2D	Function	Added
distance()	Function	Added
User-defined procedures	Functionality	Added
toString()	Function	Extended	Now also allows Boolean values as input

has()

Function

Removed

Replaced by exists()

str()

Function

Removed

Replaced by toString()

{parameter}

Syntax

Deprecated

Replaced by $parameter

properties()

Function

Added

CALL [...YIELD]

Clause

Added

point() - Cartesian 2D

Function

Added

point() - WGS 84 2D

Function

Added

distance()

Function

Added

User-defined procedures

Functionality

Added

toString()

Function

Extended

Now also allows Boolean values as input

Compatibility

The ability of Neo4j to support multiple older versions of the Cypher language has been changing. In versions of Neo4j before 3.5 the backwards compatibility layer included the Cypher language parser, planner and runtime. All supported versions of Cypher would run on the same Neo4j kernel. In Neo4j 3.4, however, this was changed such that the compatibility layer no longer included the runtime. This meant that running, for example, a CYPHER 3.1 query inside Neo4j 3.5 would plan the query using the 3.1 planner, and run it using the 3.5 runtime and kernel. In Neo4j 4.0 this was changed again, such that the compatibility layer includes only the parser. For example, running a CYPHER 3.5 query inside Neo4j will parse older language features, but plan using the 4.0 planner, and run using the 4.0 runtime and kernel. The primary reason for this change has been optimizations in the Cypher runtime to allow Cypher query to perform better.

Older versions of the language can still be accessed if required. There are two ways to select which version to use in queries.

Setting a version for all queries: You can configure your database with the configuration parameter cypher.default_language_version, and enter which version you’d like to use (see Supported language versions). Every Cypher query will use this version, provided the query hasn’t explicitly been configured as described in the next item below.
Setting a version on a query by query basis: The other method is to set the version for a particular query. Prepending a query with CYPHER 3.5 will execute the query with the version of Cypher included in Neo4j 3.5.

Below is an example using the older parameter syntax {param}:

CYPHER 3.5
MATCH (n:Person)
WHERE n.age > {agelimit}
RETURN n.name, n.age

Without the CYPHER 3.5 prefix this query would fail with a syntax error. With CYPHER 3.5 however, it will only generate a warning and still work.

In Neo4j 4.0 some older language features are understood by the Cypher parser even if they are no longer supported by the Neo4j kernel. These features will result in runtime errors. See the table at Cypher Version 4.0 for the list of affected features.

Supported language versions

Neo4j 4.0 supports the following versions of the Cypher language:

Neo4j Cypher 3.5
Neo4j Cypher 4.0

Each release of Neo4j supports a limited number of old Cypher Language Versions. When you upgrade to a new release of Neo4j, please make sure that it supports the Cypher language version you need. If not, you may need to modify your queries to work with a newer Cypher language version.