Github user Jaskey commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/53
@dongeforever
I have the same wishes for batch send too, but what drives me is that user
may propably need a batch id for one batch of message, and these message should
be success all to one single queue, which is nessecary when sneding order
message. say msgA msgB and msgC should be consumed in order, they should be
send to one same queue, but if we use for loop to send this, A may success and
B may fail to the same queue since the queue numbers may changes at that exctly
time.
Batch send could solve this problem. But we may also need to generate a
uniq batch id for this in client, which will help us to optimze the performance
of consumeorderlyservice in the furture. Currently, message in one single queue
can only be consumed only if the previous one consumed successfully which
actually is too strict. Actully we only need the message in one batch consumed
in order, batch id will help us to do this.
**So in general, I suggest adding batch id when sending batch message in
all message property.**
PS: There looks like two many repeated code, any ways or plans to clean it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
