Re: [RESULT][VOTE] Accept pulsar-admin-go as part of the Apache Pulsar project

2023-08-10 Thread Enrico Olivelli
+1 (binding) (Late on the train) Enrico Il Gio 10 Ago 2023, 05:39 tison ha scritto: > Hi, > > The vote for "Accept pulsar-admin-go as part of the Apache Pulsar project" > has PASSED and closed now. > > The result is as follows: > > 4 +1 binding Votes > - Yunze Xu > - tison > - mattisonchao > -

Re: [VOTE] Pulsar Release 3.1.0 Candidate 1

2023-08-10 Thread guo jiwei
+1 (binding) - Checked the signature - Build from source (maven 3.8.6, JDK 17.0.3) - Start standalone - Publish and Consume - Verified Cassandra connector - Verified stateful function Regards Jiwei Guo (Tboy) On Wed, Aug 9, 2023 at 9:50 AM guo jiwei wrote: > This is the first release candida

Re: [DISCUSS] PIP-285: Add pulsar_subscription_back_log_duration metric

2023-08-10 Thread Qiang Huang
+1 houxiaoyu 于2023年7月24日周一 20:00写道: > +1 > > Thanks > Xiaoyu Hou > > 丛搏 于2023年7月24日周一 19:58写道: > > > Hi, Pulsar Community > > > > I opened a new PIP design PR. > > > > https://github.com/apache/pulsar/pull/20859 > > > > Thanks, > > Bo > > > -- BR, Qiang Huang

Re: [DISCUSS] PIP 289: Secure Pulsar Connector Configuration

2023-08-10 Thread Michael Marshall
> * Should we deprecate the old way of injecting secrets? It wasn't > widely used, and it does not work in all cases. (See the PIP for the > old mechanism.) I propose we leave the old way of injecting secrets in place. This will prevent unnecessary breaking changes. I'll add some new docs to make

[VOTE] PIP 289: Secure Pulsar Connector Configuration

2023-08-10 Thread Michael Marshall
Hi Pulsar Community, This is the vote thread for PIP 289: https://github.com/apache/pulsar/pull/20903. This PIP will help improve Pulsar Connector Security by giving users the ability to remove all plaintext secrets from their configurations. Thanks, Michael

Re: [VOTE] PIP 289: Secure Pulsar Connector Configuration

2023-08-10 Thread Michael Marshall
+1 (binding) - Michael On Thu, Aug 10, 2023 at 11:43 AM Michael Marshall wrote: > > Hi Pulsar Community, > > This is the vote thread for PIP 289: > https://github.com/apache/pulsar/pull/20903. > > This PIP will help improve Pulsar Connector Security by giving users > the ability to remove all pl

Re: [DISCUSS] PIP-281: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager

2023-08-10 Thread Heesung Sohn
On Tue, Aug 8, 2023 at 9:56 PM Michael Marshall wrote: > Thanks for your proposal, Heesung. Sorry for my late response. Just > want to make a few points to hopefully improve the implementation. > Overall, I think this feature is absolutely the right direction for > Pulsar and will be a great impr

Re: [VOTE] Pulsar Release 2.10.5 Candidate 1

2023-08-10 Thread tison
Sorry. I didn't run the check binaries commands under the root path. Now I found that the source releases contains - ./pulsar-client-cpp/python/dist/pulsar_client-2.10.5-cp38-cp38-linux_x86_64.whl ./pulsar-client-cpp/python/CMakeFiles/_pulsar.dir/src/client.cc.o ./pulsar-client-cpp/python/CMakeFil

Re: [VOTE] Pulsar Release 2.10.5 Candidate 1

2023-08-10 Thread tison
The command is - $ find . -type f | perl -lne 'print if -B' Best, tison. tison 于2023年8月11日周五 11:47写道: > Sorry. I didn't run the check binaries commands under the root path. Now I > found that the source releases contains - > > > ./pulsar-client-cpp/python/dist/pulsar_client-2.10.5-cp38-cp38-l

Re: [VOTE] Pulsar Release 2.10.5 Candidate 1

2023-08-10 Thread Xiangying Meng
Hi tison, Although we have currently released the CPP and Python clients in separate repositories, the content of the Python and CPP clients has not been removed from the branch-2.10. The extra content you see consists of compiled files related to the CPP and Python clients. These files do not affe

Re: [VOTE] Pulsar Release 2.10.5 Candidate 1

2023-08-10 Thread tison
> You can safely ignore them Yeah. Here is no technical issue, but - 1. Source releases should not contain unexpected binaries; 2. Too large source tarball affects user experience. I casted my +1 vote so I also made mistakes, and since we announced 2.10.5 we cannot revoke it or edit it. I post t