Thank you, Dave.
I also voted.
Regards,
Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp
-Original Message-
From: Dave Fisher
Sent: Friday, October 15, 2021 11:38 PM
To: dev@pulsar.apache.org
Subject: Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1
Hi Masah
+1 (binding)
* Checked the license headers
* Verified the checksum and signature
* Installed the npm package
* Built the source and run producer/consumer
Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp
-Original Message-
From: Hiroyuki Sakai
Sent: Thursday, October 1
+1 (binding)
* Checked the license headers
* Verified the checksum and signature
* Installed the npm package
* Built the source and run producer/consumer
Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp
-Original Message-
From: Hiroyuki Sakai
Sent: Thursday, October 1
We have evaluated pulsar in the last few months and would like to use it
with flink.
Found that memory leak with Java-11 flink connector.
https://nightlies.apache.org/flink/flink-docs-master/zh/release-notes/flink-1.14/
Now in a dilemma whether pulsar is matured to use in streaming space as
with K
Hi,
I have opened a PR that applies the Maven Modernizer plugin on the
*pulsar-proxy* module to enforce we move away from legacy APIs and fix the
violation.
Github PR URL: https://github.com/apache/pulsar/pull/12326
Please consider reviewing it. :D
Thanks,
Amar Prakash Pandey
Github: @amarlearn
