Remove option to create indexes/constraints with index provider (#1304)

Author: JPryce-Aklundh

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

@@ -109,6 +109,16 @@ MERGE (a {foo:1})-[:T]->(b {foo:a.foo})
 a|
 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.
 
+a|
+label:functionality[]
+label:removed[]
+[source, cypher, role="noheader"]
+----
+CREATE ... INDEX ... OPTIONS { indexProvider: ... }
+CREATE ... CONSTRAINTS ... OPTIONS { indexProvider: ... }
+----
+| Specifying an index provider in the `OPTIONS` map when creating an index or constraint is no longer supported.
+
 |===
 
 

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

@@ -214,7 +214,9 @@ Instad an informational notification is returned.
 Creating a text index can be done with the `CREATE TEXT INDEX` command.
 Note that the index name must be unique.
 
-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).
+Text indexes have no supported index configuration.
+
+See xref:indexes/search-performance-indexes/managing-indexes.adoc#text-indexes-trigram-indexes[Trigram indexing] for information about how text indexes process `STRING` values.
 
 [[text-indexes-supported-predicates]]
 [discrete]
@@ -287,7 +289,7 @@ Text indexes are only used for exact query matches. To perform approximate match
 [[text-indexes-trigram-indexes]]
 ==== Trigram indexing
 
-The default text index provider, `text-2.0`, uses trigram indexing.
+Text indexes uses trigram indexing.
 This means that `STRING` values are indexed into overlapping trigrams, each containing three Unicode code points.
 For example, the word `"developer"` would be indexed by the following trigrams: `["dev", "eve", "vel", "elo", "lop", "ope", "per"]`.
 

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

@@ -68,8 +68,6 @@ A vector index allows you to retrieve a neighborhood of nodes or relationships b
 
 A vector index is a single-label, single-property index for nodes or a single-relationship-type, single-property index for relationships.
 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.
-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.
-For more information, see xref:indexes/semantic-indexes/vector-indexes.adoc#vector-index-providers[].
 
 A vector index is created by using the `CREATE VECTOR INDEX [index_name]` command.
 It is recommended to give the index a name when it is created.
@@ -347,10 +345,8 @@ DROP INDEX moviePlots
 [[vector-index-providers]]
 == Vector index providers for compatibility
 
-As of Neo4j 5.18, the default index provider is `vector-2.0`.
-As of Neo4j 5.26, it is no longer possible to specify an index provider when creating indexes.
-Instead, Neo4j selects the most performant provider (currently `vector-2.0`).
-
+It is not possible to specify an index provider when creating indexes in Cypher 25.
+Instead, Neo4j selects the most performant provider (currently `vector-2.0` for vector indexes).
 Previously created `vector-1.0` indexes will continue to function.
 
 .Learn more about vector index provider differences
@@ -381,6 +377,10 @@ Single-type, single-property index for relationships.
 | `INTEGER` between `1` and `2048` _inclusive_.
 | `INTEGER` between `1` and `4096` _inclusive_.
 
+| Indexed vector quantization and hnsw settings
+| No support.
+| Supported.
+
 | xref:indexes/semantic-indexes/vector-indexes.adoc#similarity-functions[Cosine similarity vector validity]
 | All vector components can be represented finitely in IEEE 754 *_single_* precision.