Skip to content

Commit f435fb4

Browse files
drop not delete indexes
1 parent 8be7998 commit f435fb4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
:description: This page explains how to manage indexes used for search performance.
22
include::https://raw.githubusercontent.com/neo4j-graphacademy/courses/main/asciidoc/courses/cypher-indexes-constraints/ad.adoc[]
33

4-
= Create, show, and delete indexes
4+
= Create, show, and drop indexes
55

6-
This page describes how to create, list, and delete search-performance indexes.
6+
This page describes how to create, list, and drop search-performance indexes.
77
The following index types are included in this category:
88

99
* xref:indexes/search-performance-indexes/managing-indexes.adoc#create-range-index[Range indexes]
@@ -541,7 +541,7 @@ Note that the wgs-84 and 3D cartesian settings, which are not specified in this
541541
Two token lookup indexes are created by default when creating a Neo4j database (one node label lookup index and one relationship type lookup index).
542542
Only one node label and one relationship type lookup index can exist at the same time.
543543

544-
If a token lookup index has been deleted, it can be recreated with the `CREATE LOOKUP INDEX` command.
544+
If a token lookup index has been dropped, it can be recreated with the `CREATE LOOKUP INDEX` command.
545545
Note that the index name must be unique.
546546

547547
Token lookup indexes have no supported index configuration.

0 commit comments

Comments
 (0)