You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@rocketmq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/08/10 08:41:00 UTC

[jira] [Commented] (ROCKETMQ-248) ConsumeFromWhere does not always work as expected

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

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

Github user vongosling commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/132
  
    @evthoriz we usually need some measure to verify our correction, no matter what you do. IMO, unit test is a effective practice when we coding. Looking forward to hear from you again :-)


> ConsumeFromWhere does not always work as expected
> -------------------------------------------------
>
>                 Key: ROCKETMQ-248
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-248
>             Project: Apache RocketMQ
>          Issue Type: Improvement
>          Components: rocketmq-broker, rocketmq-client
>    Affects Versions: 4.0.0-incubating, 4.1.0-incubating
>            Reporter: Yu Kaiyuan
>            Assignee: yukon
>
> As a *brand new subscription*, consumer will be allowed to decide where to start the consumption. And the options includes:
> * CONSUME_FROM_LAST_OFFSET
> * CONSUME_FROM_FIRST_OFFSET
> * CONSUME_FROM_TIMESTAMP
> But the fact is the option: `CONSUME_FROM_LAST_OFFSET` does not always work as expected. Even if the subscription is new, the consumer still might consume from the first message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)