diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/3.graph-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/3.graph-service.md index c1bfe970acb..6ff3b73f000 100644 --- a/docs-2.0/1.introduction/3.nebula-graph-architecture/3.graph-service.md +++ b/docs-2.0/1.introduction/3.nebula-graph-architecture/3.graph-service.md @@ -8,13 +8,13 @@ Graph Service is used to process the query. It has four submodules: Parser, Vali After a query is sent to Graph Service, it will be processed by the following four submodules: -1. **Parser**：Performs lexical analysis and syntax analysis. +1. **Parser**: Performs lexical analysis and syntax analysis. -2. **Validator**：Validates the statements. +2. **Validator**: Validates the statements. -3. **Planner**：Generates and optimizes the execution plans. +3. **Planner**: Generates and optimizes the execution plans. -4. **Executor**：Executes the operators. +4. **Executor**: Executes the operators. ## Parser diff --git a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md index 92de3a4e154..d2b164a62a2 100644 --- a/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md +++ b/docs-2.0/1.introduction/3.nebula-graph-architecture/4.storage-service.md @@ -152,7 +152,7 @@ Nebula Graph uses a **static Hash** strategy to shard data through a modulo oper When inserting into Nebula Graph, vertices and edges are distributed across different partitions. And the partitions are located on different machines. The number of partitions is set in the CREATE SPACE statement and cannot be changed afterward. -If certain vertices need to be placed on the same partition (i.e., on the same machine), see [Formula/code](https://github.com/vesoft-inc/nebula-common/blob/master/src/common/clients/meta/MetaClient.cpp)。 +If certain vertices need to be placed on the same partition (i.e., on the same machine), see [Formula/code](https://github.com/vesoft-inc/nebula-common/blob/master/src/common/clients/meta/MetaClient.cpp). The following code will briefly describe the relationship between VID and partition. @@ -234,7 +234,7 @@ The Listener is designed for **storage horizontal scaling**. It takes a long tim The Listener will write into the command WAL. If the leader finds a command of `add learner` when writing the WAL, it will add the listener to its peers and mark it as a Listener. Listeners cannot join the quorum votes, but logs will still be sent to them as usual. Listeners themselves will not initiate elections. -Raft listener can write the data into Elasticsearch cluster after receiving them from Learner to implement full-text search. For more information, see [Deploy Raft Listener](../../4.deployment-and-installation/6.deploy-text-based-index/3.deploy-listener.md)。 +Raft listener can write the data into Elasticsearch cluster after receiving them from Learner to implement full-text search. For more information, see [Deploy Raft Listener](../../4.deployment-and-installation/6.deploy-text-based-index/3.deploy-listener.md). ### Transfer Leadership @@ -258,4 +258,4 @@ Storage Service is a Raft-based distributed architecture, which has certain diff - Storage Service can access the file system directly. While the applications of HDFS (such as HBase) have to access HDFS before the file system, which requires more RPC times. -In a word，Storage Service is more lightweight with some functions simplified and its architecture is simpler than HDFS, which can effectively improve the read and write performance of a smaller block of data. +In a word, Storage Service is more lightweight with some functions simplified and its architecture is simpler than HDFS, which can effectively improve the read and write performance of a smaller block of data. diff --git a/docs-2.0/1.introduction/3.vid.md b/docs-2.0/1.introduction/3.vid.md index 99a1d521fb8..fd4d83d44c7 100644 --- a/docs-2.0/1.introduction/3.vid.md +++ b/docs-2.0/1.introduction/3.vid.md @@ -14,7 +14,7 @@ In Nebula Graph, a vertex is uniquely identified by its ID, which is called a VI + A VID is the unique identifier of an entity, like a person's ID card number. A tag means the type of an entity, such as driver, and boss. Different tags define two groups of different properties, such as driving license number, driving age, order amount, order taking alt, and job number, payroll, debt ceiling, business phone number. - + When two `INSERT` statements (neither uses a parameter of `IF NOT EXISTS`) with the same VID and tag are operated at the same time，the latter `INSERT` will overwrite the former. + + When two `INSERT` statements (neither uses a parameter of `IF NOT EXISTS`) with the same VID and tag are operated at the same time, the latter `INSERT` will overwrite the former. + When two `INSERT` statements with the same VID but different tags, like `TAG A` and `TAG B`, are operated at the same time, the operation of `Tag A` will not affect `Tag B`. diff --git a/docs-2.0/14.client/3.nebula-cpp-client.md b/docs-2.0/14.client/3.nebula-cpp-client.md index dc4d5ec4583..c657f4c4976 100644 --- a/docs-2.0/14.client/3.nebula-cpp-client.md +++ b/docs-2.0/14.client/3.nebula-cpp-client.md @@ -66,7 +66,7 @@ $ make -j{N} ``` -6. Install Nebula CPP。 +6. Install Nebula CPP. ```bash $ sudo make install @@ -90,9 +90,9 @@ Compile the CPP file to an executable file, then you can use it. The following s $ LIBRARY_PATH=:$LIBRARY_PATH g++ -std=c++11 SessionExample.cpp -I -lnebula_graph_client -o session_example ``` - - `library_folder_path`：The storage path of the Nebula Graph dynamic libraries. The default path is `/usr/local/nebula/lib64`. + - `library_folder_path`: The storage path of the Nebula Graph dynamic libraries. The default path is `/usr/local/nebula/lib64`. - - `include_folder_path`：The storage of the Nebula Graph header files. The default path is `/usr/local/nebula/include`. + - `include_folder_path`: The storage of the Nebula Graph header files. The default path is `/usr/local/nebula/include`. For example: 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 54f7cab7d75..94b7acc4607 100644 --- a/docs-2.0/14.client/5.nebula-python-client.md +++ b/docs-2.0/14.client/5.nebula-python-client.md @@ -39,7 +39,7 @@ $ pip install nebula2-python== $ git clone https://github.com/vesoft-inc/nebula-python.git ``` -2. Change the working directory to nebula-python。 +2. Change the working directory to nebula-python. ```bash $ cd nebula-python diff --git a/docs-2.0/19.FAQ/0.FAQ.md b/docs-2.0/19.FAQ/0.FAQ.md index a796db3fbbc..a7633413c02 100644 --- a/docs-2.0/19.FAQ/0.FAQ.md +++ b/docs-2.0/19.FAQ/0.FAQ.md @@ -13,7 +13,7 @@ If the solutions described in this topic cannot solve the problem, ask for help ???+ faq "Some errors in this manula" 1. Click the `pencil` button at the top right side of this page. - 2. Use markdown to fix this error。Then "Commit changes" at the bottom, which will start a Github pull request. + 2. Use markdown to fix this error. Then "Commit changes" at the bottom, which will start a Github pull request. 3. Sign the [CLA](../15.contribution/how-to-contribute.md). This pull request (and the fix) will be merged after to reviewer's accept. @@ -122,17 +122,17 @@ If the solutions described in this topic cannot solve the problem, ask for help ???+ faq "Storage Error E_RPC_FAILURE" - Storaged returns too many data back to graphd。Possible solutions: + Storaged returns too many data back to graphd. Possible solutions: 1. Check whether storaged is Out-of-memory. (`dmesg| grep nebula`). - 2. In `nebula-graphd.conf`, modify or add the item `--storage_client_timeout_ms=60000` to change the timeout(ms)。 + 2. In `nebula-graphd.conf`, modify or add the item `--storage_client_timeout_ms=60000` to change the timeout(ms). 3. Modify your nGQL to reduce full scans (including limit sentence). 4. Use better hardware (NVMe, more memory). - 5. retry。 + 5. retry. ???+ faq "The leader has changed. Try again later" - Known Issue. Just retry 1 to N times, where N is the partition number。The reason is that meta client needs some heartbeats to update or errors to trigger the new leader information. + Known Issue. Just retry 1 to N times, where N is the partition number. The reason is that meta client needs some heartbeats to update or errors to trigger the new leader information. ???+ faq "How to stop a slow query" @@ -163,17 +163,17 @@ If the solutions described in this topic cannot solve the problem, ask for help ???+ faq "How to scale out or scale in?" - Nebula Graph {{ nebula.release }} doesn't provide any commands or tools to support automatic scale out/in. You can do by the following steps： + Nebula Graph {{ nebula.release }} doesn't provide any commands or tools to support automatic scale out/in. You can do by the following steps: - 1. metad： metad can not be scaled out or scale in. The process can't be moved to a new machine. You can not add a new metad process to the service. + 1. metad: metad can not be scaled out or scale in. The process can't be moved to a new machine. You can not add a new metad process to the service. - 2. Scale in graphd ： remove graphd from client's code. Close this graphd process. + 2. Scale in graphd : remove graphd from client's code. Close this graphd process. - 3. Scale out graphd： prepare graphd's binary and config files in the new host. Modify the config files and add all existing metad's addresses. Then start the new graphd process. + 3. Scale out graphd: prepare graphd's binary and config files in the new host. Modify the config files and add all existing metad's addresses. Then start the new graphd process. - 4. Scale in storaged：（All spaces' replace number must be greater than 1），ref to [Balance remove command](../8.service-tuning/load-balance.md#storage_1). After the command finish, stop this storaged process. + 4. Scale in storaged: （All spaces' replace number must be greater than 1）, ref to [Balance remove command](../8.service-tuning/load-balance.md#storage_1). After the command finish, stop this storaged process. - 5. Scale out storaged：（All spaces' replace number must be greater than 1）prepare storaged's binary and config files in the new host, Modify the config files and add all existing metad's adDresses. Then start the new storaged process. + 5. Scale out storaged: （All spaces' replace number must be greater than 1）prepare storaged's binary and config files in the new host, Modify the config files and add all existing metad's adDresses. Then start the new storaged process. You may also need to run [Balance Data and Balance leader](../8.service-tuning/load-balance) after scaling in/out storaged. diff --git a/docs-2.0/2.quick-start/1.quick-start-workflow.md b/docs-2.0/2.quick-start/1.quick-start-workflow.md index c7d6c4f2198..4dfebf98fb5 100644 --- a/docs-2.0/2.quick-start/1.quick-start-workflow.md +++ b/docs-2.0/2.quick-start/1.quick-start-workflow.md @@ -25,31 +25,31 @@ Users can quickly deploy and use Nebula Graph in the following steps. diff --git a/docs-2.0/2.quick-start/2.install-nebula-graph.md b/docs-2.0/2.quick-start/2.install-nebula-graph.md index 73b63cf7cc5..3771365834c 100644 --- a/docs-2.0/2.quick-start/2.install-nebula-graph.md +++ b/docs-2.0/2.quick-start/2.install-nebula-graph.md @@ -1,4 +1,4 @@ -# Step 1：Install Nebula Graph +# Step 1: Install Nebula Graph {% include "/source_install-nebula-graph-by-rpm-or-deb.md" %} diff --git a/docs-2.0/2.quick-start/3.connect-to-nebula-graph.md b/docs-2.0/2.quick-start/3.connect-to-nebula-graph.md index cea473ebbd5..9a07a1262a9 100644 --- a/docs-2.0/2.quick-start/3.connect-to-nebula-graph.md +++ b/docs-2.0/2.quick-start/3.connect-to-nebula-graph.md @@ -1,4 +1,4 @@ -# Step 3：Connect to Nebula Graph +# Step 3: Connect to Nebula Graph {% include "/source_connect-to-nebula-graph.md" %} diff --git a/docs-2.0/2.quick-start/4.nebula-graph-crud.md b/docs-2.0/2.quick-start/4.nebula-graph-crud.md index a7b735f8660..1708ce3b930 100644 --- a/docs-2.0/2.quick-start/4.nebula-graph-crud.md +++ b/docs-2.0/2.quick-start/4.nebula-graph-crud.md @@ -1,4 +1,4 @@ -# Step 4：Use nGQL（CRUD） +# Step 4: Use nGQL（CRUD） This topic will describe the basic CRUD operations in Nebula Graph. diff --git a/docs-2.0/2.quick-start/5.start-stop-service.md b/docs-2.0/2.quick-start/5.start-stop-service.md index 771bfc38c86..d285815d892 100644 --- a/docs-2.0/2.quick-start/5.start-stop-service.md +++ b/docs-2.0/2.quick-start/5.start-stop-service.md @@ -1,4 +1,4 @@ -# Step 2：Manage Nebula Graph Service +# Step 2: Manage Nebula Graph Service {% include "/source_manage-service.md" %} diff --git a/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md b/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md index 39512926519..fe533f52c0f 100644 --- a/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md +++ b/docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md @@ -38,6 +38,6 @@ nebula> DROP TAG test; In nGQL, there is no such statement to drop a certain tag of a vertex with the given name. * In openCypher, you can use the statement `REMOVE v:LABEL` to drop the tag `LABLE` of the vertex `v`. - * In nGQL，after `CREATE TAG` and `INSERT VERTEX`, you can add a `TAG` on the vertex. But there is no way to drop the `TAG` afterward. + * In nGQL, after `CREATE TAG` and `INSERT VERTEX`, you can add a `TAG` on the vertex. But there is no way to drop the `TAG` afterward. We recommend you to add a field to identify the logical deletion in the schema. For example, add `removed` to the schema of each tag. diff --git a/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md b/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md index da21482c84c..93548795503 100644 --- a/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md +++ b/docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md @@ -39,7 +39,7 @@ prop_value_list: `INSERT VERTEX` and `CREATE` have different semantics. - The semantics of `INSERT VERTEX` is closer to that of INSERT in NoSQL (key-value), or `UPSERT` (`UPDATE` or `INSERT`) in SQL. - - When two INSERT statements (neither uses `IF NOT EXISTS`) with the same `VID` and `TAG` are operated at the same time，the latter INSERT will overwrite the former. + - When two INSERT statements (neither uses `IF NOT EXISTS`) with the same `VID` and `TAG` are operated at the same time, the latter INSERT will overwrite the former. - When two INSERT statements with the same `VID` but different `TAGS` are operated at the same time, the operation of different tags will not overwrite each other. Examples are as follows. diff --git a/docs-2.0/3.ngql-guide/3.data-types/6.list.md b/docs-2.0/3.ngql-guide/3.data-types/6.list.md index 9e2b579d1d9..dc5a72899b5 100644 --- a/docs-2.0/3.ngql-guide/3.data-types/6.list.md +++ b/docs-2.0/3.ngql-guide/3.data-types/6.list.md @@ -28,7 +28,7 @@ The index of nGQL supports queries from front to back, starting from 0. 0 means - Return empty if the index is out of bounds, while return normally if the index is within the bound. - Return empty if `M`≥`N`. - - When querying a single element, if `M` is null，return `BAD_TYPE`. When conducting a range query, if `M` or `N` is null, return `null`. + - When querying a single element, if `M` is null, return `BAD_TYPE`. When conducting a range query, if `M` or `N` is null, return `null`. ## Examples diff --git a/docs-2.0/3.ngql-guide/5.operators/1.comparison.md b/docs-2.0/3.ngql-guide/5.operators/1.comparison.md index 99c047b3a90..aabee9ac329 100644 --- a/docs-2.0/3.ngql-guide/5.operators/1.comparison.md +++ b/docs-2.0/3.ngql-guide/5.operators/1.comparison.md @@ -28,7 +28,7 @@ The result of the comparison operation is `true` or `false`. - Comparability between values of different types is often undefined. The result could be `NULL` or others. - - `EMPTY` is currently used only for checking，and does not support functions or operations such as `GROUP BY`, `count()`, `sum()`, `max()`, `hash()`, ` collect()`, `+` or `*`. + - `EMPTY` is currently used only for checking, and does not support functions or operations such as `GROUP BY`, `count()`, `sum()`, `max()`, `hash()`, ` collect()`, `+` or `*`. ## OpenCypher compatibility diff --git a/docs-2.0/7.data-security/2.backup-restore/4.br-restore-data.md b/docs-2.0/7.data-security/2.backup-restore/4.br-restore-data.md index 41a3d36f9b6..ec9e6d4acf6 100644 --- a/docs-2.0/7.data-security/2.backup-restore/4.br-restore-data.md +++ b/docs-2.0/7.data-security/2.backup-restore/4.br-restore-data.md @@ -122,7 +122,7 @@ To restore data from some backup files: !!! note - After restoration： + After restoration: + If no records are returned for the `USE ` statement, we recommend that you restart the Graph Service. + If the `Storage Error: part: 2, error code: -3.` error occurs when you query the restored data, do a check of the status of the Storage Service. If necessary, restart the Storage Service. diff --git a/docs-2.0/nebula-algorithm.md b/docs-2.0/nebula-algorithm.md index 382e36cd68b..ab9d210e7e7 100644 --- a/docs-2.0/nebula-algorithm.md +++ b/docs-2.0/nebula-algorithm.md @@ -161,16 +161,16 @@ The `lib` repository provides 10 common graph algorithms. # The name of the graph space in Nebula Graph. space:nb # The name of the tag in Nebula Graph. The graph computing result will be written into this tag. The property name of this tag is as follows. - # PageRank：pagerank - # Louvain：louvain - # ConnectedComponent：cc - # StronglyConnectedComponent：scc - # LabelPropagation：lpa - # ShortestPath：shortestpath - # DegreeStatic：degree、inDegree、outDegree - # KCore：kcore - # TriangleCount：tranglecpunt - # BetweennessCentrality：betweennedss + # PageRank: pagerank + # Louvain: louvain + # ConnectedComponent: cc + # StronglyConnectedComponent: scc + # LabelPropagation: lpa + # ShortestPath: shortestpath + # DegreeStatic: degree、inDegree、outDegree + # KCore: kcore + # TriangleCount: tranglecpunt + # BetweennessCentrality: betweennedss tag:pagerank } } diff --git a/docs-2.0/nebula-dashboard/3.connect-dashboard.md b/docs-2.0/nebula-dashboard/3.connect-dashboard.md index db73d41727f..35d08e8fcb5 100644 --- a/docs-2.0/nebula-dashboard/3.connect-dashboard.md +++ b/docs-2.0/nebula-dashboard/3.connect-dashboard.md @@ -18,6 +18,6 @@ After Dashboard is deployed, you can log in and use Dashboard on the browser. - If authentication is not enabled, you can only log in using `root` as the username and random characters as the password. - To enable authentication, see [Authentication](../7.data-security/1.authentication/1.authentication.md)。 + To enable authentication, see [Authentication](../7.data-security/1.authentication/1.authentication.md). ![Login](login.png) diff --git a/docs-2.0/nebula-dashboard/4.use-dashboard.md b/docs-2.0/nebula-dashboard/4.use-dashboard.md index 2a907bcbd4f..aff8bba544f 100644 --- a/docs-2.0/nebula-dashboard/4.use-dashboard.md +++ b/docs-2.0/nebula-dashboard/4.use-dashboard.md @@ -48,7 +48,7 @@ Service consists of the following parts: - By default, you can check the monitoring data up to 14 days before. The alternative can be 1 hour, 6 hours, 12 hours, 1 day, 3 days, 7 days, or 14 days in the past. - - You can choose the machine that you want to check the monitoring data, monitoring metrics, metric methods, and period. For more information, see [monitor parameter](6.monitor-parameter.md)。 + - You can choose the machine that you want to check the monitoring data, monitoring metrics, metric methods, and period. For more information, see [monitor parameter](6.monitor-parameter.md). - You can set a base line as a reference. diff --git a/docs-2.0/nebula-exchange/nebula-exchange.md b/docs-2.0/nebula-exchange/nebula-exchange.md new file mode 100644 index 00000000000..fb3497487ad --- /dev/null +++ b/docs-2.0/nebula-exchange/nebula-exchange.md @@ -0,0 +1,61 @@ +# Nebula Exchange + +[Nebula Exchange](https://github.com/vesoft-inc/nebula-spark-utils/tree/v2.0.0/nebula-exchange) (hereinafter referred to as Exchange) is an Apache Spark™ application for migrating data into Nebula Graph from distributed systems. Exchange supports the migration of migrating batch data and stream data of different formats. + + + +## Use cases + +Exchange applies to transforming the following data into vertices and edges in [Nebula Graph](../1.introduction/1.what-is-nebula-graph.md): + +* Stream data stored in Kafka or Pulsar, including Logs, online shopping records, online game player activities, social network information, financial trading data, and geospatial service data. +* Telemeasuring data recorded by equipment connected to IDCs. +* Batch data stored in relational databases such as MySQL or distributed file systems such as HDFS. + +## Benefits + +* Adaptable. Exchange supports importing data with many different formats and sources into the Nebula Graph for easy data migration. + +* Supports SST import. Exchange can transform data from different sources into SST files for importing. + + !!! note + + SST import is only supported on Linux. + +* Supports breakpoint continuous transmission. To save time and improve efficiency, Exchange can continue the data transmission after the transmission is stopped. + + !!! note + + For now, breakpoint continuous transmission is only supported when importing Neo4j data. + +* Asynchronous operations. Exchange generates a writing statement and then sends it to the Graph Service for data insertion. + +* Flexible. Exchange supports importing data with multiple tags and edge types that originated from different data formats or sources. + +* Supports statistics. Exchange uses Apache Spark™ Accumulators to make statistics for successful and failed insertion operations. + +* Easy to use. Exchange applies the Human-Optimized Config Object Notation (HOCON) format for configuration files. HOCON is object-oriented and easy to understand and use. + +## Data formats and origins + +Exchange 2.0 can migrate data with the following formats or origins. + +* Data stored in HDFS, including: + - Apache Parquet + - Apache ORC + - JSON + - CSV + +* Apache HBase™ + +* Data warehouse: Hive + +* Graph database: Neo4j + +* Relational database: MySQL + +* Event streaming platform: Apache Kafka® + +* Message publishing/subscribing platform: Apache Pulsar 2.4.5 diff --git a/docs-2.0/nebula-studio/deploy-connect/st-ug-deploy.md b/docs-2.0/nebula-studio/deploy-connect/st-ug-deploy.md index d3045210011..82373c28237 100644 --- a/docs-2.0/nebula-studio/deploy-connect/st-ug-deploy.md +++ b/docs-2.0/nebula-studio/deploy-connect/st-ug-deploy.md @@ -92,7 +92,7 @@ Before you deploy Docker-based Studio , you must do a check of these: !!! note `node` and `npm` should be installed in `/usr/bin/` directory. Avoid the situation that the node command cannot be found during RPM installation. - For example, the default directory of nodejs12 is in `/opt/rh/rh-nodejs12`，you can use following commands to build soft link: + For example, the default directory of nodejs12 is in `/opt/rh/rh-nodejs12`, you can use following commands to build soft link: ```bash $ sudo ln -s /opt/rh/rh-nodejs12/root/usr/bin/node /usr/bin/node @@ -199,7 +199,7 @@ Before you deploy Docker-based Studio , you must do a check of these: !!! note `node` and `npm` should be installed in `/usr/bin/` directory. Avoid the situation that the node command cannot be found during RPM installation. - For example, the default directory of nodejs12 is in `/opt/rh/rh-nodejs12`，you can use following commands to build soft link: + For example, the default directory of nodejs12 is in `/opt/rh/rh-nodejs12`, you can use following commands to build soft link: ```bash $ sudo ln -s /opt/rh/rh-nodejs12/root/usr/bin/node /usr/bin/node diff --git a/docs-2.0/nebula-studio/use-console/st-ug-console.md b/docs-2.0/nebula-studio/use-console/st-ug-console.md index a535b7dd1c6..f1655ecda47 100644 --- a/docs-2.0/nebula-studio/use-console/st-ug-console.md +++ b/docs-2.0/nebula-studio/use-console/st-ug-console.md @@ -9,7 +9,7 @@ The following table lists various functions on the console interface. | number | function | descriptions | | :----- | :-------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | toolbar | Click the **Console** tab to enter the console page. | -| 2 | select a space | Select a space in the Current Graph Space list.
**descriptions**：Studio does not support running the `USE ` statements directly in the input box. | +| 2 | select a space | Select a space in the Current Graph Space list.
**descriptions**: Studio does not support running the `USE ` statements directly in the input box. | | 3 | input box | After inputting the nGQL statements, click the ![run](../figs/st-ug-008.png) button to run the statement. You can input multiple statements and run them at the same time, separated by `;`. | | 4 | clean input box | Click ![clean](../figs/st-ug-056.png) button to clear the content entered in the input box. | | 5 | history list | Click ![history](../figs/st-ug-057.png) button representing the statement record. In the statement running record list, click one of the statements, and the statement will be automatically entered in the input box. The list provides the record of the last 15 statements. | diff --git a/docs-2.0/reuse/source_install-nebula-graph-by-rpm-or-deb.md b/docs-2.0/reuse/source_install-nebula-graph-by-rpm-or-deb.md index 81f9b57a12e..9d5808a62cd 100644 --- a/docs-2.0/reuse/source_install-nebula-graph-by-rpm-or-deb.md +++ b/docs-2.0/reuse/source_install-nebula-graph-by-rpm-or-deb.md @@ -12,7 +12,7 @@ Prepare the right [resources](../1.resource-preparations.md). * Download the released version. - URL： + URL: ```bash //Centos 6 @@ -34,14 +34,14 @@ Prepare the right [resources](../1.resource-preparations.md). https://oss-cdn.nebula-graph.io/package//nebula-graph-.ubuntu2004.amd64.deb ``` - For example, download release package `2.0.0` for `Centos 7.5`： + For example, download release package `2.0.0` for `Centos 7.5`: ```bash wget https://oss-cdn.nebula-graph.io/package/2.0.0/nebula-graph-2.0.0.el7.x86_64.rpm wget https://oss-cdn.nebula-graph.io/package/2.0.0/nebula-graph-2.0.0.el7.x86_64.rpm.sha256sum.txt ``` - download release package `2.0.0` for `Ubuntu 1804`： + download release package `2.0.0` for `Ubuntu 1804`: ```bash wget https://oss-cdn.nebula-graph.io/package/2.0.0/nebula-graph-2.0.0.ubuntu1804.amd64.deb @@ -54,7 +54,7 @@ Prepare the right [resources](../1.resource-preparations.md). Nightly versions are usually used to test new features. Don't use it for production. - URL： + URL: ```bash //Centos 6 @@ -76,14 +76,14 @@ Prepare the right [resources](../1.resource-preparations.md). https://oss-cdn.nebula-graph.io/package/v2-nightly//nebula-graph--nightly.ubuntu2004.amd64.deb ``` - For example, download the `Centos 7.5` package developed and built in `2021.03.28`： + For example, download the `Centos 7.5` package developed and built in `2021.03.28`: ```bash wget https://oss-cdn.nebula-graph.io/package/v2-nightly/2021.03.28/nebula-graph-2021.03.28-nightly.el7.x86_64.rpm wget https://oss-cdn.nebula-graph.io/package/v2-nightly/2021.03.28/nebula-graph-2021.03.28-nightly.el7.x86_64.rpm.sha256sum.txt ``` - For example, download the `Ubuntu 1804` package developed and built in `2021.03.28`： + For example, download the `Ubuntu 1804` package developed and built in `2021.03.28`: ```bash wget https://oss-cdn.nebula-graph.io/package/v2-nightly/2021.03.28/nebula-graph-2021.03.28-nightly.ubuntu1804.amd64.deb diff --git a/mkdocs.yml b/mkdocs.yml index 34fadfb6986..17abe0f738c 100755 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -42,7 +42,7 @@ extra: method: mike social: - icon: 'fontawesome/brands/github' - link: 'https://github.com/vesoft-inc/nebula-docs-cn' + link: 'https://github.com/vesoft-inc/nebula-docs' studio: base111b: 1.1.1-beta base220: 2.2.1 @@ -96,6 +96,7 @@ extra: branch: master nav: + - PDF: ./pdf/NebulaGraph-EN.pdf - About: README.md - Introduction: - What is Nebula Graph: 1.introduction/1.what-is-nebula-graph.md @@ -110,10 +111,10 @@ nav: - Quick start: - Quick start workflow: 2.quick-start/1.quick-start-workflow.md - - Step 1：Install Nebula Graph: 2.quick-start/2.install-nebula-graph.md - - Step 2：Manage Nebula Graph Service: 2.quick-start/5.start-stop-service.md - - Step 3：Connect to Nebula Graph: 2.quick-start/3.connect-to-nebula-graph.md - - Step 4：Use nGQL（CRUD）: 2.quick-start/4.nebula-graph-crud.md + - Step 1: Install Nebula Graph: 2.quick-start/2.install-nebula-graph.md + - Step 2: Manage Nebula Graph Service: 2.quick-start/5.start-stop-service.md + - Step 3: Connect to Nebula Graph: 2.quick-start/3.connect-to-nebula-graph.md + - Step 4: Use nGQL（CRUD）: 2.quick-start/4.nebula-graph-crud.md - nGQL guide: - nGQL overview: @@ -411,7 +412,6 @@ nav: - 中文手册: https://docs.nebula-graph.com.cn/ - - PDF: ./pdf/NebulaGraph-EN.pdf # Extensions markdown_extensions: @@ -438,7 +438,7 @@ plugins: - with-pdf: copyright: 2021 Vesoft Inc. cover_subtitle: master - author: Min Wu, Yao Zhou, Cooper Liang + author: Min Wu, Yao Zhou, Cooper Liang, foesa Yang, Max Zhu cover: true back_cover: true cover_logo: 'https://cloud-cdn.nebula-graph.com.cn/nebula-for-pdf.png'