I'll start a vote on this pip. This is intended to fix issue，and if we want to implement startMessageIdInclusive() in broker side， this pip will not affect the logic, we can do it in other pip later.
On 2024/10/15 16:47:49 Jiawen Wang wrote: > Thanks for your reply ! > > In my previous thought, this pip will not change the logic in manage ledger > —— still make startMssageId minus one and call > initializeCursorPosition/recoverCursor to read the next valid position, then > the readPosition will be startMessageId (minus one and increase one). keep > the logic unchange and fix issue in a lighter way. > > Today I viewed the PIP-150, and it seems a better implementation for > startMessageInclusive. > I'm not sure about this right now. Maybe we can reopen the pip-150？ > > Thanks > Jiawen Wang > > On 2024/10/11 04:19:37 Zixuan Liu wrote: > > Same PIP: https://github.com/apache/pulsar/issues/14883 > > > > FYI. > > > > Jiawen Wang <15...@163.com> 于2024年10月9日周三 23:43写道： > > > > > Hi dev, I proposed a PIP: https://github.com/apache/pulsar/pull/23427, > > > this pip is intended to fix issue > > > https://github.com/apache/pulsar/issues/23239. > > > > > > Please take a look and give your feedback. > > > > > > > > > > > > Best Regards! > > > Jiawen Wang > >
