[jira] [Commented] (ROCKETMQ-134) the offset of message filter by tags may be not commit to broker

[ASF GitHub Bot (JIRA)]

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

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

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/72
  
    
    [![Coverage 
Status](https://coveralls.io/builds/10498533/badge)](https://coveralls.io/builds/10498533)
    
    Changes Unknown when pulling **a4e22b6d8008ab0402b9e1909ef4c8061b8e9908 on 
StyleTang:message-tags** into ** on apache:master**.



> the offset of message filter by tags may be not commit to broker
> ----------------------------------------------------------------
>
>                 Key: ROCKETMQ-134
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-134
>             Project: Apache RocketMQ
>          Issue Type: Bug
>          Components: rocketmq-client
>    Affects Versions: 4.0.0-incubating
>            Reporter: Jie.Tang
>            Assignee: Xiaorui Wang
>            Priority: Trivial
>
> when different string has a same hash code.the message commit offset of 
> filtered message may be not commit to broker.
> for example:
> 1.consumer pull message from broker, broker return status FOUND and messages 
> filter by tags hash code
> 2.consumer client get the messages and than processPullResult will filter 
> message by tags.
> 3.PullCallback may get a pullResult which status is FOUND but messageList is 
> empty.(filter by tags)
> but only NO_MATCHED_MSG and NO_NEW_MSG will correctTagsOffset
> we can't commit the right with status of FOUND(for messageList is empty).
> Is that so?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)