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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user Jaskey opened a pull request:

    https://github.com/apache/incubator-rocketmq/pull/149

    [ROCKETMQ-136]Provide a handy message queue producer for order message sharding

    jira: https://issues.apache.org/jira/browse/ROCKETMQ-136
    
    
    implementation brief: provide a OrderMessageProducer which need to implement an abstract method `sharingKey` and use a consistent hash selector to select a mq to send.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Jaskey/incubator-rocketmq ROCKETMQ-136-order-message

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-rocketmq/pull/149.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #149
    
----
commit c3388ab4a457dacab59815675a2ad98270ef6159
Author: Jaskey <li...@gmail.com>
Date:   2017-08-18T10:31:49Z

    [ROCKETMQ-136]Provide a handy message queue producer for order message sharding

----


> 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)