You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "Jaskey Lam (JIRA)" <ji...@apache.org> on 2017/03/09 10:01:37 UTC

[jira] [Updated] (ROCKETMQ-136) Provide a handy message queue selector for order message sharding

     [ https://issues.apache.org/jira/browse/ROCKETMQ-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaskey Lam updated ROCKETMQ-136:
--------------------------------
    Description: 
When order message is needed, users need to provide a message queue selector to make sure that the messages which has the same shading key should be sent to the same message queue.

Actually this is a very common scenario with a common solutions, say consistent hashing.

We should provide a handy selector for them to easily do that, what they only need to provide is a sharding key.

A consistent hash selector will meet most of the user's need.

  was:
When order message is needed, users need to provide a message queue selector to make sure that the messages which has the same shading key should be sent to the same message queue.

Actually this is a very common scenario with a common solutions, say consistent hashing.

We should provide a handy selector for them to easily do that, what they only need to provide is a shading key.

A consistent hash selector will meet most of the user's need.


> Provide a handy message queue selector for order message sharding
> -----------------------------------------------------------------
>
>                 Key: ROCKETMQ-136
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-136
>             Project: Apache RocketMQ
>          Issue Type: Improvement
>          Components: rocketmq-client
>    Affects Versions: 4.1.0-incubating
>            Reporter: Jaskey Lam
>            Assignee: Jaskey Lam
>            Priority: Minor
>
> When order message is needed, users need to provide a message queue selector to make sure that the messages which has the same shading key should be sent to the same message queue.
> Actually this is a very common scenario with a common solutions, say consistent hashing.
> We should provide a handy selector for them to easily do that, what they only need to provide is a sharding key.
> A consistent hash selector will meet most of the user's need.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)