Lahiru Jayathilake updated ROCKETMQ-124:
    Comment: was deleted

(was: Hi vongosling
I went through the documentation and currently, I am trying the examples listed 
under https://rocketmq.apache.org/ to get an idea about the RocketMQ. Same time 
I am going through the code base for understanding. And also I have already 
subscribed to the dev mailing list. These took little longer because I had my 
end semester exams last week. Hope I am on the right track. Any guidance would 
be very helpful. Thanks :))

> Support non-redundant message delivery mechanism
> ------------------------------------------------
>                 Key: ROCKETMQ-124
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-124
>             Project: Apache RocketMQ
>          Issue Type: Wish
>          Components: rocketmq-broker, rocketmq-client, rocketmq-store
>            Reporter: yukon
>            Priority: Minor
>              Labels: gsoc2018
> The duplicated messages are worrisome. It will cost much if the user needs 
> non-repeating messages.
> In most cases, the user need store the consumer records to judge a message is 
> replicated or not, and the store stage should guarantee strong consistency. 
> As you see, it's very complicated, so support a strict and non-redundant 
> message delivery mechanism is impending.
> In this context, we hope to design a delivery once plugin, say, you could 
> design a global(but need raft guarantee multi-copy data) storage, using the 
> hooker of RocketMQ ConsumeMessageHook to finish the task.

This message was sent by Atlassian JIRA

Reply via email to