zymap commented on PR #17241: URL: https://github.com/apache/pulsar/pull/17241#issuecomment-1226692317
> 1. We are using the PendingReadKey as the key to determining whether the new one is duplicated read or not. It looks can only cover the case that all the subscriptions with the same read position. It will be great if we can have a more general solution for the duplicated reads which able to handle the case like [0, 20], [2, 22] I have an idea about this that is to split the read range into small pieces, then different read can share the pieces to construct their read. There will have a tradeoff, if the pieces are smaller, the different reads will share more. Something like this:  -- 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]
