mattisonchao commented on issue #25041: URL: https://github.com/apache/pulsar/issues/25041#issuecomment-3642084665
> I think set the consumer's default start position to "earliest" maybe is not a good way, that would bring a huge compatibility problem, since pulsar and other message queue such as kafka, always set default start position to "latest". And so many pulsar-client's compatibility would be break. low version client may lost message when topic partition updated. Yes, we won't do that. > If just change the start position in client#autoUpdatePartitions module, that's not complete since maybe pulsar-server update partition, client may restart and use default start position "latest" to connect. You are right, `client may restart and use the default start position "latest" to connect.` Here's the main concern. :/ Anyway, I checked the codes, and it seems that we will create a topic from metadata directly, which is good because it will bypass the broker topic creation `-partition-` keyword rejection. We could apply your fix to fix the risky issue first, then discuss how to improve this endpoint, which has many intermediate states left if the operation is interrupted. -- 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]
