openCypher specification compliance in Amazon Neptune

• MATCH   –   Supported, except that shortestPath() and allShortestPaths() are not currently supported.

• OPTIONAL MATCH

• MANDATORY MATCH   –   is not currently supported in Neptune. Neptune does, however, support custom ID values in MATCH queries.

• RETURN   –   Supported, except when used with non-static values for SKIP or LIMIT. For example, the following currently does not work:

  MATCH (n)
  RETURN n LIMIT toInteger(rand())    // Does NOT work!

• WITH   –   Supported, except when used with non-static values for SKIP or LIMIT. For example, the following currently does not work:

  MATCH (n)
  WITH n SKIP toInteger(rand())
  WITH count() AS count
  RETURN count > 0 AS nonEmpty    // Does NOT work!

• UNWIND

• WHERE

• ORDER BY

• SKIP

• LIMIT

• CREATE   –   Neptune lets you create custom ID values in CREATE queries.

• DELETE

• SET

• REMOVE

• MERGE   –   Neptune supports custom ID values in MERGE queries.

• CALL[YIELD...]   –   is not currently supported in Neptune.

• UNION, UNION ALL   –   read-only queries are supported, but mutation queries are not currently supported.

• USING   –   USING is supported from engine version 1.3.2.0. See Query hints for more information.

General operators

• DISTINCT

• The . operator for accessing properties of a nested literal map.

Mathematical operators

• The + addition operator.

• The - subtraction operator.

• The * multiplication operator.

• The / division operator.

• The % modulo division operator.

• The ^ exponentiation operator is NOT supported.

Comparison operators

• The = addition operator.

• The <> inequality operator.

• The < less-than operator is supported except when either of the arguments is a Path, List, or Map.

• The > greater-than operator is supported except when either of the arguments is a Path, List, or Map.

• The <= less-than-or-equal-to operator is supported except when either of the arguments is a Path, List, or Map.

• The >= greater-than-or-equal-to operator is supported except when either of the arguments is a Path, List, or Map.

• IS NULL

• IS NOT NULL

• STARTS WITH is supported if the data being searched for is a string.

• ENDS WITH is supported if the data being searched for is a string.

• CONTAINS is supported if the data being searched for is a string.

Boolean operators

• AND

• OR

• XOR

• NOT

String operators

• The + concatenation operator.

List operators

• The + concatenation operator.

• IN (checks for the presence of an item in the list)

• CASE

• The [] expression is is not currently supported in Neptune for accessing dynamically computed property keys within a node, relationship, or map. For example, the following does not work:

  MATCH (n)
  WITH [5, n, {key: 'value'}] AS list
  RETURN list[1].name

Predicate functions

• exists()

Scalar functions

• coalesce()

• endNode()

• epochmillis()

• head()

• id()

• last()

• length()

• randomUUID()

• properties()

• removeKeyFromMap

• size()   –   this overloaded method currently only works for pattern expressions, lists, and strings

• startNode()

• timestamp()

• toBoolean()

• toFloat()

• toInteger()

• type()

Aggregating functions

• avg()

• collect()

• count()

• max()

• min()

• percentileDisc()

• stDev()

• percentileCont()

• stDevP()

• sum()

List functions

• join() (concatenates strings in a list into a single string)

• keys()

• labels()

• nodes()

• range()

• relationships()

• reverse()

• tail()

Mathematical functions – numeric

• abs()

• ceil()

• floor()

• rand()

• round()

• sign()

Mathematical functions – logarithmic

• e()

• exp()

• log()

• log10()

• sqrt()

Mathematical functions – trigonometric

• acos()

• asin()

• atan()

• atan2()

• cos()

• cot()

• degrees()

• pi()

• radians()

• sin()

• tan()

String functions

• join() (concatenates strings in a list into a single string)

• left()

• lTrim()

• replace()

• reverse()

• right()

• rTrim()

• split()

• substring()

• toLower()

• toString()

• toUpper()

• trim()

Supported date formats

• yyyy-MM-dd

• yyyyMMdd

• yyyy-MM

• yyyy-DDD

• yyyyDDD

• yyyy

Supported time formats

• HH:mm:ssZ

• HHmmssZ

• HH:mm:ssZ

• HH:mmZ

• HHmmZ

• HHZ

• HHmmss

• HH:mm:ss

• HH:mm

• HHmm

• HH

• Support for milliseconds. Datetime literal will always be returned with milliseconds, even if milliseconds is 0. (Previous behavior was to truncate milliseconds.)

  CREATE (:event {time: datetime('2024-04-01T23:59:59Z')})
  
  # Returning the date returns with 000 suffixed representing milliseconds
  MATCH(n:event)
  RETURN n.time as datetime
  
  {
    "results" : [ {
      "n" : {
        "~id" : "0fe88f7f-a9d9-470a-bbf2-fd6dd5bf1a7d",
        "~entityType" : "node",
        "~labels" : [ "event" ],
        "~properties" : {
          "time" : "2024-04-01T23:59:59.000Z"
        }
      }
    } ]
  }

• Support for calling the datetime() function over stored properties or intermediate results. For example, the following queries were not possible prior to this feature.

  Datetime() over properties:

  // Create node with property 'time' stored as string
  CREATE (:event {time: '2024-04-01T23:59:59Z'})
  
  // Match and return this property as datetime
  MATCH(n:event)
  RETURN datetime(n.time) as datetime

  Datetime() over intermediate results:

  // Parse datetime from parameter
  UNWIND $list as myDate
  RETURN datetime(myDate) as d

• It is now also possible to save datetime perperties that are created the in cases mentioned above.

  Saving datetime from the string property of one property to another:

  // Create node with property 'time' stored as string
  CREATE (:event {time: '2024-04-01T23:59:59Z', name: 'crash'})
  
  // Match and update the same property to datetime type
  MATCH(n:event {name: 'crash'})
  SET n.time = datetime(n.time)
  
  // Match and update another node's property
  MATCH(e:event {name: 'crash'})
  MATCH(n:server {name: e.servername})
  SET n.time = datetime(e.time)

  Batch create nodes from a parameter with a datetime property:

  // Batch create from parameter
  UNWIND $list as events
  CREATE (n:crash) {time: datetime(events.time)}
  // Parameter value
  {
    "x":[
      {"time":"2024-01-01T23:59:29", "name":"crash1"},
      {"time":"2023-01-01T00:00:00Z", "name":"crash2"}
    ]
  }

• Support for a larger subset of ISO8601 datetime formats. See below.

• +/-HH:mm

• +/-HHmm

• +/-HH

• yyyy-MM-dd

• yyyyMMdd

• yyyy-MM

• yyyyMM

• yyyy-DDD

• yyyyDDD

• yyyy

• yyyy-MM-dd

• yyyy-DDD

• yyyyDDD

• HH:mm:ss.SSS

• HH:mm:ss

• HHmmss.SSS

• HHmmss

• HH:mm

• HHmm

• HH

• HH:mm:ss

• HH:mm:ss.SSS