[DISCUSS] PIP-245: Subscriptions expiration for NonPersistentTopic only

Hi, I’ve opened a new PIP to discuss: Currently, in Pulsar, we have a configuration named `subscriptionExpirationTimeMinutes` to manage the subscription expiration of `PersistentTopic` and `NonPersistentTopic`. When we set a value which is greater than 0 to `subscriptionExpirationTimeMinutes`

[Discuss] Review the new structure of client library documentation

Hi everyone, To improve the developer experience and onboard Pulsar users more efficiently, I proposed PIP-228 to refactor the client library documentation [1] and got three binding votes [2]. @RobertIndie and I have been working on implementing the information architecture changes through thi

[DISCUSS] Fix OAuth2 regression for C++, Python, Node.js clients

Hi all, Recently I found a serious bug for OAuth2 authentication [1]. Here are some related issues: [2], [3]. The affected client versions are: - C++ client 3.0.0, 3.1.0, 3.1.1 - Python client 3.0.0 - Node.js client 1.8.0 Users have to downgrade back to old releases, which might suffer the CVE-20

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

The Apache Pulsar team is proud to announce the Reactive client for Apache Pulsar, version 0.2.0. 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: [DISCUSS] PIP-245: Subscriptions expiration for NonPersistentTopic only

I think we are talking about the durable subscription of the non-persistent topic, right? For the Reader API (non-durable subscription), the subscription will be removed after the reader disconnects. If not, it should be BUG. IMO, we should remove the subscription automatically if all the consumer

Re: [VOTE] PIP-237: Make PulsarAdmin accessible in SinkContext and SourceContext

+1 Best, Rui Fu On Jan 30, 2023 at 19:12 +0800, Alexander Preuss , wrote: > Now that the DISCUSSION thread has received some more input and some time > has passed I would like to start the VOTE again. > > Best, > Alexander > > On Tue, Jan 17, 2023 at 3:21 AM Bonan Hou > wrote: > > > +1 > > > >

Re: [DISCUSS] PIP-245: Subscriptions expiration for NonPersistentTopic only

Penghui, Il giorno mar 7 feb 2023 alle ore 12:58 PengHui Li ha scritto: > > I think we are talking about the durable subscription of the non-persistent > topic, right? For the Reader API (non-durable subscription), the > subscription will be > removed after the reader disconnects. If not, it shou

Re: [ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.2.0

Congratulations ! This is another great step forward for the Pulsar community. Looking forward for the official Spring Integration that will leverage this client Enrico Il giorno mar 7 feb 2023 alle ore 12:04 Christophe Bornet ha scritto: > > The Apache Pulsar team is proud to announce the Rea

Re: [DISCUSS] PIP-245: Subscriptions expiration for NonPersistentTopic only

> I think we are talking about the durable subscription of the non-persistent > topic, right? Yes, non-durable subscriptions created by Reader, if the reader disconnected, the subscription will be deleted automatically. For `NonPersistentDispatcher`, it has the following implementations: 1. Non

Re: [DISCUSS] PIP-245: Subscriptions expiration for NonPersistentTopic only

> I think we are talking about the durable subscription of the non-persistent > topic, right? Yes, non-durable subscriptions created by Reader, if the reader disconnected, the subscription will be deleted automatically. For `NonPersistentDispatcher`, it has the following implementations: 1. Non

Pulsar Flaky test report 2023-02-07 for PR builds in CI

Dear community, Here's a report of the flaky tests in Pulsar CI during the observation period of 2023-01-31 - 2023-02-07 https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07 More flaky test issues: https://github.com/apache/pulsar/issues?q=flaky+sort%3Aupdated-desc+i

Re: [DISCUSS] Redundant ServiceUrlProvider design and improper use of PIP-121

Oh, thanks Baodi - now I understand what he meant by "calling rebuild". I agree, it's not very intuitive. Maybe? client.update(ConnectionInfo.builder() .setServiceUrl() .set...() .build()) On Mon, Feb 6, 2023 at 2:39

Re: [DISCUSS] PIP-186: Introduce two phase deletion protocol based on system topic

On Sun, Feb 5, 2023 at 2:26 AM Yan Zhao wrote: > On 2023/02/03 18:14:53 Heesung Sohn wrote: > > There are some cases to trigger it. > > 1. A cursor be removed. > > 2. Close the current ledger and create a new ledger. > > 3. Consumer ack the message, the slowest cursor move forward. > > 4. User tr

Re: Pulsar Flaky test report 2023-02-07 for PR builds in CI

Thanks for compiling the report Nicolo. What are the 10 most flaky tests? It wasn't obvious to me from the email. I'd like to suggest that we prioritize fixing the 10 most flaky ones. -Lari ti 7. helmik. 2023 klo 17.43 Nicolò Boschi kirjoitti: > Dear community, > Here's a report of the flaky t

Re: [DISCUSS] Redundant ServiceUrlProvider design and improper use of PIP-121

Hi, Asaf. Maybe? > > client.update(ConnectionInfo.builder() > .setServiceUrl() > .set...() > .build()) Yes, This is clearer. Thanks, Baodi Shi 在 2023年2月7日 23:48:03 上，Asaf Mesika 写道： > Oh, thanks Baodi - now I unders

Re: [DISCUSS] PIP-245: Subscriptions expiration for NonPersistentTopic only

I agree to remove all subscriptions when there're no consumers on the non-persistent topic. The configuration `subscriptionExpirationTimeMinutes ` should not take effect on the non-persistent topic. But it seems that currently all Durable subscriptions on non-persistent topics are NonDurable, and

Pulsar Cpp client release 3.1.2

Hi all, There is a serious OAuth2 authentication regression [1] for all existing C++ client 3.x.y releases. I see many users tend to downgrade to old versions like 2.10.2. This behavior is dangerous because of the CVE. The fix [2] is now merged, so I decided to start a 3.1.2 release ASAP, though

Re: Pulsar Cpp client release 3.1.2

+1 -- Matteo Merli On Tue, Feb 7, 2023 at 6:49 PM Yunze Xu wrote: > > Hi all, > > There is a serious OAuth2 authentication regression [1] for all > existing C++ client 3.x.y releases. I see many users tend to downgrade > to old versions like 2.10.2. This behavior is dangerous because of the > CV

Re: Pulsar Cpp client release 3.1.2

+1 Thanks, Zike Yang On Wed, Feb 8, 2023 at 11:08 AM Matteo Merli wrote: > > +1 > -- > Matteo Merli > > > On Tue, Feb 7, 2023 at 6:49 PM Yunze Xu wrote: > > > > Hi all, > > > > There is a serious OAuth2 authentication regression [1] for all > > existing C++ client 3.x.y releases. I see many us

Re: Pulsar Cpp client release 3.1.2

+1, thank you for fixing this issue, Yunze. - Michael On Tue, Feb 7, 2023 at 9:11 PM Zike Yang wrote: > > +1 > > Thanks, > Zike Yang > > On Wed, Feb 8, 2023 at 11:08 AM Matteo Merli wrote: > > > > +1 > > -- > > Matteo Merli > > > > > > On Tue, Feb 7, 2023 at 6:49 PM Yunze Xu > > wrote: > > >

Re: [DISCUSS] PIP-237: Make PulsarAdmin accessible in SinkContext and SourceContext

This proposal makes sense to me. I am +1 on option B. Thanks, Michael On Wed, Feb 1, 2023 at 2:42 AM Alexander Preuss wrote: > > Thanks to everyone for providing their input. Please vote on the VOTE > thread https://lists.apache.org/thread/ykfnfb1pv4bcxwr6lwb4klc3byq71t13 > > Many thanks, > Alex

Re: [VOTE] PIP-237: Make PulsarAdmin accessible in SinkContext and SourceContext

+1 (binding) Thanks, Michael On Tue, Feb 7, 2023 at 7:00 AM Rui Fu wrote: > > +1 > > Best, > > Rui Fu > On Jan 30, 2023 at 19:12 +0800, Alexander Preuss > , wrote: > > Now that the DISCUSSION thread has received some more input and some time > > has passed I would like to start the VOTE again.