Document errors implemented in 2025.01

Author: renetapopova

modules/ROOT/pages/errors/gql-errors.adoc

@@ -225,9 +225,9 @@ Status description:: error: data exception - invalid spatial value. A `POINT` mu
 
 Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D` coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D` coordinate reference system instead.
 
-// === 22N21
+=== 22N21
 
-// Status description:: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): `{ $crs }`.
+Status description:: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): `{ $crs }`.
 
 === 22N22
 
@@ -265,9 +265,9 @@ Status description:: error: data exception - overflow error. The result of the o
 
 // Status description:: error: data exception - missing temporal unit. At least one temporal unit must be specified.
 
-// === 22N31
+=== 22N31
 
-// Status description:: error: data exception - invalid properties in merge pattern. 'MERGE' cannot be used with graph element property values that are null or NaN.
+Status description:: error: data exception - invalid properties in merge pattern. 'MERGE' cannot be used with graph element property values that are null or NaN.
 
 === 22N32
 
@@ -297,9 +297,9 @@ Status description:: error: data exception - invalid coercion. Cannot coerce `{
 
 Status description:: error: data exception - invalid function argument. Invalid argument to the function `{ $fun }`.
 
-// === 22N39
+=== 22N39
 
-// Status description:: error: data exception - unsupported property value type. Value `{ $value }` cannot be stored in properties.
+Status description:: error: data exception - unsupported property value type. Value `{ $value }` cannot be stored in properties.
 
 // === 22N40
 
@@ -329,9 +329,9 @@ Status description:: error: data exception - unsupported use of parallel runtime
 
 Status description:: error: data exception - invalid parallel runtime configuration. No workers are configured for the parallel runtime. Set 'server.cypher.parallel.worker_limit' to a larger value.
 
-// === 22N48
+=== 22N48
 
-// Status description:: error: data exception - unable to use specified runtime. Cannot use the specified runtime `{ $runtime }` due to `{ $cause }`. Use another runtime.
+Status description:: error: data exception - unable to use specified runtime. Cannot use the specified runtime `{ $runtime }` due to `{ $cause }`. Use another runtime.
 
 === 22N49
 
@@ -365,9 +365,9 @@ Status description:: error: data exception - protocol message length limit overf
 
 // Status description:: error: data exception - invalid protocol type. Protocol type is invalid. Invalid number of struct components (received `{ $count1 }` but expected `{ $count2 }`).
 
-// === 22N58
+=== 22N58
 
-// Status description:: error: data exception - invalid spatial component. Cannot read the specified `{ $component }` component from `{ $value }`.
+Status description:: error: data exception - invalid spatial component. Cannot read the specified `{ $component }` component from `{ $value }`.
 
 // === 22N59
 
@@ -381,9 +381,9 @@ Status description:: error: data exception - protocol message length limit overf
 
 // Status description:: error: data exception - property key does not exist. The property key `{ $propKey }` does not exist.
 
-// === 22N64
+=== 22N64
 
-// Status description:: error: data exception - constraint does not exist. The constraint `{ $constrDescrOrName }` does not exist.
+Status description:: error: data exception - constraint does not exist. The constraint `{ $constrDescrOrName }` does not exist.
 
 // === 22N65
 
@@ -397,9 +397,9 @@ Status description:: error: data exception - conflicting constraint already exis
 
 Status description:: error: data exception - duplicated constraint name. A constraint with the same name already exists: `{ $constr }`.
 
-// === 22N68
+=== 22N68
 
-// Status description:: error: data exception - dependent constraint managed individually. Dependent constraints cannot be managed individually and must be managed together with its graph type.
+Status description:: error: data exception - dependent constraint managed individually. Dependent constraints cannot be managed individually and must be managed together with its graph type.
 
 === 22N69
 
@@ -441,9 +441,13 @@ Status description:: error: data exception - property presence verification fail
 
 Status description:: error: data exception - property type verification failed. `{ $entityType }` (`{ $entityId }`) with `{ $tokenType }` `{ $token }` must have the property `$propKey` with value type `{ $valueType }`.
 
-// === 22N79
+=== 22N79
 
-// Status description:: error: data exception - property uniqueness constraint violated. Property uniqueness constraint violated: `{ $reasons }`.
+Status description:: error: data exception - property uniqueness constraint violated. Property uniqueness constraint violated: `{ $reasons }`.
+
+=== 22N80
+
+Status description:: error: data exception - index entry conflict. Index entry conflict: `{ $value }`.
 
 === 22N81
 
@@ -525,13 +529,13 @@ Status description:: error: data exception - wrong token during deserialization.
 
 Status description:: error: data exception - invalid property based access control rule. Failed to administer property rule.
 
-// === 22NA1
+=== 22NA1
 
-// Status description:: error: data exception - invalid property based access control rule involving non-commutative expressions. The property `{ $propKey }` must appear on the left hand side of the `{ $operation }` operator.
+Status description:: error: data exception - invalid property based access control rule involving non-commutative expressions. The property `{ $propKey }` must appear on the left hand side of the `{ $operation }` operator.
 
-// === 22NA2
+=== 22NA2
 
-// Status description:: error: data exception - invalid property based access control rule involving multiple properties. The expression: `{ $expr }` is not supported. Property rules can only contain one property.
+Status description:: error: data exception - invalid property based access control rule involving multiple properties. The expression: `{ $expr }` is not supported. Property rules can only contain one property.
 
 // === 22NA3
 
@@ -549,9 +553,9 @@ Status description:: error: data exception - invalid property based access contr
 
 Status description:: error: data exception - invalid property based access control rule involving IS NOT NULL. The property value access rule pattern `{ $pred }` always evaluates to 'NULL'. Use 'IS NOT NULL' instead.
 
-// === 22NA7
+=== 22NA7
 
-// Status description:: error: data exception - invalid property based access control rule involving nontrivial predicates. The expression: `{ $expr }` is not supported. Only single, literal-based predicate expressions are allowed for property-based access control.
+Status description:: error: data exception - invalid property based access control rule involving nontrivial predicates. The expression: `{ $expr }` is not supported. Only single, literal-based predicate expressions are allowed for property-based access control.
 
 === 22NA8
 
@@ -761,6 +765,11 @@ Status description:: error: syntax error or access rule violation - invalid FIEL
 
 Status description:: error: syntax error or access rule violation - invalid input. Invalid input `{ $input }`, expected: `{ $valueList }`.
 
+=== 42I08
+
+Status description:: error: syntax error or access rule violation - invalid lower bound. The lower bound of the variable length relationship used in the `$fun()` function must be 0 or 1.
+
+
 === 42I13
 
 Status description:: error: syntax error or access rule violation - invalid number of procedure or function arguments. The procedure or function call does not provide the required number of arguments; expected `{ $count1 }` but got `{ $count2 }`. The procedure or function `{ $procFun }` has the signature: `{ $sig }`.
@@ -774,10 +783,19 @@ Status description:: error: syntax error or access rule violation - invalid refe
 
 Status description:: error: syntax error or access rule violation - invalid symbol in expression. Label expressions and relationship type expressions cannot contain `{ $input }`. To express a label disjunction use `{ $labelExpr }` instead.
 
+=== 42I23
+
+Status description:: error: syntax error or access rule violation - invalid quantified path pattern in shortest path. The `{ $fun }` function cannot contain a quantified path pattern.
+
+
 === 42I25
 
 Status description:: error: syntax error or access rule violation - invalid use of `CALL IN TRANSACTIONS`. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.
 
+=== 42I26
+
+Status description:: error: syntax error or access rule violation - invalid `DELETE`. 'DELETE ...' does not support removing labels from a node. Use 'REMOVE ...' instead.
+
 === 42I29
 
 Status description:: error: syntax error or access rule violation - invalid use of `IS`. The `IS` keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
@@ -786,6 +804,13 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 Status description:: error: syntax error or access rule violation - invalid use of `MATCH`. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a `WITH` clause between them.
 
+=== 42I34
+
+Status description:: error: syntax error or access rule violation - invalid use of pattern expression. A pattern expression can only be used to test the existence of a pattern. Use a pattern comprehension instead.
+
+=== 42I36
+
+Status description:: error: syntax error or access rule violation - invalid use of `REPORT STATUS`. 'REPORT STATUS' can only be used when specifying 'ON ERROR CONTINUE' or 'ON ERROR BREAK'.
 
 === 42I37
 
@@ -891,6 +916,10 @@ Status description:: error: syntax error or access rule violation - unsupported
 
 Status description:: error: syntax error or access rule violation - unsupported request. `{ $input }` is not allowed on the system database.
 
+=== 42N18
+
+Status description:: error: syntax error or access rule violation - read-only database. The database is in read-only mode.
+
 === 42N19
 
 Status description:: error: syntax error or access rule violation - duplicate clause. Duplicate `{ $syntax }` clause.
@@ -922,6 +951,10 @@ Status description:: error: syntax error or access rule violation - unbound vari
 
 Status description:: error: syntax error or access rule violation - specified number out of range. Expected `{ $component }` to be `{ $valueType }` in the range `{ $lower }` to `{ $upper }` but found `{ $value }`.
 
+=== 42N32
+
+Status description:: error: syntax error or access rule violation - invalid use of parameter map. Parameter maps cannot be used in `{ $keyword }` patterns. Use a literal map instead.
+
 === 42N39
 
 Status description:: error: syntax error or access rule violation - incompatible return columns. All subqueries in a `UNION` clause must have the same return column names.
@@ -938,6 +971,10 @@ Status description:: error: syntax error or access rule violation - unsupported
 
 Status description:: error: syntax error or access rule violation - unexpected end of input. Unexpected end of input, expected 'CYPHER', 'EXPLAIN', 'PROFILE' or a query.
 
+=== 42N47
+
+Status description:: error: syntax error or access rule violation - invalid use of `UNION`. 'CALL { ... } IN TRANSACTIONS' is not supported in '... UNION ...'.
+
 === 42N49
 
 Status description:: error: syntax error or access rule violation - unsupported normal form. Unknown Normal Form: `{ $input }`.
@@ -946,10 +983,32 @@ Status description:: error: syntax error or access rule violation - unsupported
 
 Status description:: error: syntax error or access rule violation - invalid parameter. Invalid parameter `{ $param }`.
 
+=== 42N53
+
+Status description:: error: syntax error or access rule violation - unsafe usage of repeatable elements. The quantified path pattern may yield an infinite number of rows under match mode 'REPEATABLE ELEMENTS` Use a path selector or add an upper bound to the quantified path pattern.
+
+
+=== 42N56
+
+Status description:: error: syntax error or access rule violation - unsupported use of properties. Properties are not supported in the `{ $fun }` function.
+
+
 === 42N57
 
 Status description:: error: syntax error or access rule violation - invalid use of data-modifications in expressions. `{ $expr }` cannot contain any updating clauses.
 
+=== 42N59
+
+Status description:: error: syntax error or access rule violation - variable already defined. Variable `{ $var }` already declared.
+
+=== 42N65
+
+Status description:: error: syntax error or access rule violation - node variable not bound. The `{ $fun }` function requires bound node variables when it is not part of a 'MATCH ...'.
+
+=== 42N66
+
+Status description:: error: syntax error or access rule violation - relationship variable already bound. Bound relationships are not allowed in calls to the `{ $fun }` function.
+
 === 42N70
 
 Status description:: error: syntax error or access rule violation - function without required WHERE clause. The function `{ $fun }` requires a WHERE clause.
@@ -982,6 +1041,10 @@ Status description:: error: syntax error or access rule violation - missing hint
 
 Status description:: error: syntax error or access rule violation - variable already bound. Node `{ $var }` has already been bound and cannot be modified by the `{ $clause }` clause.
 
+=== 42N81
+
+Status description:: error: syntax error or access rule violation - missing request parameter. Expected `{ $param }`, but got `{ $paramAndedList }`.
+
 === 42N83
 
 Status description:: error: syntax error or access rule violation - impersonation disallowed while password change required. Cannot impersonate a user while password change required.
@@ -1225,6 +1288,9 @@ Status description:: error: system configuration or operation exception - cyclic
 
 Status description:: error: system configuration or operation exception - insufficient resources for plan search. Could not find a query plan within given time and space limits.
 
+=== 51N25
+
+Status description:: error: system configuration or operation exception - database is busy. Cannot compile query due to excessive updates to indexes and constraints.
 
 === 51N27
 
@@ -1367,6 +1433,10 @@ Status description:: error: system configuration or operation exception - intern
 
 Status description:: error: system configuration or operation exception - unable to check enterprise license acceptance. The DBMS is unable to determine the enterprise license acceptance status.
 
+=== 51N61
+
+Status description:: error: system configuration or operation exception - index population failed. Index `{ $idx }` population failed.
+
 
 === 51N63
 
@@ -1403,10 +1473,26 @@ Status description:: error: system configuration or operation exception - bolt i
 
 Status description:: error: system configuration or operation exception - unsupported operation of a sharded database. Feature: `{ $feat }` is not available in a sharded database.
 
+=== 51N72
+
+Status description:: error: system configuration or operation exception - memory pool out of memory. Failed to allocate memory in a memory pool. See `{ $cfgSetting }` in the neo4j configuration.
+
+=== 51N73
+
+Status description:: error: system configuration or operation exception - transaction memory limit reached. The transaction used more memory than was allowed. The maximum allowed size for a transaction can be configured with `{ $cfgSetting }` in the neo4j configuration.
+
+=== 51N74
+
+Status description:: error: system configuration or operation exception - maximum number of transactions reached. Failed to start a new transaction. The limit of concurrent transactions is reached. Increase the number of concurrent transactions using `{ $cfgSetting }` in the neo4j configuration.
+
 == Procedure exception
 
 Procedure exceptions occur when there is an error in executing a procedure, such as when the procedure execution fails due to a client error, when the procedure cannot be invoked on a primary, when the number of arguments to checkConnectivity is invalid, etc.
 
+=== 52N01
+
+Status description:: error: procedure exception - procedure execution timeout. Execution of the procedure `{ $proc }` timed out after `{ $timeAmount }` `{ $timeUnit }`.
+
 === 52N02
 
 Status description:: error: procedure exception - procedure execution client error. Execution of the procedure `{ $proc }` failed due to a client error.
@@ -1508,5 +1594,33 @@ Status description:: error: procedure exception - procedure sandboxed. `{ $sig }
 
 Status description:: error: procedure exception - procedure compilation failed. Failed to compile procedure/function defined in `{ $procClass }`: `{ $msg }`
 
+=== 52N36
+
+Status description:: error: procedure exception - invalid procedure argument with API documentation hint. Invalid argument `{ $value }` for `{ $procParam }` on procedure `{ $proc }`. The expected format of `{ $procParam }` is outlined in the `{ $procParamFmt }` API documentation.
+
+=== 52N37
+
+Status description:: error: procedure exception - procedure execution error. Execution of the procedure `{ $proc } ` failed.
+
+=== 52U00
+
+Status description:: error: procedure exception - custom procedure execution error cause. Execution of the procedure `{ $proc }` failed due to `{ $msgTitle }`: { $msg }
+
+=== 53N34
+
+Status description:: error: function exception - function restricted. `{ $fun }` is is restricted and accesses database internals. User-defined function restriction is controlled by the dbms.security.procedures.unrestricted setting. Only un-restrict user-defined functions you can trust with access to database internals.
+
+=== 53N35
+
+Status description:: error: function exception - function compilation failed. Failed to compile function defined in `{ $funClass }`: { $msg }
+
+=== 53N37
+
+Status description:: error: function exception - function execution error. Execution of the function `{ $fun }` failed.
+
+=== 53U00
+
+Status description:: error: function exception - custom function execution error cause. Execution of the function `{ $fun }` failed due to `{ $msgTitle }`: { $msg }
+