You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by un...@apache.org on 2019/01/15 14:18:28 UTC

[rocketmq.wiki] branch master updated: Updated RIP 8 Consumer RACK Support (markdown)

This is an automated email from the ASF dual-hosted git repository.

unknown pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new b335a90  Updated RIP 8 Consumer RACK Support (markdown)
b335a90 is described below

commit b335a90d80895bc9522d1162953c47c13ab7e565
Author: devilfeng <de...@gmail.com>
AuthorDate: Tue Jan 15 22:18:27 2019 +0800

    Updated RIP 8 Consumer RACK Support (markdown)
---
 RIP-8-Consumer-RACK-Support.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RIP-8-Consumer-RACK-Support.md b/RIP-8-Consumer-RACK-Support.md
index 4cef0c7..1fc140d 100644
--- a/RIP-8-Consumer-RACK-Support.md
+++ b/RIP-8-Consumer-RACK-Support.md
@@ -16,7 +16,7 @@ No
 
 # Why should we do that
 ## Are there any problems of our current project?
-Yes, In our testing environment, some feture will be test in the same time, some of consumer instance will deploy in the different test environment for test different feture, but message will be consumed not our expect consumer instance.
+Yes, In our testing environment, we need test different feture in the same time, so we need deploy different consumer logic instance in the different test environment for test different feture, but message will be consumed not our expect consumer instance.
 ## What can we benefit proposed changes?
 Improve consumer in same Consumer Group Name to support different RACK, producer can specify message RACK when send message.