This is an automated email from the ASF dual-hosted git repository.
luzhijing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git
The following commit(s) were added to refs/heads/master by this push:
new 5db0b66bd9 update doc (#18871)
5db0b66bd9 is described below
commit 5db0b66bd9d5caa554e67912fd4790a473a05c7e
Author: wudi <[email protected]>
AuthorDate: Fri Apr 21 23:04:27 2023 +0800
update doc (#18871)
Co-authored-by: wudi <>
---
docs/en/docs/data-operate/update-delete/update.md | 1 +
docs/zh-CN/docs/data-operate/update-delete/update.md | 1 +
2 files changed, 2 insertions(+)
diff --git a/docs/en/docs/data-operate/update-delete/update.md
b/docs/en/docs/data-operate/update-delete/update.md
index 0b09d66bc6..149d4ea013 100644
--- a/docs/en/docs/data-operate/update-delete/update.md
+++ b/docs/en/docs/data-operate/update-delete/update.md
@@ -63,6 +63,7 @@ The main reason for this is that Doris currently supports row
updates, which mea
This presents a problem in that if two Update operations update the same row
at the same time, the behavior may be indeterminate. That is, there may be
dirty data.
However, in practice, the concurrency limit can be turned on manually if the
user himself can guarantee that even if concurrent updates are performed, they
will not operate on the same row at the same time. This is done by modifying
the FE configuration ``enable_concurrent_update``. When the configuration value
is true, there is no limit on concurrent updates.
+> Note: After enabling the configuration, there will be certain performance
risks. You can refer to the performance section above to improve update
efficiency.
## Risks of use
diff --git a/docs/zh-CN/docs/data-operate/update-delete/update.md
b/docs/zh-CN/docs/data-operate/update-delete/update.md
index 1faeafe7c1..3e7a610765 100644
--- a/docs/zh-CN/docs/data-operate/update-delete/update.md
+++ b/docs/zh-CN/docs/data-operate/update-delete/update.md
@@ -58,6 +58,7 @@ Update 语句的性能和待更新的行数以及 condition 的检索效率密
这就会存在一个问题，如果同时有两个 Update 操作对同一行进行更新，那么其行为可能是不确定的，也就是可能存在脏数据。
但在实际应用中，如果用户自己可以保证即使并发更新，也不会同时对同一行进行操作的话，就可以手动打开并发限制。通过修改 FE 配置
`enable_concurrent_update`，当配置值为 true 时，则对更新并发无限制。
+>注：开启配置后，会有一定的性能风险，可参考上面的性能小节部分，提升更新效率。
## 使用风险
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
