pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] merlimat commented on issue #3643: [client] Support seek at partitioned topic
Date Thu, 21 Feb 2019 08:15:17 GMT
merlimat commented on issue #3643: [client] Support seek at partitioned topic
URL: https://github.com/apache/pulsar/issues/3643#issuecomment-465903549
   > * seeking by earliest / latest can just seek on all partitions. 
   Agree. It doesn't make sense not to support earliest/latest... 
   > 2\. seeking by messageId is also doable. because messageId provides partition id.
   If the seek operation only affects the cursor in one partition, it might become confusing
to a user, since it's a different behavior from the above. 
   In general, I'm not a big fan of seek by message id on the consumer interface, since the
purpose of `Consumer` should be that the reading position is "managed" by the system. If an
application wants to position to a particular message id, it's more of manual handling and
maybe `Reader` is a better option there.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message