From 5330e772731c5e1f5860157c65b9074763216643 Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Wed, 26 Jun 2024 19:36:57 +0100 Subject: [PATCH] Update modules/ROOT/pages/performance/index-configuration.adoc Co-authored-by: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com> --- modules/ROOT/pages/performance/index-configuration.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/modules/ROOT/pages/performance/index-configuration.adoc b/modules/ROOT/pages/performance/index-configuration.adoc index c7f399219..526a5fd4f 100644 --- a/modules/ROOT/pages/performance/index-configuration.adoc +++ b/modules/ROOT/pages/performance/index-configuration.adoc @@ -263,7 +263,8 @@ A token lookup index is always created over all labels or relationship types, re Token lookup indexes are introduced in 4.3, and whereas the relationship type lookup index is a new concept, the node label lookup index is not. The latter evolved from the label scan store, which has existed in various forms for a long time. -The node label lookup index provides the same functionality as the former label scan store. Still, it has additional features common to all indexes, such as the ability to be created and dropped using a non-blocking population. +The node label lookup index provides the same functionality as the former label scan store. +Still, it has additional features common to all indexes, such as the ability to be created and dropped using a non-blocking population. [[index-configuration-token-lookup-use-and-significance]] === Use and significance