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

[ASF GitHub Bot (JIRA)]

    [ 
https://issues.apache.org/jira/browse/ROCKETMQ-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16132067#comment-16132067
 ] 

ASF GitHub Bot commented on ROCKETMQ-136:
-----------------------------------------

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/149
  
    
    [![Coverage 
Status](https://coveralls.io/builds/12892225/badge)](https://coveralls.io/builds/12892225)
    
    Coverage increased (+0.1%) to 39.213% when pulling 
**25f8951ecf2e3e0719d16ef91a9c930635624dad on 
Jaskey:ROCKETMQ-136-order-message** into 
**332df78e2bb6caadfc6f4714450000ebb1f9d224 on apache:develop**.



> Provide a handy message queue producer 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
>             Fix For: 4.2.0-incubating
>
>
> 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.4.14#64029)