wenbingshen commented on issue #14559: URL: https://github.com/apache/pulsar/issues/14559#issuecomment-1061383201
> Looks like a similar problem that https://github.com/apache/pulsar/wiki/PIP-84-:-Pulsar-client:-Redeliver-command-add-epoch want to resolve. Thanks for your reply. It looks a bit similar, but the two are slightly different. PIP-84 seems to only emphasize the synchronization consistency of data retransmission and data pull, but has no details about the seek operation. If you mean adding an epoch to the seek operation, assuming that the epoch of the seek operation is `1`, the broker will disconnect the client when the seek operation starts, and the epoch will be `2` when the client resubscribe the subscription again. The `FLOW` request at this time will cause the broker to start reading data and return it to the client. The client seems to have no way to filter out the data with epoch `2`, and then the broker completes the seek operation with epoch `1`. -- 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]
