DOCS-279 Publish 2026.01.3

antora.yml

@@ -1,12 +1,12 @@
 name: status-codes
 title: Status Codes for Errors & Notifications
-version: '2025.12'
+version: '2026.01'
 start_page: ROOT:index.adoc
 nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
     page-origin-private: false
-    neo4j-version: '2025.12'
-    neo4j-version-exact: '2025.12.1'
-    neo4j-buildnumber: '2025.12'
+    neo4j-version: '2026.01'
+    neo4j-version-exact: '2026.01.3'
+    neo4j-buildnumber: '2026.01'

modules/ROOT/content-nav.adoc

@@ -145,6 +145,9 @@
 **** xref:errors/gql-errors/22NA9.adoc[]
 **** xref:errors/gql-errors/22NAA.adoc[]
 **** xref:errors/gql-errors/22NAB.adoc[]
+**** xref:errors/gql-errors/22NAC.adoc[]
+**** xref:errors/gql-errors/22NAD.adoc[]
+**** xref:errors/gql-errors/22NAE.adoc[]
 **** xref:errors/gql-errors/22NB0.adoc[]
 **** xref:errors/gql-errors/22NB1.adoc[]
 **** xref:errors/gql-errors/22NB2.adoc[]
@@ -285,6 +288,11 @@
 **** xref:errors/gql-errors/42I66.adoc[]
 **** xref:errors/gql-errors/42I67.adoc[]
 **** xref:errors/gql-errors/42I68.adoc[]
+**** xref:errors/gql-errors/42I69.adoc[]
+**** xref:errors/gql-errors/42I70.adoc[]
+**** xref:errors/gql-errors/42I71.adoc[]
+**** xref:errors/gql-errors/42I72.adoc[]
+**** xref:errors/gql-errors/42I76.adoc[]
 **** xref:errors/gql-errors/42N00.adoc[]
 **** xref:errors/gql-errors/42N01.adoc[]
 **** xref:errors/gql-errors/42N02.adoc[]

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

@@ -149,6 +149,9 @@ If you want to drop the index, you must also drop the constraint.
 | Neo.ClientError.Schema.RepeatedRelationshipTypeInSchema
 | Unable to create an index or a constraint because the schema had a repeated relationship type.
 
+| Neo.ClientError.Schema.SchemaRuleEntrySizeLimitError
+| A schema rule entry exceeded the maximum allowed size.
+
 | Neo.ClientError.Schema.TokenLengthError
 | A token name, such as a label, relationship type or property key is too long
 
@@ -491,4 +494,3 @@ Please restore from backup.
 | The database was unable to terminate the transaction.
 
 |===
-

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

@@ -2,7 +2,50 @@
 
 
 == Status description
-error: data exception - invalid properties in merge pattern. `MERGE` cannot be used with graph element property values that are null or NaN.
+error: data exception - invalid properties in merge pattern. The `{ <<entityType>> }` property `{ <<propKey>> }` in `{ <<pat>> }` is invalid. `MERGE` cannot be used with a graph element property value that is `{ <<value>> }`.
+
+== Explanation
+This error occurs when a `MERGE` pattern includes a node or relationship property value that is not allowed, such as `null` or `NaN`.
+Because `MERGE` must be able to match or create a concrete graph element, these invalid values are rejected.
+
+== Example scenarios
+
+Let's take the following example scenarios:
+
+=== Null property value in a `MERGE` pattern
+For example, try to merge a node with a `null` property value as follows:
+
+[source,cypher]
+----
+MERGE (p:Person {age: null})
+----
+
+The query returns an error with GQLSTATUS 22N31 and the status description:
+
+[source]
+----
+error: data exception - invalid properties in merge pattern. The node property 'age' in '(:Person {age: null})' is invalid. `MERGE` cannot be used with a graph element property value that is null.
+----
+
+In this case, provide a concrete value for the property, or remove it from the `MERGE` pattern.
+
+=== NaN property value in a `MERGE` pattern
+For example, try to merge a relationship with a `NaN` property value as follows:
+
+[source,cypher]
+----
+WITH 0.0/0.0 AS nan
+MERGE (a:Person)-[:KNOWS {score: nan}]->(b:Person)
+----
+
+The query returns an error with GQLSTATUS 22N31 and the status description:
+
+[source]
+----
+error: data exception - invalid properties in merge pattern. The relationship property 'score' in '(:Person)-[:KNOWS {score: NaN}]->(:Person)' is invalid. 'MERGE' cannot be used with graph element property value that is NaN.
+----
+
+In this case, provide a numeric value for the property, or remove it from the `MERGE` pattern.
 
 
 ifndef::backend-pdf[]

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

@@ -0,0 +1,40 @@
+= 22NAC
+
+== Status description
+error: data exception - characters after quote in CSV field. Characters after an ending quote in a CSV field are not supported. See `{ <<input>> }` at position `{ <<pos>> }`. This is read as `{ <<variable>> }`.
+
+== Explanation
+When a CSV file contains a field that starts with a quote and has content after the ending quote, the file is formatted incorrectly, and trying to read such a file with `LOAD CSV` will result in an error.
+
+== Example scenario
+
+For example, let's say you have a CSV file, called `somefile.csv`, with the following content:
+
+[source,csv]
+----
+x,y
+"x",1
+"y"y,2
+----
+
+Then, when you run the following query:
+
+[source,cypher]
+----
+LOAD CSV 'somefile.csv' AS line
+RETURN count(line)
+----
+
+you will receive an error with GQLSTATUS 22NAC and status description:
+
+[source]
+----
+error: data exception - characters after quote in CSV field. Characters after an ending quote in a CSV field are not supported. See 'somefile.csv' at position 14. This is read as `y"y` .
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

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

@@ -0,0 +1,40 @@
+= 22NAD
+
+== Status description
+error: data exception - missing end quote in CSV field. Missing end quote at position `{ <<pos>> }` in `{ <<input>> }`.
+
+== Explanation
+When a CSV file contains a field that starts with a quote but misses an ending quote, the file is formatted incorrectly and trying to read such a file with `LOAD CSV` will result in an error.
+
+== Example scenario
+
+For example, let's say you have a CSV file, called `somefile.csv`, with the following content:
+
+[source,csv]
+----
+x,y
+"x",1
+"y,2
+----
+
+Then, when you run the following query:
+
+[source,cypher]
+----
+LOAD CSV 'somefile.csv' AS line
+RETURN count(line)
+----
+
+you will receive an error with GQLSTATUS 22NAD and status description:
+
+[source]
+----
+error: data exception - missing end quote in CSV field. Missing end quote at position 15 in 'somefile.csv'.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

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

@@ -0,0 +1,41 @@
+= 22NAE
+
+== Status description
+error: data exception - multi-line field in illegal CSV context. Multi-line fields are illegal in this context. Verify that there is not a missing end quote in `{ <<input>> }` at position `{ <<pos>> }`.
+
+== Explanation
+This error is thrown when a CSV file contains a field that spans multiple lines, but the context in which it is being read does not allow multi-line fields.
+This often occurs when there is a missing end quote in a quoted field.
+
+== Example scenario
+
+For example, let's say you have a CSV file, called `somefile.csv`, with the following content:
+[source,csv]
+----
+x,y
+"x",1
+"y
+",2
+----
+
+And that the `neo4j` database logging is configured with specific allowed multiline files, but where `somefile.csv` is not among them.
+
+Then, when you run the following query:
+[source,cypher]
+----
+LOAD CSV 'somefile.csv' AS line
+RETURN count(line)
+----
+
+you will receive an error with GQLSTATUS 22NAE and status description:
+[source]
+----
+error: data exception - multi-line field in illegal CSV context. Multi-line fields are illegal in this context. Verify that there is not a missing end quote in 'somefile.csv' at position 15.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

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

@@ -0,0 +1,35 @@
+= 42I69
+
+== Status description
+error: syntax error or access rule violation - invalid search variable reference. `{ <<variable>> }` must reference a variable from the same `MATCH` statement.
+
+== Example scenario
+
+For example, when trying to use a variable from a previous `MATCH` statement as variable reference in a `SEARCH` clause:
+
+[source,cypher]
+----
+CYPHER 25
+MATCH (movie:Movie)
+MATCH (m:Movie {title:'Matrix, The'})
+  SEARCH movie IN (
+    VECTOR INDEX moviePlots
+    FOR [1, 2, 3]
+    LIMIT 5
+  )
+RETURN movie.title AS title
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001] with a cause with GQLSTATUS 42I69 and status description:
+
+[source]
+----
+error: syntax error or access rule violation - invalid search variable reference. `movie` must reference a variable from the same `MATCH` statement.
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

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

@@ -0,0 +1,48 @@
+= 42I70
+
+== Status description
+error: syntax error or access rule violation - search clause with multiple bound variables. In order to have a search clause, a `MATCH` statement can only have one bound variable.
+
+[#_example_scenario]
+== Example scenario
+
+For example, when trying to use a `SEARCH` clause in a `MATCH` statement with more than one bound variable:
+
+[source,cypher]
+----
+Cypher 25
+MATCH (movie:Movie)-[r]->()
+  SEARCH movie IN (
+    VECTOR INDEX moviePlots
+    FOR [1, 2, 3]
+    LIMIT 5
+  )
+RETURN movie.title AS title, r.prop AS prop
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001] with a cause with GQLSTATUS 42I70.
+
+== Possible solution
+The first iteration of the `SEARCH` clause comes with many restrictions on the `MATCH` statement.
+It is likely that some of these restriction will be lifted in future versions of Neo4j.
+For the time being, the Cypher query under xref:errors/gql-errors/42I70.adoc#_example_scenario[Example scenario] can be rewritten like this:
+
+[source,cypher]
+----
+CYPHER 25
+MATCH (movie:Movie)
+  SEARCH movie IN (
+    VECTOR INDEX moviePlots
+    FOR [1, 2, 3]
+    LIMIT 5
+  )
+MATCH (movie)-[r]->()
+RETURN movie.title AS title, r.prop AS prop
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]

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

@@ -0,0 +1,48 @@
+= 42I71
+
+== Status description
+error: syntax error or access rule violation - search clause with invalid predicates. In order to have a search clause, a `MATCH` statement can only have predicates on the bound node or relationship.
+
+[#_example_scenario]
+== Example scenario
+
+For example, when trying to use a `SEARCH` clause in a `MATCH` statement with predicates on other parts of the pattern than the bound variable:
+
+[source,cypher]
+----
+CYPHER 25
+MATCH (movie:Movie)-[]->(:Actor)
+  SEARCH movie IN (
+    VECTOR INDEX moviePlots
+    FOR [1, 2, 3]
+    LIMIT 5
+  )
+RETURN movie.title AS title
+----
+
+You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001] with a cause with GQLSTATUS 42I71.
+
+== Possible solution
+The first iteration of the `SEARCH` clause comes with many restrictions on the `MATCH` statement.
+It is likely that some of these restriction will be lifted in future versions of Neo4j.
+For the time being, the Cypher query under xref:errors/gql-errors/42I71.adoc#_example_scenario[Example scenario] can be rewritten like this:
+
+[source,cypher]
+----
+CYPHER 25
+MATCH (movie:Movie)
+  SEARCH movie IN (
+    VECTOR INDEX moviePlots
+    FOR [1, 2, 3]
+    LIMIT 5
+  )
+MATCH (movie)-[]->(:Actor)
+RETURN movie.title AS title
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]