Merge branch 'dev' into vector_type

JPryce-Aklundh · web-flow · commit 81e7f84eb74f · 2025-09-29T15:37:47.000+02:00
diff --git a/antora.yml b/antora.yml
@@ -7,4 +7,4 @@ nav:
 - modules/ROOT/content-nav.adoc
 asciidoc:
   attributes:
-    neo4j-version: '2025.09'
+    neo4j-version: '2025.10'
diff --git a/modules/ROOT/content-nav.adoc b/modules/ROOT/content-nav.adoc
@@ -92,16 +92,18 @@
 ** xref:functions/graph.adoc[]
 ** xref:functions/list.adoc[]
 ** xref:functions/load-csv.adoc[]
-** xref:functions/mathematical-logarithmic.adoc[]
-** xref:functions/mathematical-numeric.adoc[]
-** xref:functions/mathematical-trigonometric.adoc[]
+** Mathematical functions
+*** xref:functions/mathematical-logarithmic.adoc[]
+*** xref:functions/mathematical-numeric.adoc[]
+*** xref:functions/mathematical-trigonometric.adoc[]
 ** xref:functions/predicate.adoc[]
 ** xref:functions/scalar.adoc[]
 ** xref:functions/spatial.adoc[]
 ** xref:functions/string.adoc[]
-** xref:functions/temporal/duration.adoc[]
-** xref:functions/temporal/index.adoc[]
-** xref:functions/temporal/format.adoc[]
+** Temporal functions
+*** xref:functions/temporal/duration.adoc[]
+*** xref:functions/temporal/index.adoc[]
+*** xref:functions/temporal/format.adoc[]
 ** xref:functions/user-defined.adoc[]
 ** xref:functions/vector.adoc[]
 
diff --git a/modules/ROOT/pages/clauses/call.adoc b/modules/ROOT/pages/clauses/call.adoc
@@ -208,7 +208,7 @@ RETURN count(*) AS results
 `YIELD` can be used to filter for specific results.
 This requires knowing the names of the arguments within a procedure's signature, which can either be found in the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/[Operations Manual -> Procedures] or in the `signature` column returned by a `SHOW PROCEDURES` command (see example below).
 
-.Find the argument names of `db.propertyKeys`
+.Find the argument names of `db.propertyKeys()`
 [source, cypher]
 ----
 SHOW PROCEDURES YIELD name, signature
diff --git a/modules/ROOT/pages/functions/index.adoc b/modules/ROOT/pages/functions/index.adoc
@@ -207,8 +207,12 @@ LOAD CSV functions can be used to get information about the file that is process
 |===
 
 
+[[header-query-functions-mathematical]]
+== Mathematical functions
+
+
 [[header-query-functions-logarithmic]]
-== Logarithmic functions
+=== Logarithmic functions
 
 These functions all operate on numerical expressions only, and will return an error if used on any other values.
 
@@ -240,7 +244,7 @@ These functions all operate on numerical expressions only, and will return an er
 
 
 [[header-query-functions-numeric]]
-== Numeric functions
+=== Numeric functions
 
 These functions all operate on numerical expressions only, and will return an error if used on any other values.
 
@@ -280,7 +284,7 @@ These functions all operate on numerical expressions only, and will return an er
 
 
 [[header-query-functions-trigonometric]]
-== Trigonometric functions
+=== Trigonometric functions
 
 These functions all operate on numerical expressions only, and will return an error if used on any other values.
 
@@ -613,8 +617,12 @@ If the points are in a Cartesian CRS, the function returns the Euclidean distanc
 |===
 
 
+[[header-query-functions-temporal]]
+== Temporal functions
+
+
 [[header-query-functions-temporal-duration]]
-== Temporal duration functions
+=== Duration functions
 
 `DURATION` values of the xref::values-and-types/temporal.adoc[temporal types] can be created manipulated using the following functions:
 
@@ -645,7 +653,7 @@ If the points are in a Cartesian CRS, the function returns the Euclidean distanc
 |===
 
 [[header-query-functions-temporal-instant-types]]
-== Temporal instant types functions
+=== Instant type functions
 
 Values of the xref::values-and-types/temporal.adoc[temporal types] -- `DATE`, `ZONED TIME`, `LOCAL TIME`, `ZONED DATETIME`, and `LOCAL DATETIME` -- can be created manipulated using the following functions:
 
@@ -766,7 +774,7 @@ Values of the xref::values-and-types/temporal.adoc[temporal types] -- `DATE`, `Z
 
 [role=label--cypher-25-only label--new-Neo4j-2025.09]
 [[header-query-functions-temporal-format]]
-== Temporal format functions
+=== Format functions
 
 These functions format temporal instance and duration values:
 
diff --git a/modules/ROOT/pages/functions/mathematical-logarithmic.adoc b/modules/ROOT/pages/functions/mathematical-logarithmic.adoc
@@ -2,7 +2,7 @@
 :table-caption!:
 
 [[query-functions-logarithmic]]
-= Mathematical functions - logarithmic
+= Logarithmic functions
 
 Logarithmic mathematical functions operate on numeric expressions only, and will return an error if used on any other values. See also xref:expressions/mathematical-operators.adoc[Mathematical operators].
 
diff --git a/modules/ROOT/pages/functions/mathematical-numeric.adoc b/modules/ROOT/pages/functions/mathematical-numeric.adoc
@@ -2,7 +2,7 @@
 :table-caption!:
 
 [[query-functions-numeric]]
-= Mathematical functions - numeric
+= Numeric functions
 
 Numeric mathematical functions operate on numeric expressions only, and will return an error if used on any other values.
 See also xref:expressions/mathematical-operators.adoc[Mathematical operators].
diff --git a/modules/ROOT/pages/functions/mathematical-trigonometric.adoc b/modules/ROOT/pages/functions/mathematical-trigonometric.adoc
@@ -2,7 +2,7 @@
 :table-caption!:
 
 [[query-functions-trigonometric]]
-= Mathematical functions - trigonometric
+= Trigonometric functions
 
 Trigonometric mathematical functions operate on numeric expressions only, and will return an error if used on any other values. See also xref:expressions/mathematical-operators.adoc[Mathematical operators].
 
diff --git a/modules/ROOT/pages/functions/temporal/duration.adoc b/modules/ROOT/pages/functions/temporal/duration.adoc
@@ -1,7 +1,7 @@
 :description: Cypher provides functions allowing for the creation and manipulation of temporal `DURATION` values.
 
 [[query-functions-temporal-duration]]
-= Temporal functions - duration
+= Duration functions
 :table-caption!:
 
 Duration functions allow for the creation and manipulation of temporal `DURATION` values.
diff --git a/modules/ROOT/pages/functions/temporal/format.adoc b/modules/ROOT/pages/functions/temporal/format.adoc
@@ -2,7 +2,7 @@
 :table-caption!:
 
 [[query-functions-temporal-format]]
-= Temporal functions - format
+= Format functions
 
 [role=label--cypher-25-only label--new-Neo4j-2025.09]
 [[query-functions-temporal-format-function]]
diff --git a/modules/ROOT/pages/functions/temporal/index.adoc b/modules/ROOT/pages/functions/temporal/index.adoc
@@ -2,7 +2,7 @@
 :table-caption!:
 
 [[query-functions-temporal-instant-types]]
-= Temporal functions - instant types
+= Instant type functions
 
 Temporal functions allow for the creation and manipulation of values for each temporal type -- `DATE`, `ZONED TIME`, `LOCAL TIME`, `ZONED DATETIME`, and `LOCAL DATETIME`.
 
diff --git a/modules/ROOT/pages/genai-integrations.adoc b/modules/ROOT/pages/genai-integrations.adoc
@@ -65,7 +65,6 @@ This function sends one API request every time it is called, which may result in
 If you want to generate many embeddings at once, use xref:genai-integrations.adoc#multiple-embeddings[].
 
 
-
 [.tabbed-example]
 ====
 [.include-with-Store-embedding-as-a-vector]
@@ -103,15 +102,15 @@ RETURN m.embedding AS embedding
 
 Use the `db.create.setNodeVectorProperty` procedure to store an embedding as a `LIST<FLOAT>` value to a node property.
 
-.Signature for `db.create.setNodeVectorProperty` label:procedure[]
+.Signature for `db.create.setNodeVectorProperty()` label:procedure[]
 [source,syntax]
 ----
 db.create.setNodeVectorProperty(node :: NODE, key :: STRING, vector :: ANY)
 ----
 
 Use the `db.create.setRelationshipVectorProperty` procedure to store an embedding as a `LIST<FLOAT>` value to a relationship property.
 
-.Signature for `db.create.setRelationshipVectorProperty` label:procedure[] 
+.Signature for `db.create.setRelationshipVectorProperty()` label:procedure[] 
 [source,syntax]
 ----
 db.create.setRelationshipVectorProperty(relationship :: RELATIONSHIP, key :: STRING, vector :: ANY)
@@ -335,7 +334,7 @@ For an alternative method more suitable to processing large amounts of data, see
 == GenAI providers
 
 The following GenAI providers are supported for generating vector embeddings.
-Each provider has its own configuration map that can be passed to `genai.vector.encode` or `genai.vector.encodeBatch()`.
+Each provider has its own configuration map that can be passed to `genai.vector.encode()` or `genai.vector.encodeBatch()`.
 
 [[vertex-ai]]
 === Vertex AI
diff --git a/modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc b/modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc
@@ -124,7 +124,7 @@ OPTIONS {
 
 <1> The `fulltext.analyzer` setting can be used to configure an index-specific analyzer.
 In this case, it is set to the `english` analyzer.
-The possible values for the `fulltext.analyzer` setting can be listed with the `db.index.fulltext.listAvailableAnalyzers` procedure.
+The possible values for the `fulltext.analyzer` setting can be listed with the `db.index.fulltext.listAvailableAnalyzers()` procedure.
 <2>  The `fulltext.eventually_consistent` setting, if set to `true`, will put the index in an _eventually consistent_ update mode.
 This means that updates will be applied in a background thread "as soon as possible", instead of during a transaction commit, which is true for other indexes.
 
@@ -134,13 +134,13 @@ For more information on how to configure full-text indexes, refer to the link:{n
 == Query full-text indexes
 
 Unlike xref:indexes/search-performance-indexes/managing-indexes.adoc[search-performance indexes], full-text indexes are not automatically used by the xref:planning-and-tuning/execution-plans.adoc[Cypher query planner].
-To query a full-text index, use either the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_queryNodes[`db.index.fulltext.queryNodes`] or the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_queryRelationships[`db.index.fulltext.queryRelationships`] procedure.
+To query a full-text index, use either the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_queryNodes[`db.index.fulltext.queryNodes()`] or the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_fulltext_queryRelationships[`db.index.fulltext.queryRelationships()`] procedure.
 
 [NOTE]
 An index cannot be used while its `state` is `POPULATING`, which occurs immediately after it is created.
 To check the `state` of a full-text index -- whether it is `ONLINE` (usable) or `POPULATING` (still being built; the `populationPercent` column shows the progress of the index creation) -- run the following command: `SHOW FULLTEXT INDEXES`.
 
-This query uses the `db.index.fulltext.queryNodes` to look for `nils` in the previously created full-text index `namesAndTeams`:
+This query uses the `db.index.fulltext.queryNodes()` procedure to look for `nils` in the previously created full-text index `namesAndTeams`:
 
 .Query a full-text index for a node property
 [source, cypher]
@@ -172,7 +172,7 @@ This is possible because both the property values that are indexed, and the quer
 
 The `score` results are always returned in _descending score order_, where the best matching result entry is put first.
 
-This query uses the `db.index.fulltext.queryRelationships` to query the previously created `communications` full-text index for any `message` containing "meeting":
+This query uses the `db.index.fulltext.queryRelationships()` procedure to query the previously created `communications` full-text index for any `message` containing "meeting":
 
 .Query a full-text index for a relationship property
 [source, cypher]
@@ -362,19 +362,19 @@ The procedures for full-text indexes are listed in the table below:
 | Usage | Procedure/Command | Description
 
 | Eventually consistent indexes.
-| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_awaitEventuallyConsistentIndexRefresh[`db.index.fulltext.awaitEventuallyConsistentIndexRefresh`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_awaitEventuallyConsistentIndexRefresh[`db.index.fulltext.awaitEventuallyConsistentIndexRefresh()`]
 | Wait for the updates from recently committed transactions to be applied to any eventually-consistent full-text indexes.
 
 | List available analyzers.
-| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_listAvailableAnalyzers[`db.index.fulltext.listAvailableAnalyzers`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_listAvailableAnalyzers[`db.index.fulltext.listAvailableAnalyzers()`]
 | List the available analyzers that the full-text indexes can be configured with.
 
 | Use full-text node index.
-| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_queryNodes[`db.index.fulltext.queryNodes`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_queryNodes[`db.index.fulltext.queryNodes()`]
 | Query the given full-text index. Returns the matching nodes and their Lucene query score, ordered by score.
 
 | Use full-text relationship index.
-| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_queryRelationships[`db.index.fulltext.queryRelationships`]
+| https://neo4j.com/docs/operations-manual/current/procedures/#procedure_db_index_fulltext_queryRelationships[`db.index.fulltext.queryRelationships()`]
 | Query the given full-text index. Returns the matching relationships and their Lucene query score, ordered by score.
 
 |===
diff --git a/modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc b/modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc
@@ -181,13 +181,13 @@ Default value::: `100`
 [[query-vector-index]]
 == Query vector indexes
 
-To query a node vector index, use the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes`] procedure.
+To query a node vector index, use the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes()`] procedure.
 
 [NOTE]
 An index cannot be used while its `state` is `POPULATING`, which occurs immediately after it is created.
 To check the `state` of a vector index -- whether it is `ONLINE` (usable) or `POPULATING` (still being built; the `populationPercent` column shows the progress of the index creation) -- run the following command: `SHOW VECTOR INDEXES`.
 
-.Signature for `db.index.vector.queryNodes`
+.Signature for `db.index.vector.queryNodes()`
 [source,syntax]
 ----
 db.index.vector.queryNodes(indexName :: STRING, numberOfNearestNeighbours :: INTEGER, query :: ANY) :: (node :: NODE, score :: FLOAT)
@@ -229,13 +229,13 @@ If the query vector itself is not wanted, adding the predicate `WHERE score < 1`
 
 To query a relationship vector index, use the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryRelationships[`db.index.vector.queryRelationships`] procedure.
 
-.Signature for `db.index.vector.queryRelationships` 
+.Signature for `db.index.vector.queryRelationships()` 
 [source,syntax]
 ----
 db.index.vector.queryRelationships(indexName :: STRING, numberOfNearestNeighbours :: INTEGER, query :: ANY) :: (relationship :: RELATIONSHIP, score :: FLOAT)
 ----
 
-`db.index.vector.queryRelationships` has the same argument descriptions as `db.index.vector.queryNodes`.
+`db.index.vector.queryRelationships()` has the same argument descriptions as `db.index.vector.queryNodes()`.
 
 [TIP]
 Use xref:functions/vector.adoc[] to compute the similarity score between two specific vector pairs without using a vector index.
@@ -472,21 +472,21 @@ image::euclidean-similarity-equation.svg["The Euclidean of vector v and vector u
 | Usage | Procedure | Description
 
 | Use node vector index.
-| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes`]
+| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes()`]
 | Query the given node vector index.
 Returns the requested number of approximate nearest neighbor nodes and their similarity score, ordered by score.
 
 | Use relationship vector index.
-| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryRelationships[`db.index.vector.queryRelationships`]
+| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryRelationships[`db.index.vector.queryRelationships()`]
 | Query the given relationship vector index.
 Returns the requested number of approximate nearest neighbor relationships and their similarity score, ordered by score. 
 
 | Set node vector property.
-| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_create_setNodeVectorProperty[`db.create.setNodeVectorProperty`]
+| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_create_setNodeVectorProperty[`db.create.setNodeVectorProperty()`]
 | Update a given node property with the given vector in a more space-efficient way than directly using xref:clauses/set.adoc#set-set-a-property[`SET`].
 
 | Set relationship vector property.
-| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_create_setRelationshipVectorProperty[`db.create.setRelationshipVectorProperty`]
+| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_create_setRelationshipVectorProperty[`db.create.setRelationshipVectorProperty()`]
 | Update a given relationship property with the given vector in a more space-efficient way than directly using xref:clauses/set.adoc#set-set-a-property[`SET`].
 
 |===
@@ -515,7 +515,7 @@ The following table lists the issues and, if fixed, the version in which they we
 |===
 | Known issues | Fixed in
 
-| The creation of a vector index using the legacy procedure link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex`] may fail with an error in Neo4j 5.18 and later if the database was last written to with a version prior to Neo4j 5.11, and the legacy procedure is the first write operation used on the newer version.
+| The creation of a vector index using the legacy procedure link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex()`] may fail with an error in Neo4j 5.18 and later if the database was last written to with a version prior to Neo4j 5.11, and the legacy procedure is the first write operation used on the newer version.
 In Neo4j 5.20, the error was clarified.
 [TIP]
 --
diff --git a/modules/ROOT/pages/indexes/syntax.adoc b/modules/ROOT/pages/indexes/syntax.adoc
@@ -177,7 +177,7 @@ ON EACH “[“ r.propertyName[, ...] “]”
 
 The following settings can be specified for full-text indexes:
 
-* `fulltext.analyzer` - specifies what analyzer to use (the `db.index.fulltext.listAvailableAnalyzers` procedure lists what analyzers are available).
+* `fulltext.analyzer` - specifies what analyzer to use (the `db.index.fulltext.listAvailableAnalyzers()` procedure lists what analyzers are available).
 * `fulltext.eventually_consistent` - specifies whether a full-text index is eventually consistent.
 If set to `true`, it will ensure that updates from committing transactions are applied in a background thread.
 
@@ -250,13 +250,13 @@ To use them, specific procedures must be called. Their signatures can be seen be
 [[query-full-text-index]]
 === Full-text indexes
 
-.Query full-text index on nodes: db.index.fulltext.queryNodes
+.Query full-text index on nodes: db.index.fulltext.queryNodes()
 [source,syntax]
 ----
 CALL db.index.fulltext.queryNodes(indexName :: STRING, queryString :: STRING, options = {} :: MAP)
 ----
 
-.Query full-text index on relationships: db.index.fulltext.queryRelationships
+.Query full-text index on relationships: db.index.fulltext.queryRelationships()
 [source, syntax]
 ----
 CALL db.index.fulltext.queryRelationships(indexName :: STRING, queryString :: STRING, options = {} :: MAP) 
@@ -275,13 +275,13 @@ For more information, see xref:indexes/semantic-indexes/full-text-indexes.adoc#q
 [[query-vector-index]]
 === Vector indexes
 
-.Query vector-text index on nodes: db.index.vector.queryNodes
+.Query vector-text index on nodes: db.index.vector.queryNodes()
 [source,syntax]
 ----
 CALL db.index.vector.queryNodes(indexName :: STRING, numberOfNearestNeighbours :: INTEGER, query :: LIST<INTEGER | FLOAT>)
 ----
 
-.Query vector-text index on relationships: db.index.vector.queryRelationships
+.Query vector-text index on relationships: db.index.vector.queryRelationships()
 [source,syntax]
 ----
 CALL db.index.vector.queryRelationships(indexName :: STRING, numberOfNearestNeighbours :: INTEGER, query :: LIST<INTEGER | FLOAT>)
diff --git a/modules/ROOT/pages/patterns/shortest-paths.adoc b/modules/ROOT/pages/patterns/shortest-paths.adoc
diff --git a/modules/ROOT/pages/planning-and-tuning/runtimes/reference.adoc b/modules/ROOT/pages/planning-and-tuning/runtimes/reference.adoc
