geniusjoe commented on PR #1340: URL: https://github.com/apache/pulsar-client-go/pull/1340#issuecomment-2706198300
> If any user depends on the existing `seek` behavior (inclusive by default), he/she might treat it as a "message lost" issue. > > This behavior change is beyond the scope of this PR. I also think it needs a discussion at the mail list. We also need to document the change and tell existing users to set `startMessageInclusive` with true to keep the old behavior. But it's still a breaking change because if `startMessageInclusive` is true, the behavior of subscribing also changes. > > Therefore, my opinion is to keep the existing seek behavior not changed for now. The "fix" could be delayed to next release. I'm not very sure what do you mean "message lost"? Compared to current fixes, does previous behavior continue to consume messages regardless of `seek()` happened, or just continue to consume messages in client cache and then jump to consume the position which `seek()` defined? -- 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: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
