Update 1.text-based-index-restrictions.md (#2124)

vesoft-inc · Jun 13, 2023 · 62231a3 · 62231a3
1 parent 69ab7ff
commit 62231a3
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...t-and-installation/6.deploy-text-based-index/1.text-based-index-restrictions.md b/...t-and-installation/6.deploy-text-based-index/1.text-based-index-restrictions.md
@@ -8,7 +8,7 @@ For now, full-text search has the following limitations:
 
 - Currently, full-text search supports `LOOKUP` statements only.
 
-- The full-text index name must starts with `nebula_` and can contain only numbers, lowercase letters, underscores, and strings no longer than 256 bytes.
+- The full-text index name must starts with `nebula_` and can contain only numbers, lowercase letters, and underscores.
 
 - If there is a full-text index on the tag/edge type, the tag/edge type cannot be deleted or modified.
 
@@ -30,4 +30,4 @@ For now, full-text search has the following limitations:
 
 - It may take a while for Elasticsearch to create indexes. If Nebula Graph warns no index is found, wait for the index to take effect (however, the waiting time is unknown and there is no code to check).
 
-- NebulaGraph clusters deployed with K8s do not support the full-text search feature.
+- NebulaGraph clusters deployed with K8s do not have native support for the full-text search feature. However, you can manually deploy the feature yourself.