Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 1 commit into from
Jun 13, 2023
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...t-and-installation/6.deploy-text-based-index/1.text-based-index-restrictions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.