Re: [DISCUSS] PIP-263: Just auto-create no-partitioned DLQ And Prevent auto-create a DLQ for a DLQ

2023-04-07 Thread Xiangying Meng
Hi Yubiao, Appreciate your effort in initiating this PIP. I believe these changes will address the existing issues and make DLQ and Retry Topic handling more efficient and straightforward. The goals you outlined are clear and, upon implementation, will improve the overall functionality of Pulsar.

Re: [DISCUSS] PIP-257: Add Open ID Connect Support to Server Components

2023-04-07 Thread Xiangying Meng
Thanks for initiating the proposal, Michael. I strongly support this addition, which will greatly enhance Pulsar's security and reliability. > I am new to this security component, but how do we support token revoke? Regarding Heesung Sohn's question about token revocation, I believe that we can ini

Re: [DISCUSS] Dropping the StreamingDispatcher

2023-04-07 Thread Xiangying Meng
Hi all, +1 for removing the StreamingDispatcher in Pulsar 3.0. Balancing maintainability, scalability, and usability is critical for an open-source project. In this case, the StreamingDispatcher seems to be neither widely adopted nor actively maintained, and its code quality and unstable tests hav

Re: [DISCUSS] Dropping the StreamingDispatcher

2023-04-07 Thread Cong Zhao
+1, I support removing it if the code isn't being used or maintained. Thanks, Cong Zhao On 2023/04/04 06:47:24 Enrico Olivelli wrote: > Hello, > It has been a long time that we have in the Pulsar code a new > experimental Dispatcher implementation named StreamingDispatcher. > > https://github.co

Re: [DISCUSS] Dropping the StreamingDispatcher

2023-04-07 Thread Yunze Xu
+1 for the reason that it was added when there is no PIP restriction for new APIs. The original author has left the community for some time and recently it seems that no one touched the code except for some necessary API changes. Thanks, Yunze On Thu, Apr 6, 2023 at 11:48 AM wrote: > > Totally a