Re: [DISCUSS] Migrate CLI parser from jcommander to picocli
Il Ven 23 Feb 2024, 04:34 Zixuan Liu ha scritto: > Thanks for the feedback! > > > Please take into account Pulsar Shell extensions > > This is a tricky issue, I noticed that it depends on jcommander here, Can you please share some pointers ? IIRC the shell extensions shouldn't need jcommander, it should be exposed in the public API Enrico and I > need to break this interface, and make it compatible with Pulsar Shell > implementation. > > I will create a draft PR to migrate the CLI parser from jcommander to > picocli, and then make a PIP to the Pulsar. > > Thanks, > Zixuan >
Re: [DISCUSS] PIP-331: WASM Function API
> What do you think about implementing a WASM function runtime directly? > It could be on par with the current Java function runtime. If we > define the API or SDK for WASM and Pulsar interaction, users could > simply upload their WASM files and process messages just like a Pulsar > function. +1 . Similar proposal has been discussed in the past: "Pluggable Pulsar Functions runtime to support new runtimes" https://lists.apache.org/thread/hcnpytky4bg4fd1xh1p4pbqbjxbv9rdg The thread contain useful requirements and suggestions for a pluggable runtime. -Lari On 2024/02/21 04:13:16 Zike Yang wrote: > Thanks for proposing this feature! > > I replied in the PR. > > Before reviewing this PIP, I thought it was an implementation of a > WASM function runtime. > IIUC, for this PIP, users need to first define a Java Pulsar function > and then construct the FunctionMap to interact with the wasm. Right? > > Just share my idea here: > What do you think about implementing a WASM function runtime directly? > It could be on par with the current Java function runtime. If we > define the API or SDK for WASM and Pulsar interaction, users could > simply upload their WASM files and process messages just like a Pulsar > function. > > BR, > Zike Yang > > On Sun, Feb 18, 2024 at 10:12 PM Asaf Mesika wrote: > > > > Hi ZiCheng, > > > > Brilliant suggestion! > > > > I replied in the PR section, which I couldn't understand. > > > > > > On Tue, Jan 30, 2024 at 1:18 PM dragon-zhang > > wrote: > > > > > Hi Pulsar Community, > > > > > > I want to add a new feature that supports run WASM bytecode to the > > > pulsar-functions module. > > > > > > Please see the PIP: https://github.com/apache/pulsar/pull/21992 > > > > > > Thanks, > > > ZiCheng Zhang >
Re: [DISCUSS] Migrate CLI parser from jcommander to picocli
> Can you please share some pointers ? Only `org.apache.pulsar.shell.ShellCommandsProvider#getJCommander` uses jcommander API. I need to use picocli instead of jcommander, or add a new method. Using picocli instead of jcommander will reduce some code, but it will break the signature of some methods. I need to carefully study how to do it. This thread is just a preliminary idea to replace jcommander, and I will write a PIP later. Thanks, Zixuan Enrico Olivelli 于2024年2月23日周五 22:59写道： > Il Ven 23 Feb 2024, 04:34 Zixuan Liu ha scritto: > > > Thanks for the feedback! > > > > > Please take into account Pulsar Shell extensions > > > > This is a tricky issue, I noticed that it depends on jcommander here, > > > > Can you please share some pointers ? IIRC the shell extensions shouldn't > need jcommander, it should be exposed in the public API > > Enrico > > and I > > need to break this interface, and make it compatible with Pulsar Shell > > implementation. > > > > I will create a draft PR to migrate the CLI parser from jcommander to > > picocli, and then make a PIP to the Pulsar. > > > > Thanks, > > Zixuan > > >
[VOTE] Release Apache Pulsar Helm Chart 3.3.0 based on 3.3.0-candidate-1
Hello Apache Pulsar Community, This is a call for the vote to release the Apache Pulsar Helm Chart version 3.3.0. Release notes for 3.3.0-candidate-1: https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-3.3.0-candidate-1 The release candidate is available at: https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/3.3.0-candidate-1/ pulsar-chart-3.3.0-source.tar.gz - is the "main source release". pulsar-3.3.0.tgz - is the binary Helm Chart release. Public keys are available at: https://www.apache.org/dist/pulsar/KEYS For convenience "index.yaml" has been uploaded (though excluded from voting), so you can also run the below commands. helm repo add --force-update apache-pulsar-dist-dev https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/3.3.0-candidate-1/ helm repo update helm install pulsar apache-pulsar-dist-dev/pulsar --version 3.3.0 --set affinity.anti_affinity=false pulsar-3.3.0.tgz.prov - is also uploaded for verifying Chart Integrity, though it is not strictly required for releasing the artifact based on ASF Guidelines. You can optionally verify this file using this helm plugin https://github.com/technosophos/helm-gpg, or by using helm --verify (https://helm.sh/docs/helm/helm_verify/). helm fetch --prov apache-pulsar-dist-dev/pulsar helm plugin install https://github.com/technosophos/helm-gpg helm gpg verify pulsar-3.3.0.tgz The vote will be open for at least 72 hours. Only votes from PMC members are binding, but members of the community are encouraged to test the release and vote with "(non-binding)". For license checks, the .rat-excludes files is included, so you can run the following to verify licenses (just update ): tar -xvf pulsar-chart-3.3.0-source.tar.gz cd pulsar-chart-3.3.0 java -jar /apache-rat-0.15/apache-rat-0.15.jar . -E .rat-excludes Please note that the version number excludes the `-candidate-X` string, so it's now simply 3.3.0. This will allow us to rename the artifact without modifying the artifact checksums when we actually release it. Thanks, Lari
