diff --git a/docs-2.0/nebula-studio/figs/st-ug-038-1.png b/docs-2.0/nebula-studio/figs/st-ug-038-1.png new file mode 100644 index 00000000000..294e3c7c374 Binary files /dev/null and b/docs-2.0/nebula-studio/figs/st-ug-038-1.png differ diff --git a/docs-2.0/nebula-studio/figs/st-ug-043-1.png b/docs-2.0/nebula-studio/figs/st-ug-043-1.png new file mode 100644 index 00000000000..bfab0db583e Binary files /dev/null and b/docs-2.0/nebula-studio/figs/st-ug-043-1.png differ diff --git a/docs-2.0/nebula-studio/figs/st-ug-044-1.png b/docs-2.0/nebula-studio/figs/st-ug-044-1.png new file mode 100644 index 00000000000..b1311dfd94a Binary files /dev/null and b/docs-2.0/nebula-studio/figs/st-ug-044-1.png differ diff --git a/docs-2.0/nebula-studio/figs/st-ug-045-1.png b/docs-2.0/nebula-studio/figs/st-ug-045-1.png new file mode 100644 index 00000000000..8e7b6d03844 Binary files /dev/null and b/docs-2.0/nebula-studio/figs/st-ug-045-1.png differ diff --git a/docs-2.0/nebula-studio/figs/st-ug-046-1.png b/docs-2.0/nebula-studio/figs/st-ug-046-1.png new file mode 100644 index 00000000000..48475aad428 Binary files /dev/null and b/docs-2.0/nebula-studio/figs/st-ug-046-1.png differ diff --git a/docs-2.0/nebula-studio/figs/st-ug-047-1.png b/docs-2.0/nebula-studio/figs/st-ug-047-1.png new file mode 100644 index 00000000000..638bcecc34d Binary files /dev/null and b/docs-2.0/nebula-studio/figs/st-ug-047-1.png differ diff --git a/docs-2.0/nebula-studio/use-console/st-ug-open-in-explore.md b/docs-2.0/nebula-studio/use-console/st-ug-open-in-explore.md index 6b95f1009fc..15ff64229e7 100644 --- a/docs-2.0/nebula-studio/use-console/st-ug-open-in-explore.md +++ b/docs-2.0/nebula-studio/use-console/st-ug-open-in-explore.md @@ -6,11 +6,9 @@ With the **Open in Explore** function, you can run nGQL statements on the **Cons To use the **Open in Explore** function, you must do a check of these: -- The version of Studio is v2.0.0 or later. +- Studio is connected to Nebula Graph. For more information, see [Connect to Nebula Graph](../deploy-connect/st-ug-connect.md). -- Studio is connected to Nebula Graph v2.x. - -- A dataset exists in the database. +- A dataset exists in the database. For more information, see [Import data](../quick-start/st-ug-import-data.md). ## Query and visualize edge data @@ -18,7 +16,7 @@ To query edge data on the **Console** page and then view the result on the **Exp 1. In the toolbar, click the **Console** tab. -2. In the **Current Graph Space** field, choose a graph space name. In this example, **mooc_actions** is chosen. +2. In the **Current Graph Space** field, choose a graph space name. In this example, **basketballplayer** is chosen. 3. In the input box, enter an nGQL statement and click the button ![Icon of Run](../figs/st-ug-008.png "Run"). @@ -29,14 +27,14 @@ To query edge data on the **Console** page and then view the result on the **Exp Here is an nGQL statement example. ```ngql - nebula> MATCH (u:user {userId: 1}) - [:action] -> (c) RETURN u.userId AS UserID, c.courseName AS Course; + nebula> GO FROM "player102" OVER serve YIELD serve._src,serve._dst; ``` !!! note For more information about the `MATCH` syntax, see [MATCH in nGQL User Guide](../../3.ngql-guide/7.general-query-statements/2.match.md). - The query result gives the edges between User 1 and the courses that he/she takes on the MOOC platform, as shown in this figure. + In the query result, you can see the start year and end year of the service team for the player whose playerId is `palyer102`. As shown below. ![The Result window shows the queried edge data, including the VIDs of the source vertex and the destination vertex](../figs/st-ug-037.png "Edge data") @@ -45,17 +43,17 @@ To query edge data on the **Console** page and then view the result on the **Exp 5. In the dialog box, configure as follows: a. Click **Edge Type**. - b. In the **Edge Type** field, enter an edge type name. In this example, `action` is used. + b. In the **Edge Type** field, enter an edge type name. In this example, `serve` is used. - c. In the **Src ID** field, choose a column name from the result table representing the VIDs of the source vertices. In this example, `UserID` is chosen. + c. In the **Src ID** field, choose a column name from the result table representing the VIDs of the source vertices. In this example, `serve._src` is chosen. - d. In the **Dst ID** field, choose a column name from the result table representing the VIDs of the destination vertices. In this example, `Course` is chosen. + d. In the **Dst ID** field, choose a column name from the result table representing the VIDs of the destination vertices. In this example, `serve._dst` is chosen. e. (Optional) If the result table contains the ranking information of the edges, in the **Rank** field, choose a column name representing the `rank` of the edges. If no ranking information exists in the result, leave the **Rank** field blank. f. When the configuration is done, click the **Import** button. - ![The dialog box for you to configure the edge data](../figs/st-ug-038.png "Configure edge data") + ![The dialog box for you to configure the edge data](../figs/st-ug-038-1.png "Configure edge data") 6. If some data exists on the board of **Explore**, choose a method to insert data: @@ -64,7 +62,7 @@ To query edge data on the **Console** page and then view the result on the **Exp When the data is inserted, you can view the visualized representation of the edge data. -![The edge data is represented on the Explore board](../figs/st-ug-044.png "Visualize edge data") +![The edge data is represented on the Explore board](../figs/st-ug-044-1.png "Visualize edge data") ## Query and visualize vertex data @@ -72,7 +70,7 @@ To query vertex data on the **Console** page and then view the result on the **E 1. In the toolbar, click the **Console** tab. -2. In the **Current Graph Space** field, choose a graph space name. In this example, **mooc_actions** is chosen. +2. In the **Current Graph Space** field, choose a graph space name. In this example, **basketballplayer** is chosen. 3. In the input box, enter an nGQL statement and click the button ![Icon of Run](../figs/st-ug-008.png "Run"). @@ -83,23 +81,23 @@ To query vertex data on the **Console** page and then view the result on the **E Here is an nGQL statement example. ```ngql - nebula> GO FROM "1" OVER action YIELD action._dst AS Course; + nebula> FETCH PROP ON player "player100" YIELD player.name; ``` - The query result gives the courses that the specified user took, as shown in this figure. + The query result gives the information of the player whose `playerId` is `player100`, as shown in this figure. - ![The Result window shows the queried vertex data](../figs/st-ug-039.png "Vertex data") + ![The Result window shows the queried vertex data](../figs/st-ug-043-1.png "Vertex data") 4. Click the **Open in Explore** button. 5. In the dialog box, configure as follows: a. Click **Vertex**. - b. In the **Vertex ID** field, choose a column name from the result table representing the VIDs of the vertices. In this example, `Course` is chosen. + b. In the **Vertex ID** field, choose a column name from the result table representing the VIDs of the vertices. In this example, `VertexID` is chosen. c. When the configuration is done, click the **Import** button. - ![The dialog box for you to configure the vertex data](../figs/st-ug-047.png "Configure vertex data") + ![The dialog box for you to configure the vertex data](../figs/st-ug-047-1.png "Configure vertex data") 6. If some data exists on the board of **Explore**, choose a method to insert data: diff --git a/docs-2.0/nebula-studio/use-console/st-ug-visualize-subgraph.md b/docs-2.0/nebula-studio/use-console/st-ug-visualize-subgraph.md index b8e0b4e2fa2..fe5e421c62f 100644 --- a/docs-2.0/nebula-studio/use-console/st-ug-visualize-subgraph.md +++ b/docs-2.0/nebula-studio/use-console/st-ug-visualize-subgraph.md @@ -4,17 +4,17 @@ With the **View Subgraphs** function, you can run a [FIND SHORTEST | ALL PATH](. ## Studio version -Studio of v2.0.0 or later versions supports this function. To update the version, see [Check updates](../about-studio/st-ug-check-updates.md). +Studio of v{{studio.release}} supports this function. To update the version, see [Check updates](../about-studio/st-ug-check-updates.md). ## Prerequisites To use the **View Subgraphs** function, you must do a check of these: -- The version of Studio is v2.0.0 or later. +- The version of Studio is v{{studio.release}} or later. -- Studio is connected to Nebula Graph v2.x. +- Studio is connected to Nebula Graph. -- A dataset exists in the database. In the example of this article, the **mooc_actions** dataset is used. For more information, see [Import data](../quick-start/st-ug-import-data.md). +- A dataset exists in the database. In the example of this article, the **basketballplayer** dataset is used. For more information, see [Import data](../quick-start/st-ug-import-data.md). ## Procedure @@ -22,7 +22,7 @@ To query the paths or subgraph on the **Console** page and then view them on the 1. In the navigation bar, click the **Console** tab. -2. In the **Current Graph Space** dropdown list, choose a graph space name. In this example, **mooc_actions** is chosen. +2. In the **Current Graph Space** dropdown list, choose a graph space name. In this example, **baskteballplayer** is chosen. 3. In the input box, enter a `FIND SHORTEST PATH`, `FIND ALL PATH`, or `GET SUBGRAPH` statement and click **Run** ![Icon of Run](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-008.png "Run"). @@ -30,18 +30,12 @@ To query the paths or subgraph on the **Console** page and then view them on the ```ngql // Run FIND ALL PATH - nebula> FIND ALL PATH FROM "1","2","4","6","42" to "History of Ecology","Neurobiology" OVER action; - - // Run FIND SHORTEST PATH - nebula> FIND SHORTEST PATH FROM "1","2","4","6","42" to "History of Ecology","Neurobiology" OVER action; - - // Run GET SUBGRAPH - nebula> GET SUBGRAPH 1 STEPS FROM "1"; + nebula> FIND ALL PATH FROM "player114" to "player100" OVER follow; ``` - Take the `FIND ALL PATH` for example, the queried result gives all the paths from the specified user vertices to the course vertices, as shown in this figure. + Take the `FIND ALL PATH` for example, query the path information as shown in this figure. - ![The result window shows the queried paths](../figs/st-ug-049.png "The queried PATHs") + ![The result window shows the queried paths](../figs/st-ug-045-1.png "The queried PATHs") 4. Click the **View Subgraphs** button. @@ -53,7 +47,7 @@ To query the paths or subgraph on the **Console** page and then view them on the When the data is inserted, you can view the visualized representation of the paths. -![The paths are represented on the Explore board](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-046.png "Visualize paths") +![The paths are represented on the Explore board](../figs/st-ug-046-1.png "Visualize paths") ## Next to do