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

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

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/132
  
    
    [![Coverage 
Status](https://coveralls.io/builds/12789603/badge)](https://coveralls.io/builds/12789603)
    
    Coverage increased (+0.2%) to 38.926% when pulling 
**f7b7b5b1d8b7536f69504fd9bbe68d2511d8865f on evthoriz:develop-my** into 
**98bd032454c9dd01bcaea0f4c92abfa0b1847bac on apache:develop**.



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

Reply via email to