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 b41f4032c74..e5593be5e34 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 5b840cda929..a790071cbe6 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")