From f82a9d37909d3e3286b6991df55f93da670e793a Mon Sep 17 00:00:00 2001 From: cooper-lzy <78672629+cooper-lzy@users.noreply.github.com> Date: Mon, 11 Oct 2021 13:32:43 +0800 Subject: [PATCH 1/4] add toss --- .../4.storage-service.md | 4 ++++ .../1.configurations/3.graph-config.md | 14 ++++++++++++++ 2 files changed, 18 insertions(+) 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 0bff7d5769a..01baefa737f 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 @@ -142,6 +142,10 @@ EdgeA_Out and EdgeA_In are stored in storage layer with opposite directions, con Like EdgeA_Out and EdgeA_In, Nebula Graph redundantly stores the information of each edge, which doubles the actual capacities needed for edge storage. The key corresponding to the edge occupies a small hard disk space, but the space occupied by Value is proportional to the length and amount of the property value. Therefore, it will occupy a relatively large hard disk space if the property value of the edge is large or there are many edge property values. + + ### Partition algorithm Nebula Graph uses a **static Hash** strategy to shard data through a modulo operation on vertex ID. All the out-keys, in-keys, and tag data will be placed in the same partition. In this way, query efficiency is increased dramatically. diff --git a/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md b/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md index 7f56fa5cec1..7f8ccb920d4 100644 --- a/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md +++ b/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md @@ -92,3 +92,17 @@ For all parameters and their current values, see [Configurations](1.configuratio | ------------------- | ---------------- | ------------------------------------------ | |`enable_authorize` |`false` |When set to `false`, the system authentication is not enabled. For more information, see [Authentication](../../7.data-security/1.authentication/1.authentication.md).| |`auth_type` |`password` |Specifies the login method. Available values are `password`, `ldap`, and `cloud`.| + + \ No newline at end of file From e6050d25cf941d2c1b240e15b0d488d72e81cbdd Mon Sep 17 00:00:00 2001 From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com> Date: Mon, 11 Oct 2021 14:23:01 +0800 Subject: [PATCH 2/4] Update 4.storage-service.md --- .../3.nebula-graph-architecture/4.storage-service.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) 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 01baefa737f..89cea25c141 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 @@ -142,9 +142,7 @@ EdgeA_Out and EdgeA_In are stored in storage layer with opposite directions, con Like EdgeA_Out and EdgeA_In, Nebula Graph redundantly stores the information of each edge, which doubles the actual capacities needed for edge storage. The key corresponding to the edge occupies a small hard disk space, but the space occupied by Value is proportional to the length and amount of the property value. Therefore, it will occupy a relatively large hard disk space if the property value of the edge is large or there are many edge property values. - +To ensure the final consistency of the two key-value pairs when operating on edges, enable the [TOSS function](../../5.configurations-and-logs/1.configurations/3.graph-config.md ). After that, the operation will be performed in Partition x first where the out-edge is located, and then in Partition y where the in-edge is located. Finally, the result is returned. ### Partition algorithm From 8236d711c5ed5c5faa4527b15cc6d30269483bf2 Mon Sep 17 00:00:00 2001 From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com> Date: Mon, 11 Oct 2021 14:35:11 +0800 Subject: [PATCH 3/4] Update 3.graph-config.md --- .../1.configurations/3.graph-config.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md b/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md index 7f8ccb920d4..9c1a82402a2 100644 --- a/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md +++ b/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md @@ -93,16 +93,14 @@ For all parameters and their current values, see [Configurations](1.configuratio |`enable_authorize` |`false` |When set to `false`, the system authentication is not enabled. For more information, see [Authentication](../../7.data-security/1.authentication/1.authentication.md).| |`auth_type` |`password` |Specifies the login method. Available values are `password`, `ldap`, and `cloud`.| - \ No newline at end of file +| TOSS | The TOSS (Transaction on Storage Side) function is used to ensure the final consistency of the `INSERT`, `UPDATE`, or `UPSERT` operations on edges (because one edge logically corresponds to two key-value pairs on the hard disk). The `DELETE` operation is not currently supported. After the TOSS function is enabled, the time delay of related operations will increase by about one time. | From 5034a6515532044798af789f4ba9cd9fc328d8a2 Mon Sep 17 00:00:00 2001 From: "max.zhu@vesoft.com" <86282370+izhuxiaoqing@users.noreply.github.com> Date: Mon, 11 Oct 2021 15:41:08 +0800 Subject: [PATCH 4/4] Update 3.graph-config.md --- .../1.configurations/3.graph-config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md b/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md index 9c1a82402a2..a56d4ebd7c7 100644 --- a/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md +++ b/docs-2.0/5.configurations-and-logs/1.configurations/3.graph-config.md @@ -103,4 +103,4 @@ For all parameters and their current values, see [Configurations](1.configuratio | Name | Description | | ------------------- | ------------------------------------------| -| TOSS | The TOSS (Transaction on Storage Side) function is used to ensure the final consistency of the `INSERT`, `UPDATE`, or `UPSERT` operations on edges (because one edge logically corresponds to two key-value pairs on the hard disk). The `DELETE` operation is not currently supported. After the TOSS function is enabled, the time delay of related operations will increase by about one time. | +| TOSS | The TOSS (Transaction on Storage Side) function is used to ensure the final consistency of the `INSERT`, `UPDATE`, or `UPSERT` operations on edges (because one edge logically corresponds to two key-value pairs on the hard disk). The `DELETE` operation is not currently supported. After the TOSS function is enabled, the time delay of related operations will be increased by about one time. |