You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by wl...@apache.org on 2019/03/13 07:15:31 UTC
[rocketmq] branch develop updated: [RIP-9] Modify English document
for Design_Trancation.md
This is an automated email from the ASF dual-hosted git repository.
wlliqipeng pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
The following commit(s) were added to refs/heads/develop by this push:
new cf2a40b [RIP-9] Modify English document for Design_Trancation.md
new 1b39485 Merge pull request #1072 from JJFighting/develop
cf2a40b is described below
commit cf2a40bffd33af5f217a4e36af6e84b80aab0cd5
Author: JJ <it...@foxmail.com>
AuthorDate: Mon Mar 11 17:35:03 2019 +0800
[RIP-9] Modify English document for Design_Trancation.md
---
docs/en/Design_Trancation.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/en/Design_Trancation.md b/docs/en/Design_Trancation.md
index e5f10ed..71cdabe 100644
--- a/docs/en/Design_Trancation.md
+++ b/docs/en/Design_Trancation.md
@@ -36,7 +36,7 @@ The compensation phase is used to resolve the timeout or failure case of the mes
3. How Op message stored and the correspondence between Op message and Half message
- RocketMQ writes the Op message to a specific system topic(RMQ_SYS_TRANS_OP_HALF_TOPIC) which will be created via the method - TransactionMessageUtil.buildOpTopic(); this topic is an internal Topic (like the topic of RMQ_SYS_TRANS_HALF_TOPIC) and will not be consumed by the user. The content of the Op message is the physical offset of the corresponding Half message. Through the Op message we can index to the Half message for subsequent check-back operation.
+ RocketMQ writes the Op message to a specific system topic(RMQ_SYS_TRANS_OP_HALF_TOPIC) which will be created via the method - TransactionalMessageUtil.buildOpTopic(); this topic is an internal Topic (like the topic of RMQ_SYS_TRANS_HALF_TOPIC) and will not be consumed by the user. The content of the Op message is the physical offset of the corresponding Half message. Through the Op message we can index to the Half message for subsequent check-back operation.
