Re: [VOTE] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation
Thank you everyone. Closing the vote with 3 binding +1s and 2 non-binding +1s. Binding votes: - Matteo Merli - Lari Hotari - Hang Chen Non-Binding votes: - Neng Lu - Chris Bono Best regards, Apurva Telang On Tue, Jul 2, 2024 at 7:19 PM Hang Chen wrote: > +1 (binding) > > Best, > Hang > > Chris Bono 于2024年7月3日周三 00:29写道： > > > > +1 > > > > On 2024/06/28 20:51:39 Apurva Telang wrote: > > > Hello All, > > > > > > I would like to start the voting thread for PIP-337: SSL Factory > Plugin to > > > customize SSL Context and SSL Engine generation > > > > > > PIP link: https://github.com/apache/pulsar/pull/22016 > > > Discuss Thread: > > > https://lists.apache.org/thread/v4xh3fqy2t62xdk37b2ghvkrvvnqrx80 > > > > > > -- > > > Best regards, > > > Apurva Telang. > > > > -- Best regards, Apurva Telang.
[VOTE] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation
Hello All, I would like to start the voting thread for PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation PIP link: https://github.com/apache/pulsar/pull/22016 Discuss Thread: https://lists.apache.org/thread/v4xh3fqy2t62xdk37b2ghvkrvvnqrx80 -- Best regards, Apurva Telang.
Re: [DISCUSS] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation
Hello Matteo, Thanks for reviewing the proposal. I will start the voting thread today. Best regards, Apurva Telang On Thu, Jun 27, 2024 at 8:51 AM Matteo Merli wrote: > Hi Apurva, > > Thanks for applying the changes to the proposal. > > It looks good and given the time since it was already created, please feel > free to move to a vote at any time. > > > -- > Matteo Merli > > > > On Wed, Jun 26, 2024 at 8:35 PM Apurva Telang > wrote: > > > Hello All, > > > > I had submitted PIP-337 a few months ago regarding customizing the > > generation of SSL Context and SSL Engine. Based on past community > feedback, > > I have made the required modifications in the PIP. > > > > PIP link: https://github.com/apache/pulsar/pull/22016 > > > > Please can the community help review the PIP again and provide additional > > feedback. > > > > Best regards, > > Apurva Telang > > > > On Tue, Feb 6, 2024 at 11:58 AM Apurva Telang > > wrote: > > > > > > > > Hello All, > > > > > > I have submitted a PIP to add a SSL Factory Plugin to customize the > > > generation of SSL Context and SSL Engine. > > > > > > Motivation: > > > Apache Pulsar's TLS encryption configuration is not pluggable. It only > > > supports file-based certificates. This makes Pulsar difficult to adopt > > for > > > organizations that require loading TLS certificates by other > mechanisms. > > > > > > Goals: > > > > > >1. Provide a mechanism to plugin a custom SSL Factory that can > > >generate SSL Context and SSL Engine. > > >2. Simplify the Pulsar code base to universally use > > >javax.net.ssl.SSLContext and reduce the amount of code required to > > build > > >and configure the SSL context taking into consideration backwards > > >compatibility. > > > > > > PIP link: https://github.com/apache/pulsar/pull/22016 > > > > > > Please can the community review the PIP and provide your feedback. > > > > > > -- > > > Best regards, > > > Apurva Telang. > > > > > > > > > -- > > Best regards, > > Apurva Telang. > > > -- Best regards, Apurva Telang.
Re: [DISCUSS] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation
Hello All, I had submitted PIP-337 a few months ago regarding customizing the generation of SSL Context and SSL Engine. Based on past community feedback, I have made the required modifications in the PIP. PIP link: https://github.com/apache/pulsar/pull/22016 Please can the community help review the PIP again and provide additional feedback. Best regards, Apurva Telang On Tue, Feb 6, 2024 at 11:58 AM Apurva Telang wrote: > > Hello All, > > I have submitted a PIP to add a SSL Factory Plugin to customize the > generation of SSL Context and SSL Engine. > > Motivation: > Apache Pulsar's TLS encryption configuration is not pluggable. It only > supports file-based certificates. This makes Pulsar difficult to adopt for > organizations that require loading TLS certificates by other mechanisms. > > Goals: > >1. Provide a mechanism to plugin a custom SSL Factory that can >generate SSL Context and SSL Engine. >2. Simplify the Pulsar code base to universally use >javax.net.ssl.SSLContext and reduce the amount of code required to build >and configure the SSL context taking into consideration backwards >compatibility. > > PIP link: https://github.com/apache/pulsar/pull/22016 > > Please can the community review the PIP and provide your feedback. > > -- > Best regards, > Apurva Telang. > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-327 Support force topic loading for unrecoverable errors
+1 (non-binding) On Tue, Apr 16, 2024 at 10:11 AM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il Mar 16 Apr 2024, 19:08 Rajan Dhabalia ha > scritto: > > > Hi, > > > > I would like to start voting thread for PIP-327 which also addresses > issue > > # https://github.com/apache/pulsar/issues/21751 > > > > PIP design PR: > > https://github.com/apache/pulsar/pull/21752 > > <https://github.com/apache/pulsar/pull/21452> > > > > Thread: > > https://lists.apache.org/thread/w7w91xztdyy07otw0dh71nl2rn3yy45p > > > > Thanks, > > Rajan > > > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-342: Support OpenTelemetry metrics in Pulsar client
+1 (non-binding) On Thu, Mar 14, 2024 at 2:12 AM mattison chao wrote: > +1 (binding) > > Best, > Mattison > On Mar 14, 2024 at 15:55 +0800, Lari Hotari , wrote: > > +1 (binding) > > > > -Lari > > > > On Thu, 14 Mar 2024 at 03:45, Matteo Merli > wrote: > > > > > > PIP: https://github.com/apache/pulsar/pull/22178 > > > > > > WIP PR: https://github.com/apache/pulsar/pull/22179 > > > > > > > > > > > > > > > -- > > > Matteo Merli > > > > -- Best regards, Apurva Telang.
Re: (Apache committer criteria) [ANNOUNCE] New Committer: Asaf Mesika
Hello, Please find the discussion thread for PIP-337 on the Dev mailing list: https://lists.apache.org/thread/v4xh3fqy2t62xdk37b2ghvkrvvnqrx80 In the case of PIP-337, Lari was prompt in helping review the PIP and PR and providing valuable feedback. I acknowledged it via slack direct message to him. Personally, I have not gotten the chance to make changes due to other priorities at work. Hence, the delay in PIP-337's progress is my own fault as the author. My personal opinion is that joining community meetings and pinging in the "Dev" slack channel has been really helpful in receiving the attention from the community irrespective of the company you belong to. Best regards, Apurva Telang On Wed, Mar 6, 2024 at 10:13 PM Girish Sharma wrote: > On Thu, Mar 7, 2024 at 11:38 AM Yunze Xu wrote: > > > Regarding PIP-332 and PIP 310, similar to PIP-337, there is no > > discussion mail in the dev mail list. David left a comment [1] in > > > > There is for 310 - > https://lists.apache.org/thread/13ncst2nc311vxok1s75thl2gtnk7w1t > > > Regards > -- > Girish Sharma > -- Best regards, Apurva Telang.
[DISCUSS] PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine generation
Hello All, I have submitted a PIP to add a SSL Factory Plugin to customize the generation of SSL Context and SSL Engine. Motivation: Apache Pulsar's TLS encryption configuration is not pluggable. It only supports file-based certificates. This makes Pulsar difficult to adopt for organizations that require loading TLS certificates by other mechanisms. Goals: 1. Provide a mechanism to plugin a custom SSL Factory that can generate SSL Context and SSL Engine. 2. Simplify the Pulsar code base to universally use javax.net.ssl.SSLContext and reduce the amount of code required to build and configure the SSL context taking into consideration backwards compatibility. PIP link: https://github.com/apache/pulsar/pull/22016 Please can the community review the PIP and provide your feedback. -- Best regards, Apurva Telang.
Re: [VOTE] PIP-335: Oxia metadata support
+1 (non-binding) On Tue, Feb 6, 2024 at 7:29 AM Zixuan Liu wrote: > +1(non-binding) > > Thanks, > Zixuan > > Zike Yang 于2024年2月6日周二 19:29写道： > > > +1 > > > > Thanks, > > Zike Yang > > > > On Tue, Feb 6, 2024 at 6:58 PM Enrico Olivelli > > wrote: > > > > > > +1 (binding) > > > > > > Enrico > > > > > > Il giorno mar 6 feb 2024 alle ore 11:36 houxiaoyu > > > ha scritto: > > > > > > > > +1 nonbinding > > > > > > > > Thanks, > > > > Xiaoyu Hou > > > > > > > > 太上玄元道君 于2024年2月6日周二 15:59写道： > > > > > > > > > > +1 nonbinding > > > > > > > > > > Matteo Merli 于2024年2月6日 周二04:40写道： > > > > > > > > > > > https://github.com/apache/pulsar/pull/22009 > > > > > > > > > > > > - > > > > > > > > > > > > # PIP-335: Support Oxia metadata store plugin > > > > > > > > > > > > # Motivation > > > > > > > > > > > > Oxia is a scalable metadata store and coordination system that > can > > be used > > > > > > as the core infrastructure > > > > > > to build large scale distributed systems. > > > > > > > > > > > > Oxia was created with the primary goal of providing an > alternative > > Pulsar > > > > > > to replace ZooKeeper as the > > > > > > long term preferred metadata store, overcoming all the current > > limitations > > > > > > in terms of metadata > > > > > > access throughput and data set size. > > > > > > > > > > > > # Goals > > > > > > > > > > > > Add a Pulsar MetadataStore plugin that uses Oxia client SDK. > > > > > > > > > > > > Users will be able to start a Pulsar cluster using just Oxia, > > without any > > > > > > ZooKeeper involved. > > > > > > > > > > > > ## Not in Scope > > > > > > > > > > > > It's not in the scope of this proposal to change any default > > behavior or > > > > > > configuration of Pulsar. > > > > > > > > > > > > # Detailed Design > > > > > > > > > > > > ## Design & Implementation Details > > > > > > > > > > > > Oxia semantics and client SDK were already designed with Pulsar > and > > > > > > MetadataStore plugin API in mind, so > > > > > > there is not much integration work that needs to be done here. > > > > > > > > > > > > Just few notes: > > > > > > 1. Oxia client already provides support for transparent batching > > of read > > > > > > and write operations, > > > > > > so there will be no use of the batching logic in > > > > > > `AbstractBatchedMetadataStore` > > > > > > 2. Oxia does not treat keys as a walkable file-system like > > interface, with > > > > > > directories and files. Instead > > > > > > all the keys are independent. Though Oxia sorting of keys is > > aware of > > > > > > '/' and provides efficient key > > > > > > range scanning operations to identify the first level > children > > of a > > > > > > given key > > > > > > 3. Oxia, unlike ZooKeeper, doesn't require the parent path of a > > key to > > > > > > exist. eg: we can create `/a/b/c` key > > > > > > without `/a/b` and `/a` existing. > > > > > > In the Pulsar integration for Oxia we're forcing to create > all > > parent > > > > > > keys when they are not there. This > > > > > > is due to several places in BookKeeper access where it does > > not create > > > > > > the parent keys, though it will > > > > > > later make `getChildren()` operations on the parents. > > > > > > > > > > > > ## Other notes > > > > > > > > > > > > Unlike in the ZooKeeper implementation, the notification of > events > > is > > > > > > guaranteed in Oxia, because the Oxia > > > > > > client SDK will use the transaction offset after server > > reconnections and > > > > > > session restarted events. This > > > > > > will ensure that brokers cache will always be properly > > invalidated. We will > > > > > > then be able to remove the > > > > > > current 5minutes automatic cache refresh which is in place to > > prevent the > > > > > > ZooKeeper missed watch issue. > > > > > > > > > > > > # Links > > > > > > > > > > > > Oxia: https://github.com/streamnative/oxia > > > > > > Oxia Java Client SDK: https://github.com/streamnative/oxia-java > > > > > > > > > > > > > > > > > > -- > > > > > > Matteo Merli > > > > > > > > > > > > > > > -- Best regards, Apurva Telang.
Re: [DISCUSS] PIP-335: Oxia metadata support
+1 Best Regards, Apurva Telang On Wed, Jan 31, 2024 at 8:00 PM 太上玄元道君 wrote: > +1 > > Matteo Merli 于2024年2月1日 周四07:58写道： > > > https://github.com/apache/pulsar/pull/22009 > > > > === > > > > # PIP-335: Supporty Oxia metadata store plugin > > > > # Motivation > > > > Oxia is a scalable metadata store and coordination system that can be > used > > as the core infrastructure > > to build large scale distributed systems. > > > > Oxia was created with the primary goal of providing an alternative Pulsar > > to replace ZooKeeper as the > > long term preferred metadata store, overcoming all the current > limitations > > in terms of metadata > > access throughput and data set size. > > > > # Goals > > > > Add a Pulsar MetadataStore plugin that uses Oxia client SDK. > > > > Users will be able to start a Pulsar cluster using just Oxia, without any > > ZooKeeper involved. > > > > ## Not in Scope > > > > It's not in the scope of this proposal to change any default behavior or > > configuration of Pulsar. > > > > # Detailed Design > > > > ## Design & Implementation Details > > > > Oxia semantics and client SDK were already designed with Pulsar and > > MetadataStore plugin API in mind, so > > there is not much integration work that needs to be done here. > > > > Just a few notes: > > 1. Oxia client already provides support for transparent batching of read > > and write operations, > > so there will be no use of the batching logic in > > `AbstractBatchedMetadataStore` > > 2. Oxia does not treat keys as a walkable file-system like interface, > with > > directories and files. Instead > > all the keys are independent. Though Oxia sorting of keys is aware of > > '/' and provides efficient key > > range scanning operations to identify the first level children of a > > given key > > 3. Oxia, unlike ZooKeeper, doesn't require the parent path of a key to > > exist. eg: we can create `/a/b/c` key > > without `/a/b` and `/a` existing. > > In the Pulsar integration for Oxia we're forcing to create all parent > > keys when they are not there. This > > is due to several places in BookKeeper access where it does not > create > > the parent keys, though it will > > later make `getChildren()` operations on the parents. > > > > ## Other notes > > > > Unlike in the ZooKeeper implementation, the notification of events is > > guaranteed in Oxia, because the Oxia > > client SDK will use the transaction offset after server reconnections and > > session restarted events. This > > will ensure that brokers cache will always be properly invalidated. We > will > > then be able to remove the > > current 5minutes automatic cache refresh which is in place to prevent the > > ZooKeeper missed watch issue. > > > > # Links > > > > Oxia: https://github.com/streamnative/oxia > > Oxia Java Client SDK: https://github.com/streamnative/oxia-java > > > > > > -- > > Matteo Merli > > > > > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-326: Create a BOM to ease dependency management
+1 (non-binding) On Thu, Dec 21, 2023 at 4:30 PM Matteo Merli wrote: > +1 > > > -- > Matteo Merli > > > > On Thu, Dec 21, 2023 at 4:24 PM Nicolò Boschi > wrote: > > > +1 binding > > > > Nicolò Boschi > > > > > > Il giorno gio 21 dic 2023 alle 21:21 Lari Hotari ha > > scritto: > > > > > +1 (binding) > > > > > > -Lari > > > > > > > > > On Thu, 21 Dec 2023 at 22:10, Chris Bono wrote: > > > > > > > > I'm starting the vote for PIP-326, since it has been reviewed by > > > > several members with no objections. > > > > > > > > PIP link: https://github.com/apache/pulsar/pull/21747 > > > > > > > > Thanks, > > > > > > > > Chris > > > > > > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-322: Pulsar Rate Limiting Refactoring
+1 (non-binding) On Mon, Dec 11, 2023 at 9:10 AM Matteo Merli wrote: > +1 > > > -- > Matteo Merli > > > > On Mon, Dec 11, 2023 at 4:51 AM Lari Hotari wrote: > > > +1 (binding) > > > > -Lari > > > > On 2023/12/11 06:20:30 Lari Hotari wrote: > > > Dear Pulsar community, > > > > > > I am starting a vote thread for "PIP-322: Pulsar Rate Limiting > > Refactoring". > > > > > > PIP-322 document: > > > https://github.com/apache/pulsar/pull/21680 > > > > > > Draft changes for "PIP-322: Pulsar Rate Limiting Refactoring": > > > https://github.com/apache/pulsar/pull/21681 > > > > > > Discussion thread: > > > https://lists.apache.org/thread/xzrp2ypggp1oql437tvmkqgfw2b4ft33 > > > > > > Please review the PIP document and vote! > > > > > > Thanks, > > > > > > Lari > > > > > > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-320: OpenTelemetry Scaffolding
+1 (non-binding) On Mon, Dec 11, 2023 at 4:50 AM Lari Hotari wrote: > +1 (binding) > > -Lari > > On 2023/12/11 07:33:53 Asaf Mesika wrote: > > Hi, > > > > I'm starting the vote for PIP-320 (1st sub-PIP of PIP-264) > > > > Link: https://github.com/apache/pulsar/pull/21635 > > > > Reminder: > > This PIPs goal is to introduce OpenTelemetry into Apache Pulsar. When > this > > PIP is implemented, we will be able to start converting (not replacing) > > existing metrics into OpenTelemetry. > > > > > > Thank you! > > > > Asaf Mesika > > > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-313 Support force unsubscribe using consumer api
+1 (non-binding) On Sun, Dec 10, 2023 at 6:12 PM guo jiwei wrote: > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Thu, Dec 7, 2023 at 4:38 PM Rajan Dhabalia > wrote: > > > Hi, > > > > I would like to start voting thread for PIP-313 which also addresses > issue > > # https://github.com/apache/pulsar/issues/21451 > > > > PIP design PR: > > https://github.com/apache/pulsar/pull/21452 > > > > Thread: > > https://lists.apache.org/thread/hptx8z9mktn94gvqtt4547wzcfcgdsrv > > > > Thanks, > > Rajan > > > -- Best regards, Apurva Telang.
Re: [VOTE] PIP-315: Configurable max delay limit for delayed delivery
+1 (non-binding) On Tue, Nov 14, 2023 at 8:02 PM Kevin Lu wrote: > Hi All, > > This thread is to start a vote for PIP-315. > > PIP: https://github.com/apache/pulsar/pull/21490 > Discussion thread: > https://lists.apache.org/thread/285nm08842or324rxc2zy83wxgqxtcjp > > Regards, > Kevin > -- Best regards, Apurva Telang.
