Skip to content

Commit a279853

Browse files
initial
1 parent cb781a1 commit a279853

File tree

3 files changed

+16
-7
lines changed

3 files changed

+16
-7
lines changed

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -109,6 +109,17 @@ MERGE (a {foo:1})-[:T]->(b {foo:a.foo})
109109
a|
110110
It is no longer possible to specify a property of one entity (node or relationship) by referring to another entity’s property within the same `MERGE` clause.
111111

112+
a|
113+
label:functionality[]
114+
label:removed[]
115+
[source, cypher, role="noheader"]
116+
----
117+
CREATE ... INDEX ... OPTIONS { indexProvider: ... }
118+
CREATE ... CONSTRAINTS ... OPTIONS { indexProvider: ... }
119+
----
120+
| Specifying an index provider in the `OPTIONS` map when creating an index or constraint is no longer supported.
121+
Cypher will default t
122+
112123
|===
113124

114125

modules/ROOT/pages/indexes/search-performance-indexes/managing-indexes.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,9 @@ Instad an informational notification is returned.
214214
Creating a text index can be done with the `CREATE TEXT INDEX` command.
215215
Note that the index name must be unique.
216216

217-
Text indexes have no supported index configuration and they have two index providers available, `text-2.0` (default -- see xref:indexes/search-performance-indexes/managing-indexes.adoc#text-indexes-trigram-indexes[Trigram indexing] below for more information) and `text-1.0` (deprecated).
217+
Text indexes have no supported index configuration.
218+
219+
See xref:indexes/search-performance-indexes/managing-indexes.adoc#text-indexes-trigram-indexes[Trigram indexing] for information about how text indexes process `STRING` values.
218220

219221
[[text-indexes-supported-predicates]]
220222
[discrete]

modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,6 @@ A vector index allows you to retrieve a neighborhood of nodes or relationships b
6868

6969
A vector index is a single-label, single-property index for nodes or a single-relationship-type, single-property index for relationships.
7070
It can be used to index nodes or relationships by `LIST<INTEGER | FLOAT>` properties valid to the dimensions and vector similarity function of the index.
71-
Note that the available vector index providers (`vector-2.0` (default) and `vector-1.0` (deprecated)) support different index schemas, property value types, and vector dimensions.
72-
For more information, see xref:indexes/semantic-indexes/vector-indexes.adoc#vector-index-providers[].
7371

7472
A vector index is created by using the `CREATE VECTOR INDEX [index_name]` command.
7573
It is recommended to give the index a name when it is created.
@@ -347,10 +345,8 @@ DROP INDEX moviePlots
347345
[[vector-index-providers]]
348346
== Vector index providers for compatibility
349347

350-
As of Neo4j 5.18, the default index provider is `vector-2.0`.
351-
As of Neo4j 5.26, it is no longer possible to specify an index provider when creating indexes.
352-
Instead, Neo4j selects the most performant provider (currently `vector-2.0`).
353-
348+
It is not possible to specify an index provider when creating indexes in Cypher 25.
349+
Instead, Neo4j selects the most performant provider (currently `vector-2.0` for vector indexes).
354350
Previously created `vector-1.0` indexes will continue to function.
355351

356352
.Learn more about vector index provider differences

0 commit comments

Comments
 (0)