[
https://issues.apache.org/jira/browse/ROCKETMQ-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279839#comment-16279839
]
ASF GitHub Bot commented on ROCKETMQ-324:
-----------------------------------------
coveralls commented on issue #201: [ROCKETMQ-324] Expose an interface for
client to specify the async call back executor
URL: https://github.com/apache/rocketmq/pull/201#issuecomment-349570319
[](https://coveralls.io/builds/14524951)
Coverage decreased (-0.04%) to 39.224% when pulling
**37cf2a7cb706a0cfe5b217940467c4a9cb33626e on zhouxinyu:ROCKETMQ-324** into
**8c303104830afe53721fad231e671fc12670df8c on apache:develop**.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Expose an interface for client to specify the async call back executor
> ----------------------------------------------------------------------
>
> Key: ROCKETMQ-324
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-324
> Project: Apache RocketMQ
> Issue Type: Improvement
> Components: rocketmq-client
> Affects Versions: 4.0.0-incubating, 4.1.0-incubating
> Reporter: yukon
> Assignee: yukon
> Fix For: 4.2.0
>
>
> Currently, the async call back will be executed in a public executor which is
> mainly used in CHECK_TRANSACTION_STATE, NOTIFY_CONSUMER_IDS_CHANGED,
> CONSUME_MESSAGE_DIRECTLY, etc. More details please refer to MQClientAPIImpl.
> Should expose an interface for client to specify the independent call back
> executor.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
