Re: [DISCUSS] PIP-345: Optimize finding message by timestamp

Hi Jiuming Firstly, I think the idea you provided is great. It seems the field `beginPublishTimestamp` is also not needed, and there is an existing field `ledgerInfo.timestamp` to use, - The current ledger's timestamp can be used as `beginPublishTimestamp` - The next ledger's timestamp can be use

[ANNOUNCE] Apache Pulsar Client C++ 3.5.0 released

The Apache Pulsar team is proud to announce Apache Pulsar Client C++ version 3.5.0. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor managemen

Re: [DISCUSS] PIP-345: Optimize finding message by timestamp

Hi Yubiao, Thanks for your review! 1. As I mentioned in the *Alternatives* part of the PIP `LedgerInfo#timestamp` is broker's timestamp, finding message by timestamp is client's timestamp(publishTimestamp). We have to consider about client's clock doesn't sync to broker's clock, and we are find