ConcurrencyPractitioner commented on issue #3983: [Issue#3976] [component/client] Adding config for ReaderImpl URL: https://github.com/apache/pulsar/pull/3983#issuecomment-483032373 Alright, so here is my current approach on the issue. ```resetCursor``` is known to cause the consumer to disconnect. That might've been the cause of why we are starting to process from my-message-0 despite the seek call. So what I have done is that during the ```subscribe``` command, I match the start publish time with the message id ```startId``` that is the closest to it, and then I will call ```getNonDurableSubscription(MessageId startMessageId)``` to create the subscription where startMessageId equals ```startId```. That is the basic approach that I'm currently doing.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
