lhotari commented on issue #23661: URL: https://github.com/apache/pulsar/issues/23661#issuecomment-2507421178
> In Pulsar, if client didn't set a specific value, the expected is Latest. But in the situation above, subscription was created with earliest position. Since this is existing behavior in the API that you are using, it would be a breaking change to change it. It's better to solve this type of cases by documenting the behavior instead of changing the default behavior. The value is set to latest in the Java Admin client code: https://github.com/apache/pulsar/blob/fe4274842465f922a5bdac40294b84b1c9fddc94/pulsar-client-admin/src/main/java/org/apache/pulsar/client/admin/internal/TopicsImpl.java#L1077-L1078 It's not impossible to change the default behavior in the broker side code, but that would [require a Pulsar Improvement Proposal (PIP)](https://github.com/apache/pulsar/tree/master/pip#when-is-a-pip-required). Is it really worth it? -- 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]
