yebai1105 commented on issue #20954:
URL: https://github.com/apache/pulsar/issues/20954#issuecomment-1672480290

   > When you create a subscription, the latestMessageId will be converted to 
the lastConfirmedEntry, you can seek position to lastestMessageId again before 
consuming.
   
   Your method can be useful, but you need to actively update cursor.
   But my problem is: when create subscription set "latest" the expectation 
should be the first time it consumes it should start consuming from the latest 
message,otherwise it should not be named "latest". Its effect is hidden and 
somewhat misleading to use, I think the position of the first consumption 
should not be related to the time of creating the subscription, for real-time 
tasks, this will consume a lot of uncontrollable historical data.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to