yapxue commented on PR #17071: URL: https://github.com/apache/pulsar/pull/17071#issuecomment-1214524222
> The sequence ID will reset to 0 after the input topic have been re-created. Does this will impact the function if the output topic haven't been re-created? Because the new data writing to output topic always with the lower sequenceID. > > The `getSequenceId` is different, because the message ID is guaranteed to be monotonically increasing within a cluster. Any suggestions to make index persistent anywhere else to survive topic recreation? Or just use ledgerId+entryId+batchIndex as sequenceId ? I am afraid 24 bits for ledgerId may overflow for large clusters. -- 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]
