From fc9d8d0507485473d5bfcfd8195682e8bad9e86a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9C=B1=E6=99=93=E9=9D=92?= <86282370+izhuxiaoqing@users.noreply.github.com> Date: Fri, 3 Sep 2021 10:39:04 +0800 Subject: [PATCH 1/2] update --- docs-2.0/14.client/4.nebula-java-client.md | 4 +-- docs-2.0/14.client/5.nebula-python-client.md | 4 +-- .../about-studio/st-ug-limitations.md | 8 ++--- .../about-studio/st-ug-shortcuts.md | 4 +-- .../st-ug-what-is-graph-studio.md | 6 ++-- .../deploy-connect/st-ug-deploy.md | 31 ++++++++++--------- .../deploy-connect/st-ug-reset-connection.md | 2 +- .../quick-start/st-ug-create-schema.md | 4 +-- .../quick-start/st-ug-import-data.md | 16 ++++++---- .../quick-start/st-ug-plan-schema.md | 4 +-- 10 files changed, 45 insertions(+), 38 deletions(-) diff --git a/docs-2.0/14.client/4.nebula-java-client.md b/docs-2.0/14.client/4.nebula-java-client.md index acc2e51afff..ea08a69dab6 100644 --- a/docs-2.0/14.client/4.nebula-java-client.md +++ b/docs-2.0/14.client/4.nebula-java-client.md @@ -33,13 +33,13 @@ You have installed Java 8.0 or later versions. !!! note - We recommended that each thread use one session. If multiple threads use the same session, the performance will be reduced. + We recommend that each thread uses one session. If multiple threads use the same session, the performance will be reduced. When importing a Maven project with tools such as IDEA, set the following dependency in `pom.xml`. !!! note - `2.0.0-SNAPSHOT` indicates the daily development version that may have unknow issues. We recommend that you replace `2.0.0-SNAPSHOT` with a released version number to use a table version. + `2.0.0-SNAPSHOT` indicates the daily development version that may have unknown issues. We recommend that you replace `2.0.0-SNAPSHOT` with a released version number to use a table version. ```bash diff --git a/docs-2.0/14.client/5.nebula-python-client.md b/docs-2.0/14.client/5.nebula-python-client.md index 94b7acc4607..d81495dacfd 100644 --- a/docs-2.0/14.client/5.nebula-python-client.md +++ b/docs-2.0/14.client/5.nebula-python-client.md @@ -53,7 +53,7 @@ $ pip install nebula2-python== !!! note - To run unit tests in the development mode, install `requirements-dev.txt` instead. + To run unit tests in the development mode, install dependencies of `requirements-dev.txt`. 4. Run the following command to install Nebula Python. @@ -80,7 +80,7 @@ ok = connection_pool.init([('192.168.xx.1', 9669)], config) # Get the session from the connection pool. session = connection_pool.get_session('root', 'nebula') -# Selection a graph space. +# Select a graph space. session.execute('USE basketballplayer') # Run the SHOW TAGS statement. diff --git a/docs-2.0/nebula-studio/about-studio/st-ug-limitations.md b/docs-2.0/nebula-studio/about-studio/st-ug-limitations.md index 2640b1e3918..5579dfe3707 100644 --- a/docs-2.0/nebula-studio/about-studio/st-ug-limitations.md +++ b/docs-2.0/nebula-studio/about-studio/st-ug-limitations.md @@ -1,6 +1,6 @@ # Limitations -This article introduces the limitations of Studio. +This topic introduces the limitations of Studio. ## Nebula Graph versions @@ -17,7 +17,7 @@ This article introduces the limitations of Studio. ## Architecture -For now, Docker-based and RPM-based Studio v2.x supports x86_64 architecture only. +For now, Docker-based and RPM-based Studio v3.x supports x86_64 architecture only. ## Upload data -If you want to reset Nebula Graph, you can clear the connection and reconfigure the database +If you want to reset Nebula Graph, you can clear the connection and reconfigure the database. When the Studio is still connected to a Nebula Graph database, you can choose **setting > clear connect** at the toolbar. If the **Config Server** page is displayed on the browser, it means that Studio has successfully disconnected from the Nebula Graph database. \ No newline at end of file diff --git a/docs-2.0/nebula-studio/quick-start/st-ug-create-schema.md b/docs-2.0/nebula-studio/quick-start/st-ug-create-schema.md index 05eef9ffff1..1b2778b17c6 100644 --- a/docs-2.0/nebula-studio/quick-start/st-ug-create-schema.md +++ b/docs-2.0/nebula-studio/quick-start/st-ug-create-schema.md @@ -18,9 +18,9 @@ To create a graph schema on Studio, you must do a check of these: - A graph space is created. - !!! note +!!! note - If no graph space exists and your account has the GOD privilege, you can create a graph space on the **Console** page. For more information, see [CREATE SPACE](../../3.ngql-guide/9.space-statements/1.create-space.md). + If no graph space exists and your account has the GOD privilege, you can create a graph space on the **Console** page. For more information, see [CREATE SPACE](../../3.ngql-guide/9.space-statements/1.create-space.md). ## Create a schema with Schema diff --git a/docs-2.0/nebula-studio/quick-start/st-ug-import-data.md b/docs-2.0/nebula-studio/quick-start/st-ug-import-data.md index a233ef34e68..7bf3414425c 100644 --- a/docs-2.0/nebula-studio/quick-start/st-ug-import-data.md +++ b/docs-2.0/nebula-studio/quick-start/st-ug-import-data.md @@ -10,7 +10,7 @@ To batch import data, do a check of these: - A schema is created. -- CSV files for vertex and edge data separately are created. +- CSV files meet the demands of the Schema. - Your account has privilege of GOD, ADMIN, DBA, or USER. @@ -22,7 +22,7 @@ To batch import data, follow these steps: 2. On the **Select Space** page, choose a graph space name. In this example, **basketballplayer** is used. And then click the **Next** button. -3. On the **Upload Files** page, click the **Upload Files** button and then choose CSV files. In this example, `edge_serve.csv`, `edge_follow.csv`, `vertex_player.csv` and `vertex_team.csv` are chosen. +3. On the **Upload Files** page, click the **Upload Files** button and then choose CSV files. In this example, `edge_serve.csv`, `edge_follow.csv`, `vertex_player.csv`, and `vertex_team.csv` are chosen. !!! note @@ -39,12 +39,16 @@ To batch import data, follow these steps: a. In the **CSV Index** column, click **Mapping**. ![Click "Mapping** in the CSV Index column](../figs/st-ug-032-1.png "Choose the source for vertexId") - b. In the dialog box, choose a column from the CSV file. In this example, the only one cloumn of `vertex_player.csv` is chosen to generate VIDs representing users and the `playerID` column of `vertex_player.csv` is chosen to generate VIDs representing courses. + b. In the dialog box, choose a column from the CSV file. In this example, the only one cloumn of `vertex_player.csv` is chosen to generate VIDs representing players and the `playerID` column of `vertex_player.csv` is chosen to generate VIDs representing players. + + !!! Note + + In the same graph space, the VID is always unique and cannot be repeated. For VID information, see [VID](../../1.introduction/3.vid.md) "Click to enter the Nebula Graph Manual". 8. In the **TAG 1** section, do these operations: a. In the **TAG** drop-down list, choose a tag name. In this example, **player** is used for the `vertex_player.csv` file, and **team** is used for the `vertex_team.csv` file. - b. In the property list, click **Mapping** to choose a data column from the CSV file as the value of a property. In this example,for the **player** tag, choose **Column 1** for the `age` property and set its type to **int**. And choose **Column 2** for the `name` property and set its type to **string**. + b. In the property list, click **Mapping** to choose a data column from the CSV file as the value of a property. In this example, for the **player** tag, choose **Column 1** for the `age` property and set its type to **int**. And choose **Column 2** for the `name` property and set its type to **string**. ![Data source for the course vertices](../figs/st-ug-033-1.png "Choose data source for tag properties") @@ -57,7 +61,7 @@ To batch import data, follow these steps: 12. In the **Type** drop-down list, choose an edge type name. In this example, **follow** is chosen. -13. In the property list, click **Mapping** to choose a column from the `edge_follow.csv` file as values of a property for the edges. **srcId** and **dstId** are the VIDs of the source vertex and destination vertex of an edge. In this example, **srcId** must be set to the VIDs of the player and **dstId** must be set to the VIDs of another player. **rank** is optional. +13. In the property list, click **Mapping** to choose a column from the `edge_follow.csv` file as values of a property for the edges. **srcId** and **dstId** are the VIDs of the source vertex and destination vertex of an edge. In this example, **srcId** must be set to the VIDs of the player and **dstId** must be set to the VIDs of another player. **Rank** is optional. ![Data source for the action edges](../figs/st-ug-034-1.png "Choose data source for the edge type properties") @@ -68,4 +72,4 @@ To batch import data, follow these steps: ## Next to do -When the data are imported to Nebula Graph v2.x, you can [query graph data](st-ug-explore.md). +When the data are imported to v{{nebula.release}}, you can [query graph data](st-ug-explore.md). diff --git a/docs-2.0/nebula-studio/quick-start/st-ug-plan-schema.md b/docs-2.0/nebula-studio/quick-start/st-ug-plan-schema.md index f75922f3609..2cf8362d656 100644 --- a/docs-2.0/nebula-studio/quick-start/st-ug-plan-schema.md +++ b/docs-2.0/nebula-studio/quick-start/st-ug-plan-schema.md @@ -19,6 +19,6 @@ This table gives all the essential elements of the schema. | Edge type | **serve** | - `start_year` （`int`）
- `end_year` （`int`） | Represent the players behavior.
This behavior connects the player to the team, and the direction is from player to team. | | Edge type | **follow** | - `degree`（`int`） | Represent the players behavior.
This behavior connects the player to the player, and the direction is from a player to a player. | -This figure shows the relationship (**action**) between a **user** and a **course** on the MOOC platform. +This figure shows the relationship (**serve**/**follow**) between a **player** and a **team**. -![Users take actions on a MOOC platform](../figs/st-ug-006-1.png "Relationship between users and courses in the example dataset") +![The relationship between players and between players and teams](../figs/st-ug-006-1.png "Relationship between players and teams in the example dataset") From 67c8c0c0a00ea7c273789de3f8ff21020924a169 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9C=B1=E6=99=93=E9=9D=92?= <86282370+izhuxiaoqing@users.noreply.github.com> Date: Fri, 3 Sep 2021 14:32:14 +0800 Subject: [PATCH 2/2] update --- .../manage-schema/st-ug-crud-edge-type.md | 20 +++++++++---------- .../manage-schema/st-ug-crud-index.md | 7 +++---- .../manage-schema/st-ug-crud-space.md | 13 ++++++------ .../manage-schema/st-ug-crud-tag.md | 12 +++++------ .../st-ug-config-server-errors.md | 2 +- .../troubleshooting/st-ug-faq.md | 13 ++++++------ .../use-console/st-ug-open-in-explore.md | 4 ++++ .../use-console/st-ug-visualize-subgraph.md | 4 ++++ 8 files changed, 40 insertions(+), 35 deletions(-) diff --git a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-edge-type.md b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-edge-type.md index a71b937c38d..5527d720154 100644 --- a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-edge-type.md +++ b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-edge-type.md @@ -1,6 +1,6 @@ # Operate edge types -After a graph space is created in Nebula Graph, you can create edge types. With Studio, you can choose to use the **Console** page or the **Schema** page to create, retrieve, update, or delete edge types. This article only introduces how to use the **Schema** page to operate edge types in a graph space. +After a graph space is created in Nebula Graph, you can create edge types. With Studio, you can choose to use the **Console** page or the **Schema** page to create, retrieve, update, or delete edge types. This topic introduces how to use the **Schema** page to operate edge types in a graph space only. ## Studio version @@ -28,27 +28,25 @@ To create an edge type on the **Schema** page, follow these steps: 5. On the **Create** page, do these settings: - a. **Name**: Specify an appropriate name for the edge type. In this example, `serve` is used. + - **Name**: Specify an appropriate name for the edge type. In this example, `serve` is used. - b. (Optional) If necessary, under the name, click the **Comment** to input content. + - (Optional) If necessary, under the name, click the **Comment** to input content. - c. (Optional) If necessary, in the upper left corner of the **Define Properties** panel, click the check box to expand the panel and do these settings: + - (Optional) If necessary, in the upper left corner of the **Define Properties** panel, click the check box to expand the panel and do these settings: - - To define a property: Enter a property name, a data type, and a default value. + - To define a property: Enter a property name, a data type, and a default value. - - To add multiple properties: Click the **Add Property** button and define more properties. + - To add multiple properties: Click the **Add Property** button and define more properties. - - To cancel a defined property: Besides the **Defaults** column, click the button ![Icon of deletion](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-020.png "Cancel"). + - To delete a defined property: Besides the **Defaults** column, click the button ![Icon of deletion](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-020.png "Cancel"). - d. (Optional) If no index is set for the edge type, you can set the TTL configuration: In the upper left corner of the **Set TTL** panel, click the check box to expand the panel, and configure `TTL_COL` and `TTL_ DURATION`. For more information about both parameters, see [TTL configuration](../../3.ngql-guide/8.clauses-and-options/ttl-options.md "Click to go to Nebula Graph website"). + - (Optional) If no index is set for the edge type, you can set the TTL configuration: In the upper left corner of the **Set TTL** panel, click the check box to expand the panel, and configure `TTL_COL` and `TTL_ DURATION`. For more information about both parameters, see [TTL configuration](../../3.ngql-guide/8.clauses-and-options/ttl-options.md "Click to go to Nebula Graph website"). 6. When the preceding settings are completed, in the **Equivalent to the following nGQL statement** panel, you can see the nGQL statement equivalent to these settings. ![Define properties of the `action` edge type](../figs/st-ug-027-1.png "Define an edge type") -7. Confirm the settings and then click the **+ Create** button. - -When the edge type is created successfully, the **Define Properties** panel shows all its properties on the list. +7. Confirm the settings and then click the **+ Create** button. When the edge type is created successfully, the **Define Properties** panel shows all its properties on the list. ## Edit an edge type diff --git a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-index.md b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-index.md index 8b23fd48784..bdeaf1f0a48 100644 --- a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-index.md +++ b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-index.md @@ -1,6 +1,6 @@ # Operate Indexes -You can create an index for a Tag and/or an Edge type. An index lets traversal start from vertices or edges with the same property and it can make a query more efficient. You can create two index types: Tag Index and Edge type Index. With Studio, you can use the **Console** page or the **Schema** page to create, retrieve, and delete indexes. This article introduces how to use the **Schema** page to operate an index. +You can create an index for a Tag and/or an Edge type. An index lets traversal start from vertices or edges with the same property and it can make a query more efficient. You can create two index types: Tag Index and Edge type Index. With Studio, you can use the **Console** page or the **Schema** page to create, retrieve, and delete indexes. This topic introduces how to use the **Schema** page to operate an index only. !!! note @@ -42,12 +42,11 @@ To create an index on the **Schema** page, follow these steps: e. **Comment**: The remarks of a certain property or the index itself. The maximum length is 256 bytes. By default, there will be no comments on an index. But in this example, `follow_index` is used. - When the settings are done, the **Equivalent to the following nGQL statement** panel shows the statement equivalent to the settings. +6. When the settings are done, the **Equivalent to the following nGQL statement** panel shows the statement equivalent to the settings. ![A page for index creation](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-030.png "Create an index") -6. Confirm the settings and then click the **+ Create** button. - When an index is created, the index list shows the new index. +7. Confirm the settings and then click the **+ Create** button. When an index is created, the index list shows the new index. ## View indexes diff --git a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-space.md b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-space.md index 8469567399a..a4e2e00a736 100644 --- a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-space.md +++ b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-space.md @@ -23,15 +23,15 @@ To create a graph space on the **Schema** page, follow these steps: 2. On the **Graph Space List** page, click the **+ Create** button. 3. On the **Create** page, do these settings: - a. **Name**: Specify a name to the new graph space. In this example, `basketballplayer` is used. The name must be distinct in the database. The name cannot be used keywords or reserved keywords as identifiers. For more information, see [keywords](../../3.ngql-guide/1.nGQL-overview/keywords-and-reserved-words.md). + - **Name**: Specify a name to the new graph space. In this example, `basketballplayer` is used. The name must be distinct in the database. The name cannot be used keywords or reserved keywords as identifiers. For more information, see [keywords](../../3.ngql-guide/1.nGQL-overview/keywords-and-reserved-words.md). - b. **Vid type**: The data types of VIDs are restricted to `FIXED_STRING()` or `INT64`; a graph space can only select one VID type, `FIXED_STRING(32)` is used. For more information, see [VID](../../1.introduction/3.vid.md). + - **Vid type**: The data types of VIDs are restricted to `FIXED_STRING()` or `INT64`. A graph space can only select one VID type. In this example, `FIXED_STRING(32)` is used. For more information, see [VID](../../1.introduction/3.vid.md). - c. **Comment**: The remarks of a certain property or the space itself. The maximum length is 256 bytes. By default, there will be no comments on a space. But in this example, `Statistics of basketball players` is used. + - **Comment**: The remarks of a certain property or the space itself. The maximum length is 256 bytes. By default, there will be no comments on a space. But in this example, `Statistics of basketball players` is used. - d. **Optional Parameters**: Set `partition_num`, `replica_factor`. In this example, these parameters are set to `100` and `1` separately. For more information, see [`CREATE SPACE` syntax](../../3.ngql-guide/9.space-statements/1.create-space.md "Click to go to the Nebula Graph website"). + - **Optional Parameters**: Set the values of `partition_num` and `replica_factor` respectively. In this example, these parameters are set to `100` and `1` respectively. For more information, see [`CREATE SPACE` syntax](../../3.ngql-guide/9.space-statements/1.create-space.md "Click to go to the Nebula Graph website"). - In the **Equivalent to the following nGQL statement** panel, you can see the statement equivalent to the preceding settings. + In the **Equivalent to the following nGQL statement** panel, you can see the statement equivalent to the preceding settings. ```bash CREATE SPACE basketballplayer (partition_num = 100, replica_factor = 1, vid_type = FIXED_STRING(32)) COMMENT = "Statistics of basketball players" @@ -53,8 +53,7 @@ To delete a graph space on the **Schema** page, follow these steps: 2. In the graph space list, find a graph space and then the button ![Icon of deletion](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-017.png "Delete") in the **Operations** column. ![Graph space list with the graph space to be deleted](./../figs/st-ug-029.png) -3. On the dialog box, confirm the information and then click the **OK** button. - When the graph space is deleted successfully, it is removed from the graph space list. +3. On the dialog box, confirm the information and then click the **OK** button. When the graph space is deleted successfully, it is removed from the **graph space list**. ## Next to do diff --git a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-tag.md b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-tag.md index 5c836280ec1..e374cf05c98 100644 --- a/docs-2.0/nebula-studio/manage-schema/st-ug-crud-tag.md +++ b/docs-2.0/nebula-studio/manage-schema/st-ug-crud-tag.md @@ -1,6 +1,6 @@ # Operate tags -After a graph space is created in Nebula Graph, you can create tags. With Studio, you can use the **Console** page or the **Schema** page to create, retrieve, update, or delete tags. This article only introduces how to use the **Schema** page to operate tags in a graph space. +After a graph space is created in Nebula Graph, you can create tags. With Studio, you can use the **Console** page or the **Schema** page to create, retrieve, update, or delete tags. This topic introduces how to use the **Schema** page to operate tags in a graph space only. ## Studio version @@ -28,7 +28,7 @@ To create a tag on the **Schema** page, follow these steps: 5. On the **Create** page, do these settings: - a. **Name**: Specify an appropriate name for the tag. In this example, `course` is specified. + a. **Name**: Specify an appropriate name for the tag. In this example, `player` and `team` are specified. b. (Optional) If necessary, in the upper left corner of the **Define Properties** panel, click the check box to expand the panel and do these settings: @@ -44,9 +44,7 @@ To create a tag on the **Schema** page, follow these steps: ![Define properties of the `course` tag](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-028.png "Define a tag") -7. Confirm the settings and then click the **+ Create** button. - -When the tag is created successfully, the **Define Properties** panel shows all its properties on the list. +7. Confirm the settings and then click the **+ Create** button. When the tag is created successfully, the **Define Properties** panel shows all its properties on the list. ## Edit a tag @@ -62,7 +60,7 @@ To edit a tag on the **Schema** page, follow these steps: 5. On the **Edit** page, do these settings: - - To edit a Comment: Click **Edit** under the Name. + - To edit a Comment: Click **Edit** under the **Name**. - To edit a property: On the **Define Properties** panel, find a property, click **Edit**, and then change the data type or the default value. @@ -95,6 +93,8 @@ To delete a tag on the **Schema** page, follow these steps: 4. Click the **Tag** tab, find a tag and then the button ![Icon of deletion](https://docs-cdn.nebula-graph.com.cn/nebula-studio-docs/st-ug-017.png) in the **Operations** column. +5. CLick **OK**. + ## Next to do After the tag is created, you can use the **Console** page to insert vertex data one by one manually or use the **Import** page to bulk import vertex data. diff --git a/docs-2.0/nebula-studio/troubleshooting/st-ug-config-server-errors.md b/docs-2.0/nebula-studio/troubleshooting/st-ug-config-server-errors.md index 2670d3f3361..c2cb06fd0db 100644 --- a/docs-2.0/nebula-studio/troubleshooting/st-ug-config-server-errors.md +++ b/docs-2.0/nebula-studio/troubleshooting/st-ug-config-server-errors.md @@ -26,7 +26,7 @@ Check Nebula Graph service status. Regarding the operation of viewing services: - If you use Nebula Graph deployed by Docker Compose and RPM, refer to the [Nebula Graph service status and ports](../deploy-connect/st-ug-deploy.md). -If the Nebula Graph service is normal, proceed to Step4 to continue troubleshooting. Otherwise, please restart Nebula Graph service. +If the Nebula Graph service is normal, proceed to Step 4 to continue troubleshooting. Otherwise, please restart Nebula Graph service. !!! Note diff --git a/docs-2.0/nebula-studio/troubleshooting/st-ug-faq.md b/docs-2.0/nebula-studio/troubleshooting/st-ug-faq.md index 8c0a5e70ae2..692aa0ef395 100644 --- a/docs-2.0/nebula-studio/troubleshooting/st-ug-faq.md +++ b/docs-2.0/nebula-studio/troubleshooting/st-ug-faq.md @@ -1,9 +1,10 @@ # FAQ -!!! faq "Why can't I use a function?" +**Why can't I use a function?** - If you find that a function cannot be used, it is recommended to troubleshoot the problem according to the following steps: - 1. Confirm that Nebula Graph is the latest version. If you use Docker Compose to deploy the Nebula Graph database, it is recommended to run `docker-compose pull && docker-compose up -d` to pull the latest Docker image and start the container. - 2. Confirm that Studio is the latest version. For more information, refer to [check updates](../about-studio/st-ug-check-updates.md). - 3. Search the [nebula forum](https://discuss.nebula-graph.io/), [nebula](https://github.com/vesoft-inc/nebula) and [nebula-studio](https://github.com/vesoft-inc/nebula-studio) projects on the GitHub to confirm if there are already similar problems. - 4. If none of the above steps solve the problem, you can submit a problem on the forum. \ No newline at end of file +If you find that a function cannot be used, it is recommended to troubleshoot the problem according to the following steps: + +1. Confirm that Nebula Graph is the latest version. If you use Docker Compose to deploy the Nebula Graph database, it is recommended to run `docker-compose pull && docker-compose up -d` to pull the latest Docker image and start the container. +2. Confirm that Studio is the latest version. For more information, refer to [check updates](../about-studio/st-ug-check-updates.md). +3. Search the [nebula forum](https://discuss.nebula-graph.io/), [nebula](https://github.com/vesoft-inc/nebula) and [nebula-studio](https://github.com/vesoft-inc/nebula-studio) projects on the GitHub to confirm if there are already similar problems. +4. If none of the above steps solve the problem, you can submit a problem on the forum. 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 15ff64229e7..1e95cfa6521 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 @@ -2,6 +2,10 @@ With the **Open in Explore** function, you can run nGQL statements on the **Console** page to query vertex or edge data and then view the result on the **Explore** page in a visualized way. +## Supported versions + +Studio of v{{ studio.release }} or later versions supports this function. For more information, see [check updates](../about-studio/st-ug-check-updates.md). + ## Prerequisites To use the **Open in Explore** function, you must do a check of these: 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 fe5e421c62f..a56e9359840 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 @@ -16,6 +16,10 @@ To use the **View Subgraphs** function, you must do a check of these: - 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). +!!! Note + + Users can view subgraphs online in [Studio](https://playground.nebula-graph.com.cn/explore). + ## Procedure To query the paths or subgraph on the **Console** page and then view them on the **Explore** page, follow these steps: