Re: [DISCUSS] Propose a Contributor Repository for Pulsar

Hi: I think this is a very good idea. In the native pulsar warehouse, there are some interfaces that have no default implementation classes, such as ConsumerInterceptor, ProducerInterceptor. Users must implement the interface themselves, which increases the cost of use. If there is a plug-in libra

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

Hello Wen Zhi, This project is a new repository similar to a connector, and it will not make any modifications to Pulsar itself. [0] Its code part is simply a plugin library, based on Pulsar's external interfaces, providing a rich set of implementations. It only retains a "curated list", which is

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

Hi, xiangying, First of all, thanks for driving the proposal. I have some questions. 1. Will this repository maintained by committers/pmc? If the answer is yes, there will be too many new modules introduced into pulsar and hard to maintain. If the answer is no, i think we have better not

Re: [VOTE] PIP-366: Support to specify different config for Configuration and Local Metadata Store

+1 (binding) Thanks for driving the proposal. Regards, Penghui On Sun, Jul 21, 2024 at 6:46 PM Kai Wang wrote: > Hi all, I want to start a vote on PIP-366: Support to specify different > config for Configuration and Local Metadata Store. > > You can find the proposal at https://github.com/apac

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

Thank you for your feedback, let's further clarify this matter. The original design of this proposal is a new contributor repository, and provides two ways to contribute. The first one: Contributors contribute through PR and accept code review, and can only be merged into the main branch after rev

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

Il giorno lun 22 lug 2024 alle ore 17:34 xiangying meng < xiangyingme...@gmail.com> ha scritto: > >thanks for your proposal, we need more and more energy in the project. > > Yes, it requires a lot of participation, but sometimes we also need a > start. > > >Also we allow only "committers" to commi

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

>thanks for your proposal, we need more and more energy in the project. Yes, it requires a lot of participation, but sometimes we also need a start. >Also we allow only "committers" to commit patches to the repositories that are >under the responsibility of the Apache Pulsar PMC, I don't know ho

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

Hello, thanks for your proposal, we need more and more energy in the project. I don't think that this is a good idea. The main reason is that as an ASF project we must guarantee the quality and especially the security of what we provide to the public. Such kinds of repositories tend to become fu

Re: [DISCUSS] Propose a Contributor Repository for Pulsar

We think this is a very good solution, Our XHS team(@liangyepianzhou @AuroraTwinkle @StevenLuMT @cai152 ) will submit a few to pulsar-java-contrib

[DISCUSS] Propose a Contributor Repository for Pulsar

Hello Pulsar Community, I hope this message finds you well. I'm reaching out to propose the establishment of a Pulsar Contributor Repository. This new initiative is designed to provide a dedicated space for experimental and community-driven features that complement our core offerings. This repos

Re: Ability to decrease partition count in pulsar

Hi Tao, We are planning to get a PIP out in this quarter. Regards On Mon, Jul 22, 2024 at 1:35 PM Tao Jiuming wrote: > Hi, > > How's the proposal going? > > On 2024/01/19 06:28:14 Girish Sharma wrote: > > Hello everyone, > > > > A a true cloud native platform, which supports scale up and scale d

Re: Ability to decrease partition count in pulsar

Hi, How's the proposal going? On 2024/01/19 06:28:14 Girish Sharma wrote: > Hello everyone, > > A a true cloud native platform, which supports scale up and scale down, I > feel like there is a need to be able to reduce partition count in pulsar to > truly achieve a scale down after events like s