You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did you do (The steps to reproduce)?
PrintMessageByQueueCommand with the option -d -e
What did you expect to see?
print the right msglist
What did you see instead?
the -e may get a max offset,but consumer.pull(mq, subExpression, offset, 32); this code may return the msg which bigger than the maxoffset
and the option -d -d describe as a string like End timestamp[currentTimeMillis|yyyy-MM-dd#HH:mm:ss:SSS] but acturally it need a long
timestamp = Long.parseLong(value);
Please tell us about your environment:
None.
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
None
The text was updated successfully, but these errors were encountered:
pigpdong
pushed a commit
to pigpdong/rocketmq
that referenced
this issue
Feb 26, 2019
The max offset problem, i suggest you optimize method "PrintMessageByQueueCommand#calculateByTag" and "PrintMessageByQueueCommand#printMessage" to filter the messages which exceed the max offset.
BUG REPORT
PrintMessageByQueueCommand with the option -d -e
print the right msglist
the -e may get a max offset,but consumer.pull(mq, subExpression, offset, 32); this code may return the msg which bigger than the maxoffset
and the option -d -d describe as a string like End timestamp[currentTimeMillis|yyyy-MM-dd#HH:mm:ss:SSS] but acturally it need a long
timestamp = Long.parseLong(value);
None.
None
The text was updated successfully, but these errors were encountered: