[ 
https://issues.apache.org/jira/browse/ROCKETMQ-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jaskey Lam updated ROCKETMQ-105:
--------------------------------
    Description: 
This issue does not affect all functionality, but it indeed is a problem for 
user to understand the principle  of RocketMQ.

- ConsumerOffset:

User might consider `ConsumerOffset` is the offset where I have consumed. for 
example if CG1 have a consumer offset 100 of topicA-q1, I may propabaly 
consider message with offset 100 has been cosumed. But actully, it is not. The 
message with offset 100 is the next target when I pull from.

- Max Offset

User might consider this is the offset of the latest message in a queue. But it 
is not, it is indicating that next offset when new message arrived.

If possible , any of the below two things should be taken into consideration

1. the implementaion should be changed to be closer to the presentative 
judgment of human

2. rename the concept to clarify how it really implemented.


  was:
This issue does not affect all functionality, but it indeed is a problem for 
user to understand the principle  of RocketMQ.

- ConsumerOffset:

User might consider **ConsumerOffset** is the offset where I have consumed. for 
example if CG1 have a consumer offset 100 of topicA-q1, I may propabaly 
consider message with offset 100 has been cosumed. But actully, it is not. The 
message with offset 100 is the next target when I pull from.

- Max Offset

User might consider this is the offset of the latest message in a queue. But it 
is not, it is indicating that next offset when new message arrived.

If possible , any of the below two things should be taken into consideration

1. the implementaion should be changed to be closer to the presentative 
judgment of human

2. rename the concept to clarify how it really implemented.



> Implementation of consumerOffset and maxOffset are counter-intuitive
> --------------------------------------------------------------------
>
>                 Key: ROCKETMQ-105
>                 URL: https://issues.apache.org/jira/browse/ROCKETMQ-105
>             Project: Apache RocketMQ
>          Issue Type: Wish
>          Components: rocketmq-broker, rocketmq-client, rocketmq-store
>    Affects Versions: 4.0.0-incubating
>            Reporter: Jaskey Lam
>            Assignee: yukon
>            Priority: Minor
>
> This issue does not affect all functionality, but it indeed is a problem for 
> user to understand the principle  of RocketMQ.
> - ConsumerOffset:
> User might consider `ConsumerOffset` is the offset where I have consumed. for 
> example if CG1 have a consumer offset 100 of topicA-q1, I may propabaly 
> consider message with offset 100 has been cosumed. But actully, it is not. 
> The message with offset 100 is the next target when I pull from.
> - Max Offset
> User might consider this is the offset of the latest message in a queue. But 
> it is not, it is indicating that next offset when new message arrived.
> If possible , any of the below two things should be taken into consideration
> 1. the implementaion should be changed to be closer to the presentative 
> judgment of human
> 2. rename the concept to clarify how it really implemented.



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

Reply via email to