fix yield in exchange (#1988) (#1997)

Co-authored-by: cooper-lzy <[email protected]>

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-clickhouse.md

@@ -306,7 +306,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-csv.md

@@ -391,7 +391,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hbase.md

@@ -336,7 +336,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-hive.md

@@ -362,7 +362,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-jdbc.md

@@ -371,7 +371,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-json.md

@@ -390,7 +390,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-kafka.md

@@ -298,7 +298,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-maxcompute.md

@@ -332,7 +332,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-mysql.md

@@ -344,7 +344,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-neo4j.md

@@ -311,7 +311,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-oracle.md

@@ -343,7 +343,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [SHOW STATS](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-orc.md

@@ -356,7 +356,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-parquet.md

@@ -357,7 +357,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-pulsar.md

@@ -307,7 +307,7 @@ You can search for `batchSuccess.<tag_name/edge_name>` in the command output to
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.

docs-2.0/nebula-exchange/use-exchange/ex-ug-import-from-sst.md

@@ -530,7 +530,7 @@ Connect to the NebulaGraph database using the client tool and import the SST fil
 Users can verify that data has been imported by executing a query in the NebulaGraph client (for example, NebulaGraph Studio). For example:
 
 ```ngql
-GO FROM "player100" OVER follow;
+LOOKUP ON player YIELD id(vertex);
 ```
 
 Users can also run the [`SHOW STATS`](../../3.ngql-guide/7.general-query-statements/6.show/14.show-stats.md) command to view statistics.