From 31f95994237e5b2ebe103656e8036cc9a29ec19e Mon Sep 17 00:00:00 2001 From: "min.wu" <50101159+whitewum@users.noreply.github.com> Date: Thu, 9 Sep 2021 10:08:47 +0800 Subject: [PATCH 1/2] Update 5.lookup.md --- docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md b/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md index 6b1bd6dc58e..c98f56e3798 100644 --- a/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md +++ b/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md @@ -20,7 +20,7 @@ This topic applies to native nGQL only. - If the specified property is not indexed when using the `LOOKUP` statement, Nebula Graph randomly selects one of the available indexes. - For example, the tag `player` has two properties, `name` and `age`. Both the tag `player` itself and the property `name` have indexes, but the property `age` has no indexes. When running `LOOKUP ON player WHERE player.age == 36 YIELD player.name;`, Nebula Graph randomly uses one of the indexes of the tag `player` and the property `age`. + For example, the tag `player` has two properties, `name` and `age`. Both the tag `player` itself and the property `age` have indexes, but the property `name` has no indexes. When running `LOOKUP ON player WHERE player.age == 36 YIELD player.name;`, Nebula Graph randomly uses one of the indexes of the tag `player` and the property `age`. !!! compatibility "Legacy version compatibility" From a9fe184de387bb17e798c19dc55f1e882c11adf5 Mon Sep 17 00:00:00 2001 From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com> Date: Tue, 14 Sep 2021 15:51:24 +0800 Subject: [PATCH 2/2] Update 5.lookup.md --- docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md b/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md index c98f56e3798..1299379211c 100644 --- a/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md +++ b/docs-2.0/3.ngql-guide/7.general-query-statements/5.lookup.md @@ -20,7 +20,7 @@ This topic applies to native nGQL only. - If the specified property is not indexed when using the `LOOKUP` statement, Nebula Graph randomly selects one of the available indexes. - For example, the tag `player` has two properties, `name` and `age`. Both the tag `player` itself and the property `age` have indexes, but the property `name` has no indexes. When running `LOOKUP ON player WHERE player.age == 36 YIELD player.name;`, Nebula Graph randomly uses one of the indexes of the tag `player` and the property `age`. + For example, the tag `player` has two properties, `name` and `age`. Both the tag `player` itself and the property `name` have indexes, but the property `age` has no indexes. When running `LOOKUP ON player WHERE player.age == 36 YIELD player.name;`, Nebula Graph randomly uses one of the indexes of the tag `player` and the property `name`. !!! compatibility "Legacy version compatibility"