From 6c93dd124a41708ef1ab6085c9ed7319c80cb1f9 Mon Sep 17 00:00:00 2001 From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com> Date: Tue, 18 Jan 2022 09:29:59 +0800 Subject: [PATCH] fix links (#1044) --- docs-2.0/20.appendix/0.FAQ.md | 4 +- docs-2.0/20.appendix/0.vid.md | 20 -- docs-2.0/20.appendix/3.system-design.md | 1 - docs-2.0/20.appendix/4.raft.md | 1 - docs-2.0/20.appendix/5.partition.md | 32 --- docs-2.0/20.appendix/comments.md | 42 ---- .../identifier-case-sensitivity.md | 23 -- .../keywords-and-reserved-words.md | 228 ------------------ .../4.rebuild-native-index.md | 2 +- .../{7.unwind.md => unwind.md} | 0 ...bula-graph-by-compiling-the-source-code.md | 2 +- .../deploy-nebula-graph-cluster.md | 2 +- .../upgrade-nebula-from-200-to-latest.md | 2 +- .../upgrade-nebula-graph-to-latest.md | 2 +- .../4.uninstall-nebula-graph.md | 2 +- .../3.deploy-listener.md | 2 +- .../1.configurations/1.configurations.md | 2 +- .../2.log-management/logs.md | 4 +- docs-2.0/7.data-security/3.manage-snapshot.md | 2 +- .../2.how-to-create-subsciption.md | 4 + .../3.cluster-information.md | 2 +- .../4.cluster-operator/4.manage.md | 2 +- .../1.introduction-to-nebula-operator.md | 2 +- 23 files changed, 20 insertions(+), 363 deletions(-) delete mode 100644 docs-2.0/20.appendix/0.vid.md delete mode 100644 docs-2.0/20.appendix/3.system-design.md delete mode 100644 docs-2.0/20.appendix/4.raft.md delete mode 100644 docs-2.0/20.appendix/5.partition.md delete mode 100644 docs-2.0/20.appendix/comments.md delete mode 100644 docs-2.0/20.appendix/identifier-case-sensitivity.md delete mode 100644 docs-2.0/20.appendix/keywords-and-reserved-words.md rename docs-2.0/3.ngql-guide/8.clauses-and-options/{7.unwind.md => unwind.md} (100%) diff --git a/docs-2.0/20.appendix/0.FAQ.md b/docs-2.0/20.appendix/0.FAQ.md index d21a0a0c807..2626dd52b5f 100644 --- a/docs-2.0/20.appendix/0.FAQ.md +++ b/docs-2.0/20.appendix/0.FAQ.md @@ -341,11 +341,11 @@ Nebula Graph {{ nebula.release }} does not provide any commands or tools to supp 3. Scale out graphd: Prepare the binary and config files of the graphd process in the new host. Modify the config files and add all existing addresses of the metad processes. Then start the new graphd process. -4. Scale in storaged: (The number of replicas must be greater than 1) See [Balance remove command](../8.service-tuning/load-balance.md#storage_1). After the command is finished, stop this storaged process. +4. Scale in storaged: (The number of replicas must be greater than 1) See [Balance remove command](../8.service-tuning/load-balance.md). After the command is finished, stop this storaged process. 5. Scale out storaged: (The number of replicas must be greater than 1) Prepare the binary and config files of the storaged process in the new host, Modify the config files and add all existing addresses of the metad processes. Then start the new storaged process. -You also need to run [Balance Data and Balance leader](../8.service-tuning/load-balance) after scaling in/out storaged. +You also need to run [Balance Data and Balance leader](../8.service-tuning/load-balance.md) after scaling in/out storaged. ### "After changing the name of the host, the old one keeps displaying `OFFLINE`. What should I do?" diff --git a/docs-2.0/20.appendix/0.vid.md b/docs-2.0/20.appendix/0.vid.md deleted file mode 100644 index 9e02164181b..00000000000 --- a/docs-2.0/20.appendix/0.vid.md +++ /dev/null @@ -1,20 +0,0 @@ -TODO(doc) - - -## VID - -`VID` is short for vertex identifier. - -In Nebula Graph, vertices are identified with vertex identifiers (i.e. `VID`s). -The VID can be an int64 or a fixed length string. -When inserting a vertex, you must specify a `VID` for it. - -You can also call `hash()` to generate an int64 VID if the graph has less than one billion vertices. - -> `VID` must be unique in a graph space. - -That is, in the same graph space, two vertices that have the same `VID` are considered as the same vertex. - -In addition, one `VID` can have multiple `TAG`s. E.g., One person (`VID`) can have two roles (`tags`). - -Two `VID`s in two different graph spaces are totally independent of each other. \ No newline at end of file diff --git a/docs-2.0/20.appendix/3.system-design.md b/docs-2.0/20.appendix/3.system-design.md deleted file mode 100644 index 56cb9dd06fb..00000000000 --- a/docs-2.0/20.appendix/3.system-design.md +++ /dev/null @@ -1 +0,0 @@ -TODO(doc) \ No newline at end of file diff --git a/docs-2.0/20.appendix/4.raft.md b/docs-2.0/20.appendix/4.raft.md deleted file mode 100644 index 56cb9dd06fb..00000000000 --- a/docs-2.0/20.appendix/4.raft.md +++ /dev/null @@ -1 +0,0 @@ -TODO(doc) \ No newline at end of file diff --git a/docs-2.0/20.appendix/5.partition.md b/docs-2.0/20.appendix/5.partition.md deleted file mode 100644 index 59db3c0fb9f..00000000000 --- a/docs-2.0/20.appendix/5.partition.md +++ /dev/null @@ -1,32 +0,0 @@ -# Partition ID - -When inserting into Nebula Graph, vertices and edges are distributed across different partitions. And the partitions are located on different machines. If you want certain vertices to locate on the same partition (i.e., on the same machine), you can control the generation of the `VID`s by using the following [formula / code](https://github.com/vesoft-inc/nebula-common/blob/master/src/common/clients/meta/MetaClient.cpp). - -```C++ - // If the length of the id is 8, we will treat it as int64_t to be compatible - // with the version 1.0 - uint64_t vid = 0; - if (id.size() == 8) { - memcpy(static_cast(&vid), id.data(), 8); - } else { - MurmurHash2 hash; - vid = hash(id.data()); - } - PartitionID pId = vid % numParts + 1; -``` - -Roughly say, after hashing a fixed string to int64, (the hashing of int64 is the number itself), do modulo and then plus one. - -```C++ -pId = vid % numParts + 1; -``` - -In the preceding formula, - -- `%` is the modulo operation. -- `numParts` is the number of partition for the graph space where the `VID` is located, namely the value of `partition_num` in the [CREATE SPACE](../3.ngql-guide/9.space-statements/1.create-space.md) statement. -- `pId` is the ID for the partition where the `VID` is located. - -For example, if there are 100 partitions, the vertices with `VID` 1, 101, 1001 will be stored on the same partition. - -But, the mapping between the `partition ID` and the machine address is random. Therefore, you can't assume that any two partitions are located on the same machine. diff --git a/docs-2.0/20.appendix/comments.md b/docs-2.0/20.appendix/comments.md deleted file mode 100644 index 9828f717a3a..00000000000 --- a/docs-2.0/20.appendix/comments.md +++ /dev/null @@ -1,42 +0,0 @@ -# Comments - -## Legacy version compatibility - -* In Nebula Graph 1.0, four comment styles: `#`, `--`, `//`, `/* */`. -* In Nebula Graph 2.0, `--` represents an edge, and can not be used as comments. - -## Examples -```ngql -nebula> # Do nothing this line -nebula> RETURN 1+1; # This comment continues to the end of line -nebula> RETURN 1+1; // This comment continues to the end of line -nebula> RETURN 1 /* This is an in-line comment */ + 1 == 2; -nebula> RETURN 11 + \ -/* Multiple-line comment \ -Use backslash as line break. \ -*/ 12; -``` - -The backslash `\` in a line indicates a line break. - -## OpenCypher Compatibility - -You must add a `\` at the end of every line, even in multi-line comments `\* *\`. - -```openCypher -/* The openCypher style: -The following comment -spans more than -one line */ -MATCH (n:label) -RETURN n -``` - -```ngql -/* The native nGQL style: \ -The following comment \ -spans more than \ -one line */ \ -MATCH (n:tag) \ -RETURN n -``` diff --git a/docs-2.0/20.appendix/identifier-case-sensitivity.md b/docs-2.0/20.appendix/identifier-case-sensitivity.md deleted file mode 100644 index 01b41fd17f9..00000000000 --- a/docs-2.0/20.appendix/identifier-case-sensitivity.md +++ /dev/null @@ -1,23 +0,0 @@ -# Identifer Case Sensitivity - -## Identifiers are Case-Sensitive - -The following statements would not work because they refer to two different spaces, i.e. `my_space` and `MY_SPACE`: - -```ngql -nebula> CREATE SPACE IF NOT EXISTS my_space; -nebula> use MY_SPACE; -[ERROR (-8)]: SpaceNotFound: -# my_space and MY_SPACE are two different spaces -``` - -## Keywords and Reserved Words are Case-Insensitive - -The following statements are equivalent: - -```ngql -nebula> show spaces; # show and spaces are keywords. -nebula> SHOW SPACES; -nebula> SHOW spaces; -nebula> show SPACES; -``` diff --git a/docs-2.0/20.appendix/keywords-and-reserved-words.md b/docs-2.0/20.appendix/keywords-and-reserved-words.md deleted file mode 100644 index a7456617940..00000000000 --- a/docs-2.0/20.appendix/keywords-and-reserved-words.md +++ /dev/null @@ -1,228 +0,0 @@ -# Keywords and Reserved Words - -Keywords have significance in nGQL. Certain keywords are reserved and require special treatment for use as identifiers. - -Non-reserved keywords are permitted as identifiers without quoting. Non-reserved keywords are case-insensitive. To use reserved keywords as identifiers, quote them with back quotes such as \`AND\`. - -```ngql -nebula> CREATE TAG TAG(name string); -[ERROR (-7)]: SyntaxError: syntax error near `TAG' - -// SPACE is an unreserved keyword. -nebula> CREATE TAG SPACE(name string); -Execution succeeded -``` - -`TAG` is a reserved keyword. To use `TAG` as an identifier, you must quote it with a backtick. `SPACE` is a non-reserved keyword. You can use `SPACE` as an identifier without quoting it. - -!!! note - - There is a small pitfall when you use the non-reserved keyword. Unquoted non-reserved keyword will be converted to **lower-case** words. For example, `SPACE` or `Space` will become `space`. - -```ngql -// TAG is a reserved keyword here. -nebula> CREATE TAG `TAG` (name string); -Execution succeeded -``` - -## Reserved Words - -The following list shows reserved words in nGQL. - -```ngql -ADD -ALTER -AND -AS -ASC -BALANCE -BOOL -BY -CASE -CHANGE -COMPACT -CREATE -DATE -DATETIME -DELETE -DESC -DESCRIBE -DISTINCT -DOUBLE -DOWNLOAD -DROP -EDGE -EDGES -EXISTS -EXPLAIN -FETCH -FIND -FIXED_STRING -FLOAT -FLUSH -FORMAT -FROM -GET -GO -GRANT -IF -IN -INDEX -INDEXES -INGEST -INSERT -INT -INT16 -INT32 -INT64 -INT8 -INTERSECT -IS -LIMIT -LOOKUP -MATCH -MINUS -NO -NOT -NULL -OF -OFFSET -ON -OR -ORDER -OVER -OVERWRITE -PROFILE -PROP -REBUILD -RECOVER -REMOVE -RETURN -REVERSELY -REVOKE -SET -SHOW -STEP -STEPS -STOP -STRING -SUBMIT -TAG -TAGS -TIME -TIMESTAMP -TO -UNION -UPDATE -UPSERT -UPTO -USE -VERTEX -WHEN -WHERE -WITH -XOR -YIELD -``` - -## Non-Reserved Keywords - -```ngql -ACCOUNT -ADMIN -ALL -ANY -ATOMIC_EDGE -AUTO -AVG -BIDIRECT -BIT_AND -BIT_OR -BIT_XOR -BOTH -CHARSET -CLIENTS -COLLATE -COLLATION -COLLECT -COLLECT_SET -CONFIGS -CONTAINS -COUNT -COUNT_DISTINCT -DATA -DBA -DEFAULT -ELASTICSEARCH -ELSE -END -ENDS -FALSE -FORCE -FUZZY -GOD -GRAPH -GROUP -GROUPS -GUEST -HDFS -HOST -HOSTS -INTO -JOB -JOBS -LEADER -LISTENER -MAX -META -MIN -NOLOOP -NONE -OPTIONAL -OUT -PART -PARTITION_NUM -PARTS -PASSWORD -PATH -PLAN -PREFIX -REGEXP -REPLICA_FACTOR -RESET -ROLE -ROLES -SEARCH -SERVICE -SHORTEST -SIGN -SINGLE -SKIP -SNAPSHOT -SNAPSHOTS -SPACE -SPACES -STARTS -STATS -STATUS -STD -STORAGE -SUBGRAPH -SUM -TEXT -TEXT_SEARCH -THEN -TRUE -TTL_COL -TTL_DURATION -UNWIND -USER -USERS -UUID -VALUE -VALUES -VID_TYPE -WILDCARD -ZONE -ZONES -``` diff --git a/docs-2.0/3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md b/docs-2.0/3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md index 5b143208bfa..0d1f3e4860a 100644 --- a/docs-2.0/3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md +++ b/docs-2.0/3.ngql-guide/14.native-index-statements/4.rebuild-native-index.md @@ -55,7 +55,7 @@ nebula> SHOW JOB 31; +----------------+---------------------+------------+-------------------------+-------------------------+ ``` -Nebula Graph creates a job to rebuild the index. The job ID is displayed in the preceding return message. To check if the rebuilding process is complete, use the `SHOW JOB ` statement. For more information, see [SHOW JOB](../18.operation-and-maintenance-statements/4.job-statements.md/#show-job-job_id). +Nebula Graph creates a job to rebuild the index. The job ID is displayed in the preceding return message. To check if the rebuilding process is complete, use the `SHOW JOB ` statement. For more information, see [SHOW JOB](../18.operation-and-maintenance-statements/4.job-statements.md#show_job). ## Legacy version compatibility diff --git a/docs-2.0/3.ngql-guide/8.clauses-and-options/7.unwind.md b/docs-2.0/3.ngql-guide/8.clauses-and-options/unwind.md similarity index 100% rename from docs-2.0/3.ngql-guide/8.clauses-and-options/7.unwind.md rename to docs-2.0/3.ngql-guide/8.clauses-and-options/unwind.md diff --git a/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md b/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md index 63888f9d3f5..74418cfa492 100644 --- a/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md +++ b/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/1.install-nebula-graph-by-compiling-the-source-code.md @@ -169,6 +169,6 @@ If the compiling fails, we suggest you: 1. Check whether the operating system release meets the requirements and whether the memory and hard disk space are sufficient. -2. Check whether the [third-party](../1.resource-preparations/#_5) is installed correctly. +2. Check whether the [third-party](../1.resource-preparations.md) is installed correctly. 3. Use `make -j1` to reduce the compiling concurrency. diff --git a/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/deploy-nebula-graph-cluster.md b/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/deploy-nebula-graph-cluster.md index be482be807b..b038c2d2dc9 100644 --- a/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/deploy-nebula-graph-cluster.md +++ b/docs-2.0/4.deployment-and-installation/2.compile-and-install-nebula-graph/deploy-nebula-graph-cluster.md @@ -282,7 +282,7 @@ sudo /usr/local/nebula/scripts/nebula.service start ### Step 4: Check the cluster status -Install the native CLI client [Nebula Console](../../2.quick-start/3.connect-to-nebula-graph.md#_1), then connect to any machine that has started the graphd process, and run `SHOW HOSTS` to check the cluster status. For example: +Install the native CLI client [Nebula Console](../../2.quick-start/3.connect-to-nebula-graph.md), then connect to any machine that has started the graphd process, and run `SHOW HOSTS` to check the cluster status. For example: ```bash $ ./nebula-console --addr 192.168.10.111 --port 9669 -u root -p nebula diff --git a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md index 21222ae4222..da8b66fca9f 100644 --- a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md +++ b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-from-200-to-latest.md @@ -32,7 +32,7 @@ To upgrade Nebula Graph v2.0.x to v{{nebula.release}}, you only need to use the $ sudo dpkg -i ``` -4. Start the required services on each server. For details, see [Manage Nebula Graph Service](../../2.quick-start/5.start-stop-service.md#_1). +4. Start the required services on each server. For details, see [Manage Nebula Graph Service](../../2.quick-start/5.start-stop-service.md). ## Upgrade steps by compiling the new source code diff --git a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md index d1434f01a17..314665e4251 100644 --- a/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md +++ b/docs-2.0/4.deployment-and-installation/3.upgrade-nebula-graph/upgrade-nebula-graph-to-latest.md @@ -113,7 +113,7 @@ By default, old versions of Nebula Graph are installed in `/usr/local/nebula/`, 4. Follow the substeps to prepare the Meta servers (usually 3 of them in a cluster). - - Locate the old Meta [data path](#old-installation-path) and copy the data files to the new path. + - Locate the old Meta data path and copy the data files to the new path. Find the `--data_path` option in `${nebula-old}/etc/nebula-metad.conf`. The default value is `data/meta`. diff --git a/docs-2.0/4.deployment-and-installation/4.uninstall-nebula-graph.md b/docs-2.0/4.deployment-and-installation/4.uninstall-nebula-graph.md index 7c9556622bc..a3c03bd6df6 100644 --- a/docs-2.0/4.deployment-and-installation/4.uninstall-nebula-graph.md +++ b/docs-2.0/4.deployment-and-installation/4.uninstall-nebula-graph.md @@ -18,7 +18,7 @@ If you have modified the `data_path` in the configuration files for the Meta Ser For a Nebula Graph cluster, delete the data files of all Storage and Meta servers. -1. Check the [Storage Service disk settings](../5.configurations-and-logs/1.configurations/4.storage-config.md#disk). For example: +1. Check the [Storage Service disk settings](../5.configurations-and-logs/1.configurations/4.storage-config.md#disk_configurations). For example: ```bash ########## Disk ########## diff --git a/docs-2.0/4.deployment-and-installation/6.deploy-text-based-index/3.deploy-listener.md b/docs-2.0/4.deployment-and-installation/6.deploy-text-based-index/3.deploy-listener.md index 4be1be9d7e1..0784846e6ae 100644 --- a/docs-2.0/4.deployment-and-installation/6.deploy-text-based-index/3.deploy-listener.md +++ b/docs-2.0/4.deployment-and-installation/6.deploy-text-based-index/3.deploy-listener.md @@ -16,7 +16,7 @@ Full-text index data is written to the Elasticsearch cluster asynchronously. The * The Storage Service that you want to run as the Listener must have the same or later release with all the other Nebula Graph services in the cluster. -* For now, you can only add all Listeners to a graph space once and for all. Trying to add a new Listener to a graph space that already has a Listener will fail. To add all Listeners, set them [in one statement](#step_3_add_listeners_to_nebula_graph). +* For now, you can only add all Listeners to a graph space once and for all. Trying to add a new Listener to a graph space that already has a Listener will fail. To add all Listeners, set them [in one statement](#step_4_add_listeners_to_nebula_graph). ## Deployment process diff --git a/docs-2.0/5.configurations-and-logs/1.configurations/1.configurations.md b/docs-2.0/5.configurations-and-logs/1.configurations/1.configurations.md index 9f12966e39a..bd1c1cf6be5 100644 --- a/docs-2.0/5.configurations-and-logs/1.configurations/1.configurations.md +++ b/docs-2.0/5.configurations-and-logs/1.configurations/1.configurations.md @@ -1,6 +1,6 @@ # Configurations -Nebula Graph builds the configurations based on the [gflags](https://gflags.github.io/gflags/) repository. Most configurations are flags. When the Nebula Graph service starts, it will get the configuration information from [Configuration files](#_4) by default. Configurations that are not in the file apply the default values. +Nebula Graph builds the configurations based on the [gflags](https://gflags.github.io/gflags/) repository. Most configurations are flags. When the Nebula Graph service starts, it will get the configuration information from [Configuration files](#configuration_files) by default. Configurations that are not in the file apply the default values. !!! note diff --git a/docs-2.0/5.configurations-and-logs/2.log-management/logs.md b/docs-2.0/5.configurations-and-logs/2.log-management/logs.md index 8364a54fe3c..6f4af891549 100644 --- a/docs-2.0/5.configurations-and-logs/2.log-management/logs.md +++ b/docs-2.0/5.configurations-and-logs/2.log-management/logs.md @@ -53,8 +53,8 @@ $ curl -X PUT -H "Content-Type: application/json" -d '{"":[,"": |Parameter|Description| |:---|:---| -|`key`|The type of the log to be changed. For optional values, see [Parameter descriptions](#_3).| -|`value`|The level of the log. For optional values, see [Parameter descriptions](#_3).| +|`key`|The type of the log to be changed. For optional values, see [Parameter descriptions](#parameter_descriptions).| +|`value`|The level of the log. For optional values, see [Parameter descriptions](#parameter_descriptions).| |`ws_ip`|The IP address for the HTTP service, which can be found in the configuration files above. The default value is `127.0.0.1`.| |`ws_port`|The port for the HTTP service, which can be found in the configuration files above. The default values are `19559`(Meta), `19669`(Graph), and `19779`(Storage) respectively.| diff --git a/docs-2.0/7.data-security/3.manage-snapshot.md b/docs-2.0/7.data-security/3.manage-snapshot.md index dfa40ffd593..32ee19fe5b8 100644 --- a/docs-2.0/7.data-security/3.manage-snapshot.md +++ b/docs-2.0/7.data-security/3.manage-snapshot.md @@ -12,7 +12,7 @@ If authentication is enabled, only the GOD role user can use the snapshot featur * To prevent data loss, create a snapshot as soon as the system structure changes, for example, after operations such as `ADD HOST`, `DROP HOST`, `CREATE SPACE`, `DROP SPACE`, and `BALANCE` are performed. -* Nebula Graph cannot automatically delete the invalid files created by a failed snapshot task. You have to manually delete them by using [`DROP SNAPSHOT`](#delete_a_snapshot). +* Nebula Graph cannot automatically delete the invalid files created by a failed snapshot task. You have to manually delete them by using [`DROP SNAPSHOT`](#delete_snapshots). * Customizing the storage path for snapshots is not supported for now. The default path is `/usr/local/nebula/data`. diff --git a/docs-2.0/nebula-cloud/2.how-to-create-subsciption.md b/docs-2.0/nebula-cloud/2.how-to-create-subsciption.md index 3297ac0bae8..311adb5a14c 100644 --- a/docs-2.0/nebula-cloud/2.how-to-create-subsciption.md +++ b/docs-2.0/nebula-cloud/2.how-to-create-subsciption.md @@ -28,4 +28,8 @@ Before using Nebula Graph Cloud, you need to create a subscription on Azure. Thi 3. (Optional) On the **Tags** page, enter **Name: Value**. 4. At the bottom of **Review + subscribe** page, click **Subscribe** and wait for about 2 minutes. +<<<<<<< Updated upstream 3. After the subscription is completed, you need to click **Open the SaaS account on the publisher's website** to create and configure your Solution. For details, see [How to configure a Solution](../nebula-nebula-cloud/3.how-to-set-solution.md). +======= +3. After the subscription is completed, you need to click `Open the SaaS account on the publisher's website` to create and configure your Solution. For details, see [How to configure a Solution](3.how-to-set-solution.md). +>>>>>>> Stashed changes diff --git a/docs-2.0/nebula-dashboard-ent/4.cluster-operator/3.cluster-information.md b/docs-2.0/nebula-dashboard-ent/4.cluster-operator/3.cluster-information.md index a4424026f54..6851533c0ba 100644 --- a/docs-2.0/nebula-dashboard-ent/4.cluster-operator/3.cluster-information.md +++ b/docs-2.0/nebula-dashboard-ent/4.cluster-operator/3.cluster-information.md @@ -69,6 +69,6 @@ On this page, the information of all jobs will be shown. Before viewing the job | :--- | :--- | | `Job ID` | Shows the Job ID. | | `Command` | Shows the command type. | -| `Status` | Shows the status of the job or task. For more information, see [Job statements](../../3.ngql-guide/18.operation-and-maintenance-statements/4.job-statements.md#_6). | +| `Status` | Shows the status of the job or task. For more information, see [Job statements](../../3.ngql-guide/18.operation-and-maintenance-statements/4.job-statements.md). | |`Start Time`| Shows a timestamp indicating the time when the job or task starts RUNNING.| | `Stop Time` | Shows a timestamp indicating the time when the job or task gets `FINISHED`, `FAILED`, or`STOPPED`. | diff --git a/docs-2.0/nebula-dashboard-ent/4.cluster-operator/4.manage.md b/docs-2.0/nebula-dashboard-ent/4.cluster-operator/4.manage.md index 9ecfd50c051..009d693643c 100644 --- a/docs-2.0/nebula-dashboard-ent/4.cluster-operator/4.manage.md +++ b/docs-2.0/nebula-dashboard-ent/4.cluster-operator/4.manage.md @@ -36,7 +36,7 @@ On this page, the information of all nodes will be shown, including the cluster !!! caution - Currently, you can dynamically scale Storaged and Graphd services through Dashboard. The Metad service cannot be scaled. When scaling a cluster, it is recommended to back up data in advance so that data can be rolled back when scaling fails. For more information, see [FAQ](../../20.appendix/0.FAQ.md#_11). + Currently, you can dynamically scale Storaged and Graphd services through Dashboard. The Metad service cannot be scaled. When scaling a cluster, it is recommended to back up data in advance so that data can be rolled back when scaling fails. For more information, see [FAQ](../../20.appendix/0.FAQ.md). In this example, storage services with nodes `192.168.8.143` and `192.168.8.167` are added, and Graph services with node `192.168.8.169` are deleted. If the box is dotted and the service name is greyed, it means the service is removed. If the box is solid, it means the service is newly added. diff --git a/docs-2.0/nebula-operator/1.introduction-to-nebula-operator.md b/docs-2.0/nebula-operator/1.introduction-to-nebula-operator.md index 02cf30f935c..4e6702a1aa6 100644 --- a/docs-2.0/nebula-operator/1.introduction-to-nebula-operator.md +++ b/docs-2.0/nebula-operator/1.introduction-to-nebula-operator.md @@ -16,7 +16,7 @@ The following features are already available in Nebula Operator: - **Deploy and uninstall clusters**: Nebula Operator simplifies the process of deploying and uninstalling clusters for users. Nebula Operator allows you to quickly create, update, or delete a Nebula Graph cluster by simply providing the corresponding CR file. For more information, see [Deploy Nebula Graph Clusters with Kubectl](3.deploy-nebula-graph-cluster/3.1create-cluster-with-kubectl.md) or [Deploy Nebula Graph Clusters with Helm](3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm.md). -- **Scale clusters**: Nebula Operator calls Nebula Graph's native scaling interfaces in a control loop to implement the scaling logic. You can simply perform scaling operations with YAML configurations and ensure the stability of data. For more information, see [Scale clusters with Kubectl](3.deploy-nebula-graph-cluster/3.1create-cluster-with-kubectl.md#_3) or [Scale clusters with Helm](3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm.md#_2). +- **Scale clusters**: Nebula Operator calls Nebula Graph's native scaling interfaces in a control loop to implement the scaling logic. You can simply perform scaling operations with YAML configurations and ensure the stability of data. For more information, see [Scale clusters with Kubectl](3.deploy-nebula-graph-cluster/3.1create-cluster-with-kubectl.md) or [Scale clusters with Helm](3.deploy-nebula-graph-cluster/3.2create-cluster-with-helm.md). - **Cluster Upgrade**: Nebula Operator supports cluster upgrading from version 2.5.x to version 2.6.x.