> 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 <asaf.mes...@gmail.com> 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 <zhangzich...@apache.org> > > 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 >
