[ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.5.1

2023-12-17 Thread Chris Bo
The Apache Pulsar team is proud to announce the Reactive client for Apache Pulsar, version 0.5.1. The Reactive client for Apache Pulsar can be used together with any Reactive Streams implementation on the JVM. Examples include Project Reactor / Spring Reactive, Akka Streams, RxJava 3, Vert.x, Smal

Re: [VOTE] PIP-323: Complete Backlog Quota Telemetry

2023-12-17 Thread PengHui Li
+1 (binding) Regards, Penghui On Wed, Dec 13, 2023 at 4:47 PM guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Wed, Dec 13, 2023 at 4:23 PM Asaf Mesika wrote: > > > Hi, > > > > I'm starting the vote for PIP-323, since it has been reviewed by several > > people and all

Re: [DISSCUSS] PIP-325: Add command to abort transaction

2023-12-17 Thread PengHui Li
Hi, Ruihong The proposal looks good to me. Just left a comment about the security considerations. We need to have a clear permission definition for newly added admin API Regards, Penghui On Sun, Dec 17, 2023 at 1:14 AM |海阔天高 <1373544...@qq.com.invalid> wrote: > Hi community, > > > PIP-325 intro

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

2023-12-17 Thread Xiangying Meng
Hi Jiwei Great advice. Thanks for your suggestions and additions. Thanks, Xiangying On Fri, Dec 15, 2023 at 9:41 AM guo jiwei wrote: > Hi Xiangying, >I think we can rename this PIP to: *Introduce `allowed-clusters` and > `topic-policy-synchronized-clusters` to fully support replication

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

2023-12-17 Thread PengHui Li
As I understand, I think the topic is about the granularity and flexibility of the resource hierarchy design. - The namespace level granularity is good for most cases from the start. But the business is changing, and the requirement for flexibility will be engaged. - Moving to another namespace f

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

2023-12-17 Thread PengHui Li
Hi Jiwei, > I think we can rename this PIP to: *Introduce `allowed-clusters` and `topic-policy-synchronized-clusters` to fully support replication on message and topic level* I'm sorry, I don't fully understand your point here. What is the "support replication on message and topic level"? As

Re: [VOTE] PIP-317: Add `bookkeeperDeleted` field to show whether a ledger is deleted from the Bookie while using tiered storage

2023-12-17 Thread Hang Chen
+1 (binding) Regards, Hang PengHui Li 于2023年11月27日周一 09:54写道: > > +1 (binding) > > And please also update the `# Backward & Forward Compatibility` section > as Enrico mentioned. > > Regards, > Penghui > > On Thu, Nov 16, 2023 at 12:47 PM Enrico Olivelli > wrote: > > > +1 > > > > It will be impo

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

2023-12-17 Thread Xiangying Meng
Hi Penghui >I'm sorry, I don't fully understand your point here. What is the "support replication on message and topic level"? >As I understand, are the `allowed-clusters` and `replication-clusters` more concise options? Pulsar support set replication-cluster for per message. After this proposal