Re: [DISCUSS] Code freeze for Pulsar 2.12

> Following PIP-175, we have to provide the first LTS release which will be 3.0. Actuall as discussed in [1], the first LTS release is 2.10 for being the last Java 8 release. The major version 3.0 bump would simply signal the type of the release. I think we should make a VOTE on PIP-175 officiall

Re: [DISCUSS] Release Pulsar 2.10.4

+1, It's about 3 months since the discussion of the 2.10.3 release. Haiting On Wed, Feb 1, 2023 at 11:26 AM Xiangying Meng wrote: > > Hello, Pulsar community: > > I'd like to propose releasing Apache Pulsar 2.10.4. It's been about one > month since 2.10.3 was released. > > There are 45 PRs [0] n

Re: [ANNOUNCE] Nicolò Boschi as new PMC member in Apache Pulsar

Congrats, Nicolò! BR, Haiting On Thu, Feb 2, 2023 at 8:01 AM Devin Bost wrote: > > Congrats! > > -- > Devin Bost > Sent from mobile > Cell: 801-400-4602 > > On Wed, Feb 1, 2023, 6:07 AM r...@apache.org > wrote: > > > Congratulations! > > > > -- > > Thanks > > Xiaolong Ran > > > > Qiang Huang 于

Re: [DISCUSS] Topic name restriction

Thanks for starting this thread, Mattison. > The topic name character validation is already done by > `NamedEntity#checkName`. Based on my reading of the code, only the tenant and the namespace names are validated using that method. There is a call [0] that looks like it validates topic names, bu

Re: [DISCUSS] Topic name restriction

Hi Mattison: Agree with Yong's idea. We can expose `disallowed topic` as a configuration to the user side, and a more flexible way is to expose it as a namespace-level policy. This can ensure that there is no need to do special processing on customized keywords in the future, and the expected effe

Re: [VOTE] PIP-241: TopicEventListener / topic events for the BrokerService.

Passed by 5 binding votes. Voting is closed. Thank you all! On Tue, Jan 24, 2023 at 8:13 AM Andrey Yegorov wrote: > I am starting VOTE for the proposed implementation of PIP-241. > > https://github.com/apache/pulsar/pull/19153 for PIP-241: > TopicEventListener / topic events for > the BrokerSer

Re: [DISCUSS] Topic name restriction

Sent from my iPhone > On Feb 1, 2023, at 6:52 PM, Yong Zhang wrote: > > Mattison, > > I agree with you about restricting the topic name. > > How about using a blacklist way to restrict it? If we do then please call it by another name like “disallowed”. > > We can have a blacklist on the

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 1

I see. It's a miss of the release process. I think we need a step to update the `__about__.py` (like the commit that updates the `version.txt` before), I will start a new candidate soon. Thanks, Yunze On Thu, Feb 2, 2023 at 12:50 AM Matteo Merli wrote: > > The wheels work fine (tested Mac & Linu

Re: [DISCUSS] Topic name restriction

The topic name character validation is already done by `NamedEntity#checkName`. And I agree that the system topic should be taken carefully as well. But I have a concern that whether we should treat all topics that start with the long underscore ("__") as system topics? Users might have defined the

Re: [DISCUSS] Topic name restriction

Mattison, I agree with you about restricting the topic name. How about using a blacklist way to restrict it? We can have a blacklist on the topic name restriction and make it configurable. Add the keywords you mentioned in the default configuration. That would have a more general way to block a

Re: [ANNOUNCE] Nicolò Boschi as new PMC member in Apache Pulsar

Congrats! -- Devin Bost Sent from mobile Cell: 801-400-4602 On Wed, Feb 1, 2023, 6:07 AM r...@apache.org wrote: > Congratulations! > > -- > Thanks > Xiaolong Ran > > Qiang Huang 于2023年2月1日周三 10:16写道： > > > Congratulations !!! > > > > Zike Yang 于2023年1月30日周一 16:41写道： > > > > > Congratulations!

[DISCUSS] Topic name restriction

Hi, All In the current implementation, pulsar didn't support topic name restriction. It's a good chance to discuss it. I think this discussion aims to identify what types of topic names we all need to restrict. I know three topic names that need to be restricted at the moment. 1. The `-partit

[VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 2

This is the release candidate 2 for the Reactive Java client for Apache Pulsar, version 0.2.0. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag). Binaries in the Maven repository are provided for co

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 1

The wheels work fine (tested Mac & Linux) and the checksums are all correct, though the version is `3.1.0a1`. We need to remove `a1` for final release that are uploaded to PyPI -- Matteo Merli On Wed, Feb 1, 2023 at 1:00 AM Yunze Xu wrote: > > This is the 1st release candidate for Apache Pulsar

Re: [ANNOUNCE] Nicolò Boschi as new PMC member in Apache Pulsar

Congratulations! -- Thanks Xiaolong Ran Qiang Huang 于2023年2月1日周三 10:16写道： > Congratulations !!! > > Zike Yang 于2023年1月30日周一 16:41写道： > > > Congratulations! > > > > BR, > > Zike Yang > > > > On Mon, Jan 30, 2023 at 3:16 PM houxiaoyu wrote: > > > > > > Congratulations ! > > > > > > Best > > > X

[VOTE] Pulsar Client Python Release 3.1.0 Candidate 1

This is the 1st release candidate for Apache Pulsar Client Python, version 3.1.0. It fixes the following issues: https://github.com/apache/pulsar-client-python/milestone/2?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Python wheel

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

Thanks to everyone for providing their input. Please vote on the VOTE thread https://lists.apache.org/thread/ykfnfb1pv4bcxwr6lwb4klc3byq71t13 Many thanks, Alexander On Thu, Jan 19, 2023 at 5:01 AM r...@apache.org wrote: > Hello Alexander, thanks your work for this. > It seems that all agrees wi