Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

2023-12-06 Thread Girish Sharma
Hello Xiangying, On Thu, Dec 7, 2023 at 6:32 AM Xiangying Meng wrote: > Hi Girish, > > What you are actually opposing is the implementation of true topic-level > geo-replication. You believe that topics should be divided into different > namespaces based on replication. Following this line of

Re: [DISCUSS] Strategy for pushing the latest tag to Pulsar docker images

2023-12-06 Thread Zixuan Liu
Hi Zike, > I prefer the 1st way as well. +1 Thanks, Zixuan Yunze Xu 于2023年12月5日周二 20:26写道: > I prefer the 1st way as well. > > Thanks, > Yunze > > On Tue, Dec 5, 2023 at 5:11 PM Zike Yang wrote: > > > > Hi, everyone, > > > > There seems to be a gap in our current release process concerning

[VOTE] DotPulsar Release 3.1.1 RC 1

2023-12-06 Thread tison
Hi everyone, This is a quick fix patch release for exactly https://github.com/apache/pulsar-dotpulsar/commit/f35e6824f0790696bf4300dcd7a00967cf6c250e : Fixed a bug where disposing a disconnected consumer, reader or producer would cause a hang Please review and vote on the release candidate #1

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

2023-12-06 Thread Xiangying Meng
Hi Girish, What you are actually opposing is the implementation of true topic-level geo-replication. You believe that topics should be divided into different namespaces based on replication. Following this line of thought, what we should do is restrict the current topic-level replication

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

2023-12-06 Thread Girish Sharma
Hello, replies inline. On Wed, Dec 6, 2023 at 5:28 PM Xiangying Meng wrote: > Hi Girish, > > Thank you for your explanation. Because Joe's email referenced the current > implementation of Pulsar, I misunderstood him to be saying that this > current implementation is not good. > > A possible use

[DISCUSS] Depreciation of redundant newAck() methods

2023-12-06 Thread Umut Bilal Okur
Hello folks, We have 8 methods to create an acknowledge command. We should consider checking which one is redundant. PR I will add comments for links ASAP. Thanks, Umut Bilal Okur

[DISCUSS] PIP-322: Pulsar Rate Limiting Refactoring

2023-12-06 Thread Lari Hotari
Dear Pulsar community, As a follow-up to the action point of the Pulsar Community Meeting on 2023/11/23, I have created "PIP-322: Pulsar Rate Limiting Refactoring" and a draft PR with the proposed refactoring changes. PIP-322 document for review: https://github.com/apache/pulsar/pull/21680

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

2023-12-06 Thread Xiangying Meng
Hi Girish, >But the reason why you've raised this PIP is to bring down the actual replication semantics at a topic level. Yes, namespace level still exists as per your PIP as well, but is basically left only to be a "default in case topic level is missing". I'm afraid there's some

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

2023-12-06 Thread Xiangying Meng
Hi Girish, Thank you for your explanation. Because Joe's email referenced the current implementation of Pulsar, I misunderstood him to be saying that this current implementation is not good. A possible use case is where there is one or a small number of topics in the namespace that store

Re: [ANNOUNCE] Apache Pulsar 3.0.2 released

2023-12-06 Thread Zike Yang
Hi, Kiryl Thanks for your catch. I have submitted a PR to fix it: https://github.com/apache/pulsar-site/pull/746 PTAL. Thanks, Zike Yang On Wed, Dec 6, 2023 at 4:41 PM Kiryl Valkovich wrote: > > Congrats on the release! > > Small fixes in the Release table are needed. I raised the issue here:

Re: [ANNOUNCE] Apache Pulsar 3.0.2 released

2023-12-06 Thread Kiryl Valkovich
Congrats on the release! Small fixes in the Release table are needed. I raised the issue here: https://github.com/apache/pulsar/issues/21677 Best, Kiryl From: Yubiao Feng Date: Wednesday, December 6, 2023 at 8:17 AM To: dev@pulsar.apache.org , us...@pulsar.apache.org , annou...@apache.org

[VOTE] Pulsar Client C++ Release 3.4.2 Candidate 1

2023-12-06 Thread Yunze Xu
This is the first release candidate for Apache Pulsar Client C++, version 3.4.2. It fixes the following issues: https://github.com/apache/pulsar-client-cpp/pulls?q=is%3Apr+is%3Aclosed+label%3Arelease%2F3.4.2 *** Please download, test and vote on this release. This vote will stay open for at