Re: [VOTE] PIP-332: peek messages from topic subscription with offset value

+1 (binding) The proposal overall LGTM. But since the PIP itself and its implementation are coupled in the same PR, I left minor comments in that PR directly, which does not affect my +1. Thanks, Yunze On Mon, Mar 11, 2024 at 11:04 AM Yubiao Feng wrote: > > +1 (binding) > > Thanks > Yubiao Feng

Re: [VOTE] PIP-332: peek messages from topic subscription with offset value

+1 (binding) Thanks Yubiao Feng On Tue, Mar 5, 2024 at 11:38 PM Balaji Lakshmanan wrote: > Hi, > > This is the vote for the PIP-332 to peek messages from a topic subscription > with an offset value. > > Can you please reply with your vote? > > Here is the link to the PIP pull request >

[ANNOUNCE] Apache Pulsar 3.0.3 released

The Apache Pulsar team is proud to announce Apache Pulsar version 3.0.3. 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 management for subsc

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

Asaf and Dave, thank you for your responses. The proposed version menu structure looks good to me: - Next - active versions still in support - Others If there will be no more input, I’m going to submit the PR in the upcoming week. I updated the redirect and the release process instructions. Pl

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I like the notion of not updating documentation for versions that are out of EOL unless the documentation is incorrect. The only versions that should be on the documentation pop-up on https:/pulsar.apache.org/docs/x,y,z/ should be: - Next - active versions

Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika

> > I have selected these examples from the most recent discussions and they > may not be the best examples to fully illustrate the point. You should respect people's time by taking the time to craft your replies in this discussion. >From my experience, I've been contributing a lot in recent year

Re: [DISCUSS] Clarify the relation between supported Pulsar versions and versioned docs

I personally agree it is frustrating to update in multiple places. It's not time consuming, just annoying. Maybe we can only update for the support LTS version and onwards? On Mar 6 2024, at 1:56 pm, Kiryl Valkovich wrote: > Idea: don't require updating versioned docs from contributors. > Making