[
https://issues.apache.org/jira/browse/ROCKETMQ-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051327#comment-16051327
]
ASF GitHub Bot commented on ROCKETMQ-40:
----------------------------------------
Github user Jaskey commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/40
@dongeforever
what's your opinion for the new listener? Can we just add a method to the
existing interface while which will make the user suffer from compile error
after updating.
If we add a new interface with the ackmode method, what will be a better
name?
@lizhanhui @zhouxinyu @shroman
> AUTO_CLIENT_ACKNOWNLEDGE & CLIENT_ACKNOWLEDGE support
> ------------------------------------------------------
>
> Key: ROCKETMQ-40
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-40
> Project: Apache RocketMQ
> Issue Type: New Feature
> Components: rocketmq-client
> Reporter: Jaskey Lam
> Assignee: Xiaorui Wang
> Fix For: 4.2.0-incubating
>
>
> For now, push consumer only supports DUPS_OK_ACKNOWLEDGE .
> If user wants to AUTO_CLIENT_ACKNOWNLEDGE or CLIENT_ACKNOWLEDGE , he or she
> must use pull consumer which is not easy enough to use.
> push consumer should support AUTO_CLIENT_ACKNOWNLEDGE and CLIENT_ACKNOWLEDGE
> .
> AUTO_CLIENT_ACKNOWNLEDGE : auto ack after consume and persist to broker
> CLIENT_ACKNOWLEDGE : user should ack by itself, consumer will not ack even
> after handle.
> ref: https://docs.oracle.com/cd/E19587-01/821-0029/aeqbk/index.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
