Full-text index restrictions¶

This document holds the restrictions for full-text indexes. Please read the restrictions very carefully before using the full-text indexes. For now, full-text search has the following limitations:

1. The maximum indexing string length is 256 bytes. The part of data that exceeds 256 bytes will not be indexed.
2. Full-text index can not be applied to more than one property at a time (similar to a composite index).
3. The WHERE clause in full-text search statement LOOKUP does not support logical expressions AND and OR.
4. Full-text index can not be applied to multiple tags search.
5. Sorting for the returned results of the full-text search is not supported. Data is returned in the order of data insertion.
6. Full-text index can not search the null properties.
7. Rebuilding or altering Elasticsearch indexes is not supported at this time.
8. Pipe is not supported in the LOOKUP statement, excluding the examples in our document.
9. Full-text search only works on single terms.
10. Full-text indexes are not deleted together with the graph space.
11. Make sure that you start the Elasticsearch cluster and Nebula Graph at the same time. If not, the data writing on the Elasticsearch cluster can be incomplete.
12. Do not contain ' or \ in the vertex or edge values. If not, a error is caused in the Elasticsearch cluster storage.
13. 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.