You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "Jie.Tang (JIRA)" <ji...@apache.org> on 2017/03/08 07:55:37 UTC
[jira] [Created] (ROCKETMQ-134) the offset of message filter by
tags may be not commit to broker
Jie.Tang created ROCKETMQ-134:
---------------------------------
Summary: 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)