[DISCUSS] Pulsar Node.js Client Release 1.7.0

2022-09-06 Thread Yuto Furuta 
Hello everyone,

I'd like to propose to release Pulsar Node.js Client Release 1.7.0

Currently, we have 14 commits [0] and there are bug fixes, security fixes and 
performance improvements.
And there are open PRs [1].

If you have any important fixes or any questions, please reply to this email, 
we will evaluate whether to include it in 1.7.0

[0]
https://github.com/apache/pulsar-client-node/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2Fv1.7.0

[1]
https://github.com/apache/pulsar-client-node/pulls?q=is%3Aopen


Best Regards,

Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

Re: [VOTE] Pulsar Client Go Release 0.3.0 Candidate 1

2020-11-11 Thread Yuto Furuta 
+1 (non-binding)

- Verify checksum
- Run producer/consumer

Thank you.

Best Regards,
Yuto

--
Yuto Furuta
yfur...@yahoo-corp.jp


差出人: xiaolong ran 
送信日時: 2020年11月11日 19:53
宛先: dev@pulsar.apache.org 
件名: [VOTE] Pulsar Client Go Release 0.3.0 Candidate 1

Hi everyone,

Please review and vote on the release candidate #1 for the version 0.3.0, as 
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the first release candidate for Apache Pulsar Go client, version 0.3.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-go/milestone/4?closed=1 
<https://github.com/apache/pulsar-client-go/milestone/4?closed=1>

Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS 
<https://dist.apache.org/repos/dist/dev/pulsar/KEYS>

Please download these packages and review this release candidate:

- Review release notes
- Download the source package (verify shasum, and asc) and follow the
README.md to build and run the pulsar-client-go.

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

Source file:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.3.0-candidate-1/apache-pulsar-client-go-0.3.0-src.tar.gz
 
<https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.3.0-candidate-1/apache-pulsar-client-go-0.3.0-src.tar.gz>

The tag to be voted upon:
v0.3.0-candidate-1 
https://github.com/apache/pulsar-client-go/tree/v0.3.0-candidate-1 
<https://github.com/apache/pulsar-client-go/tree/v0.3.0-candidate-1>

SHA-512 checksums:
7ff0e25245bd0f4c26169e3a034e25c1d0e98810a423caff5eb97e4210e6cdf001757947538f7231738fead0bd02243782cff50453d8952c5df5db2ee0325b65
  apache-pulsar-client-go-0.3.0-src.tar.gz

Re: [PROPOSAL] PIP 74: Pulsar client memory limits

2020-12-17 Thread Yuto Furuta 
Matteo,

Thank you for your proposal.
I have two questions about it.

1. Why are producer queue size related settings deprecated/ignored?
It may be true that it is easy for users to set memory sizes than queue sizes.
However, there may be some users who have already set appropriate values.
So, I think these settings don't need to be deprecated/ignored.

2. Can producer queue size be changed dynamically?

Best regards,

Yuto
--
Yuto Furuta
yfur...@yahoo-corp.jp



差出人: Matteo Merli 
送信日時: 2020年12月16日 5:20
宛先: Dev 
件名: [PROPOSAL] PIP 74: Pulsar client memory limits

https://github.com/apache/pulsar/wiki/PIP-74%3A-Pulsar-client-memory-limits


## Motivation

Currently, there are multiple settings in producers and consumers that allow
to control the sizes of the message queues. These are ultimately used to
control the amount of memory used by the Pulsar client.

There are few issues with the current approach, that makes it complicated, in
non-trivial scenarios, to select an overall configuration that leads to a
certain use of memory:

 1. The settings are in terms of "number of messages", so one has to adjust
based on the expected message size.

 2. The settings are per producer/consumer. If an application has a large
(or simply unknown) number number of producers/consumer, it's very difficult
to select an appropriate value for queue sizes. The same is true for topics
that have many partitions.

## Goal

Allow to specify a maximum amount of memory on a given Pulsar client. The
producers and consumers will compete for the memory assigned.

The scope of this proposal is to track the "direct" memory used to hold
outgoing or incoming message payloads. The usage of JVM heap memory is outside
the scope, though normally it only represents a small fraction of the payloads
size.

The change will be done in multiple steps:
 1. Introduce new API to set the memory limit, keeping it disabled by default
  1.1 Implement memory limit for producers
 2. Implement memory limit for consumers
 3. (Once the feature is stable)
Enable memory limit by default, with 64 MB
 4. Deprecate producer queue size related settings
 5. Ignore producer queue size related settings

## Client API

```java

public class ClientBuilder {
  // 

  /**
   * Configure a limit on the amount of direct memory that will be
allocated by this client instance.
   * 
   * Setting this to 0 will disable the limit.
   *
   * @param memoryLimit
   *the limit
   * @param unit
   *the memory limit size unit
   * @return the client builder instance
   */
  ClientBuilder memoryLimit(long memoryLimit, SizeUnit unit);
}
```

For example:

```java
PulsarClient client = PulsarClient.builder()
.serviceUrl("pulsar://localhost:6650")
.memoryLimit(64, SizeUnit.MEGA_BYTES)
.create();
```

The same logic described here will be implemented first in Java and then
in the rest of supported client libraries.

## Implementation

The enforcement of the memory limit is done in a different way for producers as
compared to consumers, although both will share a common instance of a
`MemoryLimitController`, which is unique per each `PulsarClient` instance.

```java
interface MemoryLimitController {

// Non-blocking
boolean tryReserveMemory(long size);

// Blocks until memory is available
void reserveMemory(long size) throws InterruptedException;

void releaseMemory(long size);
}
```

The implementation of `MemoryLimitController` will be optimized to avoid
contention across multiple threads trying to reserve and release memory.

### Producer

If the memory limit is set, the producer will first try to acquire the
semaphore that is currently set based on the producer queue size, then it
will try to reserve the memory, either in blocking or non-blocking way,
depending on the producer configuration.

### Consumer

The logic for consumers is slightly more complicated because a client needs to
give permits to brokers to push messages. Right now, the count is done in terms
of messages and it cannot simply switch to "bytes" because a consumer will
need to consume from multiple topics and partitions.

Because of that, we need to invert the order, by using the memory limit
controller as a wait to interact with the flow control, reserving memory
after we have already received the messages.

The proposal is to keep the receiver queue size as a configuration, although
treat it more as the "max receiver queue size".

When a consumer is created, and memory limit is set, it will use these
parameters:
 * `maxReceiverQueueSize`: the values configured by the application
 * `currentReceiverQueue`: a dynamic limit that will be auto adjusted, starting
from an initial value (eg: 1) up to the max.

The goal is to step up the `currentReceiverQueue` if and only if:
 1. Doing it would improve throughput
 2. We have enough memory to do it

Re: [VOTE] Pulsar Release 2.6.3 Candidate 2

2021-01-18 Thread Yuto Furuta 
+1 (non binding)

 - Check checksums
 - Validate Produce/Consume
 - Validate Pulsar IO
 -- pulsar-io-cassandra-2.6.3.nar

Regards,
Yuto
--
Yuto Furuta
yfur...@yahoo-corp.jp

差出人: Hiroyuki Sakai 
送信日時: 2021年1月18日 16:03
宛先: Dev 
件名: Re: [VOTE] Pulsar Release 2.6.3 Candidate 2

+1 (binding)

 - check signatures/checksums
 - Validate Pub/Sub and Java Functions
 - Validate Stateful Functions

Regards,
Hiroyuki




From: PengHui Li 
Sent: Wednesday, January 13, 2021 20:42
To: Dev 
Subject: Re: [VOTE] Pulsar Release 2.6.3 Candidate 2

Sorry, forget to update the link address, you can copy the address directly
for validation.

Thanks,
Penghui

PengHui Li  于2021年1月13日周三 下午7:35写道：

> This is the second release candidate for Apache Pulsar, version 2.6.3.
>
> It fixes the following 
> issues:https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.6.3+is%3Aclosed
>
> *** Please download, test and vote on this release. This vote will stay open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary 
> files:https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.6.3-candidate-2/ 
> <https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.6.3-candidate-1/>
>
> SHA-1 checksums:
>
> e620672cb560b5947069e4e22be9b0e1bd08c327  apache-pulsar-2.6.3-src.tar.gz
> d1f3f9907ce54c002a7ec0a73dbe84be933cb4d1  apache-pulsar-2.6.3-bin.tar.gz
>
> Maven staging 
> repo:https://repository.apache.org/content/repositories/orgapachepulsar-1078/ 
> <https://repository.apache.org/content/repositories/orgapachepulsar-1077/>
>
> The tag to be voted upon:
> v2.6.3-candidate-2 
> (801ba85350f9a1c5dff9a7288c1f8fc9c22d8868)https://github.com/apache/pulsar/releases/tag/v2.6.3-candidate-2
>
> Pulsar's KEYS file containing PGP keys we use to sign the 
> release:https://dist.apache.org/repos/dist/release/pulsar/KEYS
>
> Please download the the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>

Re: [VOTE] Pulsar Client Go Release 0.5.0 Candidate 1

2021-05-11 Thread Yuto Furuta 
+1 (binding)

- verify checksum
- run produce/consume

Regards,
Yuto Furuta

差出人: Matteo Merli 
送信日時: 2021年5月11日 10:35
宛先: Dev 
件名: [VOTE] Pulsar Client Go Release 0.5.0 Candidate 1

Hi everyone,

Please review and vote on the release candidate #1 for the version
0.X.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the first release candidate for Apache Pulsar Go client, version 0.X.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-go/milestone/6?closed=1

Pulsar Client Go's KEYS file contains PGP keys we used to sign this release:
https://dist.apache.org/repos/dist/release/pulsar/KEYS

Please download these packages and review this release candidate:
- Review release notes
- Download the source package (verify shasum, and asc) and follow the
README.md to build and run the pulsar-client-go.

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Source file:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go/apache-pulsar-client-go-0.5.0-src.tar.gz

The tag to be voted upon:
v0.5.0-candidate-1
aa1c9a33ca04fe84d06e4a580c5654dfbcf303a4
https://github.com/apache/pulsar-client-go/releases/tag/v0.5.0-candidate-1

SHA-512 checksums:
b354597dbaa788362ac97e0e68ba741a56ab7270b51f5c0f80873f6bbfdb99624ccfd17c4531b9dbd4e6e421917ad168228a848d578355af032c0ed8a9a41f83
 apache-pulsar-client-go-0.5.0-src.tar.gz

Thanks,
Matteo

--
Matteo Merli

Re: [VOTE] Pulsar Node.js Client Release 1.4.0 Candidate 1

2021-07-28 Thread Yuto Furuta 
+1 (binding)

Checked:
* build
* install npm package
* run samples
** producer
** consumer, consumer_listener
** reader, reader_listener

Environment:
* CentOS 7.6.0
* node v14.17.2

Best Regards,
Yuto


差出人: Nozomi Kurihara 
送信日時: 2021年7月28日 19:28
宛先: dev@pulsar.apache.org 
件名: Re: [VOTE] Pulsar Node.js Client Release 1.4.0 Candidate 1

+1 (binding)

Checked:
* build
* license
* install npm package
* run small producer/consumer samples

Environment:
* CentOS 7.6.0
* node v16.5.0

Best Regards,
Nozomi

2021年7月28日(水) 9:52 Hiroyuki Sakai :

> This is the first release candidate for Apache Pulsar Node.js client,
> version 1.4.0.
>
> It fixes the following issues:
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Fmilestone%2F6%3Fclosed%3D1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C7a4a57d285cd43fcd52808d951b27f45%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637630651557701837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=HECz3Rdr5anMsY%2B2SyNbLMvLFPrfWiL0Q5nwNwUnSsY%3D&reserved=0
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), the npm package is provided
> for convenience.
>
> The tag to be voted upon:
> v1.4.0-rc.1
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Freleases%2Ftag%2Fv1.4.0-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C7a4a57d285cd43fcd52808d951b27f45%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637630651557701837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ODq%2Fl6lChVB5F6lRHtS3cHzbL5ukc1YKtVIj20yZQiw%3D&reserved=0
>
> The npm package:
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2Fpulsar-client%2Fv%2F1.4.0-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C7a4a57d285cd43fcd52808d951b27f45%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637630651557701837%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=onKEl5aGTsQWi8%2B83PryCjAWILq2F9cep7pQqfKpT8Y%3D&reserved=0
>
> Please download the source files, and follow the README to build
> and run the Pulsar Node.js client.
>
> ==
> Hiroyuki Sakai
> Yahoo Japan Corp.
> E-mail: hsa...@yahoo-corp.jp
>

Re: [VOTE] Pulsar Node.js Client Release 1.3.1 Candidate 1

2021-09-15 Thread Yuto Furuta 
+1 (binding)

* build the source code
* check the license headers
* install the package
* run producer/consumer/reader/consumer_listener

Regards,

Yuto Furuta

差出人: Hiroyuki Sakai 
送信日時: 2021年9月13日 16:20
宛先: dev@pulsar.apache.org 
件名: [VOTE] Pulsar Node.js Client Release 1.3.1 Candidate 1

This is the first release candidate for Apache Pulsar Node.js client, version 
1.3.1.

It fixes the following issues:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Fmilestone%2F8%3Fclosed%3D1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C93610160566e45513f8408d97686fb20%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637671144421395872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=NNns4kyojB516nJLRQmofNwSU5T%2Fgef7LAc96ZMHago%3D&reserved=0

*** Please download, test and vote on this release. This vote will stay open 
for at least 72 hours ***

Note that we are voting upon the source (tag), the npm package is provided for 
convenience.

The tag to be voted upon:
v1.3.1-rc.1
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Freleases%2Ftag%2Fv1.3.1-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C93610160566e45513f8408d97686fb20%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637671144421395872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YJtli0%2BRvnGowJpMokk0fY7oN7ubjnEJpYu4BfKG3do%3D&reserved=0

The npm package:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2Fpulsar-client%2Fv%2F1.3.1-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C93610160566e45513f8408d97686fb20%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637671144421395872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=N9if4cQJIVx3hr57Pl7y1qRZFlgvAuzDyLnH7ZKNQr0%3D&reserved=0

Please download the source files, and follow the README to build and run the 
Pulsar Node.js client.

Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

2021-10-10 Thread Yuto Furuta 
+1 (binding)

* build the source code
* check the license headers
* install the package
* run producer/consumer/reader/consumer_listener

Regards,

Yuto Furuta

差出人: Masahiro Sakamoto 
送信日時: 2021年10月8日 19:20
宛先: dev@pulsar.apache.org 
件名: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1

This is the first release candidate for Apache Pulsar Node.js client, version 
1.3.2.

It fixes the following issues:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Fmilestone%2F9%3Fclosed%3D1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7Cedfdf11d54d84bb0340508d98a45465a%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637692852396552850%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oSQKwbP8SPFlYwpKKjDUgWLRpv9hA9xjuZThBRxDrjc%3D&reserved=0

*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***

Note that we are voting upon the source (tag), the npm package is provided
for convenience.

The tag to be voted upon:
v1.3.2-rc.1
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Freleases%2Ftag%2Fv1.3.2-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7Cedfdf11d54d84bb0340508d98a45465a%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637692852396552850%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=u7xe5rFGI%2FdoJUD%2Fshz0zbiXRDhIYOBsyu8Thk%2FHh70%3D&reserved=0

The npm package:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2Fpulsar-client%2Fv%2F1.3.2-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7Cedfdf11d54d84bb0340508d98a45465a%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637692852396552850%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mPiBT8ItAKXxufnJpnwHd1FfiMk2XMEPGlJauolOA90%3D&reserved=0

Please download the source files, and follow the README to build
and run the Pulsar Node.js client.

Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp

Re: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

2021-10-10 Thread Yuto Furuta 
+1 (binding)

* build the source code
* check the license headers
* install the package
* run producer/consumer/reader/consumer_listener/reader_listener

Regards,

Yuto Furuta


差出人: Nozomi Kurihara 
送信日時: 2021年10月11日 12:21
宛先: dev@pulsar.apache.org 
件名: Re: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1

+1 (binding)

* check the license headers
* install the npm package
* run producer/consumer

Thanks,
Nozomi

2021年10月8日(金) 19:23 Masahiro Sakamoto :

> This is the first release candidate for Apache Pulsar Node.js client,
> version 1.4.1.
>
> It fixes the following issues:
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Fmilestone%2F10%3Fclosed%3D1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C1eee5e50593c40657c9b08d98c663979%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637695192936841760%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=H0OYTBAj9jfSP0S1waN4GJ9qqQTuoAcU86w%2BAQNMtEQ%3D&reserved=0
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), the npm package is provided
> for convenience.
>
> The tag to be voted upon:
> v1.4.1-rc.1
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar-client-node%2Freleases%2Ftag%2Fv1.4.1-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C1eee5e50593c40657c9b08d98c663979%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637695192936841760%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hMbJkbl1G4XOCKleQfmlMM%2BppBraQiwp7EExwlKSDcE%3D&reserved=0
>
> The npm package:
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2Fpulsar-client%2Fv%2F1.4.1-rc.1&data=04%7C01%7Cyfuruta%40yahoo-corp.jp%7C1eee5e50593c40657c9b08d98c663979%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637695192936841760%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UZHTty4hnRNy2Z7g7bqquu8BUGfygSwYEPD7FUtyVaM%3D&reserved=0
>
> Please download the source files, and follow the README to build
> and run the Pulsar Node.js client.
>
> Masahiro Sakamoto
> Yahoo Japan Corp.
> E-mail: massa...@yahoo-corp.jp
>

[VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 1

2022-10-03 Thread Yuto Furuta 
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.7.0, as 
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the first release candidate for Apache Pulsar Node.js client, version 
1.7.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/issues?q=label%3Arelease%2Fv1.7.0+is%3Aclosed

Please download the source files and review this release candidate:
- Review release notes
- Download the source package (verify shasum and asc) and follow the README.md 
to build and run the Pulsar Node.js client.

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

Source files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.7.0-candidate-1/

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

SHA-512 checksum:
7012560ef62744d5211d858e3784276a694f83437bb929c2fcec9f249706d7bea0d9b757f464298a25725b702340c760a2c9ff488814c6c11d8a10362b2ffe0a
  pulsar-client-node-1.7.0.tar.gz

The tag to be voted upon:
v1.7.0-rc.1
https://github.com/apache/pulsar-client-node/releases/tag/v1.7.0-rc.1

[https://opengraph.githubassets.com/68c696c8446e431f7e494bc22ee38c6e6e23d3a20f31426e1d216819bdcb9550/apache/pulsar-client-node]<https://github.com/apache/pulsar-client-node/releases/tag/v1.7.0-rc.1>
Release v1.7.0-rc.1 · 
apache/pulsar-client-node<https://github.com/apache/pulsar-client-node/releases/tag/v1.7.0-rc.1>
Release v1.7.0-rc.1
github.com




Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

[VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 1

2022-10-04 Thread Yuto Furuta 
Hi everyone,

Please review and vote on the release candidate #1 for the version 1.7.0, as 
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the first release candidate for Apache Pulsar Node.js client, version 
1.7.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/issues?q=label%3Arelease%2Fv1.7.0+is%3Aclosed

Please download the source files and review this release candidate:
- Review release notes
- Download the source package (verify shasum and asc) and follow the README.md 
to build and run the Pulsar Node.js client.

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

Source files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.7.0-candidate-1/

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

SHA-512 checksum:
7012560ef62744d5211d858e3784276a694f83437bb929c2fcec9f249706d7bea0d9b757f464298a25725b702340c760a2c9ff488814c6c11d8a10362b2ffe0a
  pulsar-client-node-1.7.0.tar.gz

The tag to be voted upon:
v1.7.0-rc.1
https://github.com/apache/pulsar-client-node/releases/tag/v1.7.0-rc.1


Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

Re: [VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 1

2022-10-05 Thread Yuto Furuta 
Thanks for your help.
Due to an error in the signature of candidate #1, close this VOTE and prepare 
candidate #2.

Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

差出人: 古田 悠人
送信日時: 2022年10月4日 16:45
宛先: dev@pulsar.apache.org 
件名: [VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 1

Hi everyone,

Please review and vote on the release candidate #1 for the version 1.7.0, as 
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the first release candidate for Apache Pulsar Node.js client, version 
1.7.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/issues?q=label%3Arelease%2Fv1.7.0+is%3Aclosed

Please download the source files and review this release candidate:
- Review release notes
- Download the source package (verify shasum and asc) and follow the README.md 
to build and run the Pulsar Node.js client.

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

Source files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.7.0-candidate-1/

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

SHA-512 checksum:
7012560ef62744d5211d858e3784276a694f83437bb929c2fcec9f249706d7bea0d9b757f464298a25725b702340c760a2c9ff488814c6c11d8a10362b2ffe0a
  pulsar-client-node-1.7.0.tar.gz

The tag to be voted upon:
v1.7.0-rc.1
https://github.com/apache/pulsar-client-node/releases/tag/v1.7.0-rc.1


Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

[VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 2

2022-10-05 Thread Yuto Furuta 
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.7.0, as 
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

This is the second release candidate for Apache Pulsar Node.js client, version 
1.7.0.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/issues?q=label%3Arelease%2Fv1.7.0+is%3Aclosed

Please download the source files and review this release candidate:
- Review release notes
- Download the source package (verify shasum and asc) and follow the README.md 
to build and run the Pulsar Node.js client.

The vote will be open for at least 72 hours. It is adopted by majority 
approval, with at least 3 PMC affirmative votes.

Source files:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.7.0-candidate-2/

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://dist.apache.org/repos/dist/dev/pulsar/KEYS

SHA-512 checksum:
7012560ef62744d5211d858e3784276a694f83437bb929c2fcec9f249706d7bea0d9b757f464298a25725b702340c760a2c9ff488814c6c11d8a10362b2ffe0a
  pulsar-client-node-1.7.0.tar.gz

The tag to be voted upon:
v1.7.0-rc.2
https://github.com/apache/pulsar-client-node/releases/tag/v1.7.0-rc.2

Re: [VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 2

2022-10-18 Thread Yuto Furuta 
Thanks for your help.
Close this vote with 3 binding +1s.

Sincerely,
Yuto Furuta


Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

差出人: Masahiro Sakamoto 
送信日時: 2022年10月14日 18:03
宛先: dev@pulsar.apache.org 
件名: RE: [VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 2

Thanks Yuri. I agree with you and will change my vote to +1.

+1 (binding)

* Checked the license headers
* Verified the checksum and signature
* Built the source and ran producer/consumer

Regards,

Masahiro Sakamoto
Yahoo Japan Corp.
E-mail: massa...@yahoo-corp.jp

-Original Message-
From: Yuri Mizushima 
Sent: Friday, October 14, 2022 12:56 PM
To: dev@pulsar.apache.org
Subject: Re: [VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 2

Hi Masahiro,

It seems the C++ client causes the AlreadyClosed issue.
https://github.com/apache/pulsar-client-cpp/issues/51

I think this issue doesn't block releasing new Node.js client.
What do you think?

Thanks,
--
Yuri Mizushima
yumiz...@yahoo-corp.jp


"Masahiro Sakamoto"  wrote:

-1 (binding)

I almost always get "Failed to send message: AlreadyClosed" errors when running 
the following code:
##
$ cat producer.js
const Pulsar = require('./index.js');

(async () => {
  const client = new Pulsar.Client({
serviceUrl: 'pulsar://localhost:6650',
  });

  const producer = await client.createProducer({
topic: 'persistent://public/default/t1',
batchingEnabled: false,
  });

  for (let i = 0; i < 10; i += 1) {
const msg = `my-message-${i}`;
producer.send({
  data: Buffer.from(msg),
});
console.log(`Sent message: ${msg}`);
  }
  await producer.flush();

  await producer.close();
  await client.close();
})();
$ node producer.js
Sent message: my-message-0
Sent message: my-message-1
Sent message: my-message-2
Sent message: my-message-3
Sent message: my-message-4
Sent message: my-message-5
Sent message: my-message-6
Sent message: my-message-7
Sent message: my-message-8
Sent message: my-message-9
(node:18572) UnhandledPromiseRejectionWarning: Error: Failed to send message: 
AlreadyClosed
(Use `node --trace-warnings ...` to show where the warning was created)
(node:18572) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 
This error originated either by throwing inside of an async function without a 
catch block, or by rejecting a promise which was not handled with .catch(). To 
terminate the node process on unhandled promise rejection, use the CLI flag 
`--unhandled-rejections=strict` (see 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnodejs.org%2Fapi%2Fcli.html%23cli_unhandled_rejections_mode&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Cb6c618f44ab34f4a292708daadc31495%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638013350617082428%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Msq14MYGAwhzs7QbZMivs3HBABXfMCNblG0pPXufK4I%3D&reserved=0).
 (rejection id: 1)
(node:18572) [DEP0018] DeprecationWarning: Unhandled promise rejections are 
deprecated. In the future, promise rejections that are not handled will 
terminate the Node.js process with a non-zero exit code.
(node:18572) UnhandledPromiseRejectionWarning: Error: Failed to send message: 
AlreadyClosed
(node:18572) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 
This error originated either by throwing inside of an async function without a 
catch block, or by rejecting a promise which was not handled with .catch(). To 
terminate the node process on unhandled promise rejection, use the CLI flag 
`--unhandled-rejections=strict` (see 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnodejs.org%2Fapi%2Fcli.html%23cli_unhandled_rejections_mode&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Cb6c618f44ab34f4a292708daadc31495%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638013350617082428%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Msq14MYGAwhzs7QbZMivs3HBABXfMCNblG0pPXufK4I%3D&reserved=0).
 (rejection id: 2)
(node:18572) UnhandledPromiseRejectionWarning: Error: Failed to send message: 
AlreadyClosed
(node:18572) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 
This error originated either by throwing inside of an async function without a 
catch block, or by rejecting a promise which was not handled with .catch(). To 
terminate the node process on unhandled promise rejection, use the CLI flag 
`--unhandled-rejections=strict` (see 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnodejs.org%2Fapi%2Fcli.html%23cli_unhandled_rejections_mode&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Cb6c618f44ab34f4a292708daadc31495%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638013350617082428%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV

[ANNOUNCE] Apache Pulsar Node.js client 1.7.0 released

2022-10-19 Thread Yuto Furuta 
The Apache Pulsar team is proud to announce Apache Pulsar Node.js client 
version 1.7.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.

For Pulsar Node.js client release details and downloads, visit:
https://www.npmjs.com/package/pulsar-client

Release Notes are at:
https://github.com/apache/pulsar-client-node/releases

We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team

[DISCUSS] Should we bump up Node.js Client for C++ Client's upgrade

2023-01-09 Thread Yuto Furuta 
Hi all,

Currently Node.js Client is tied to specified version of C++ Client due to the 
following PR:
https://github.com/apache/pulsar-client-node/pull/235

Should we bump up the version of Node.js Client even when there is no update 
except for C++ Client’s upgrade(at least for critical bug fixies)?


Best Regards,
Yuto

Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp

Re: [DISCUSS] Should we bump up Node.js Client for C++ Client's upgrade

2023-01-16 Thread Yuto Furuta 
Thank you for your comments.

I proposed the versioning rule of Node.js Client.
Please review it if you have time.
https://github.com/apache/pulsar-client-node/pull/287

Thanks,
Yuto


Yuto Furuta
Yahoo Japan Corp.
E-mail: yfur...@yahoo-corp.jp


差出人: Yunze Xu 
送信日時: 2023年1月10日 16:19
宛先: dev@pulsar.apache.org 
件名: Re: [DISCUSS] Should we bump up Node.js Client for C++ Client's upgrade

My answer is yes. Some bug fixes might be included in a newer C++
client. But I think we don't need to start a release in a hurry once a
newer C++ client is released.

Thanks,
Yunze

On Tue, Jan 10, 2023 at 3:03 PM Zike Yang  wrote:
>
> Hi, Yuto Furuta,
>
> Currently, the latest Nodejs client 1.8.0 is already tied to the
> latest C++ client 3.1.0. If there is a new C++ client version release,
> I think it's also better to release a new Nodejs client version that
> is tied to the latest C++ client version even though there are no new
> commits in the Nodejs client. In this case, we can make sure the
> latest Nodejs client always gets the latest updates or bug fixes of
> the C++ client.
>
> BR,
> Zike Yang
>
> On Tue, Jan 10, 2023 at 1:57 PM Yuto Furuta  wrote:
> >
> > Hi all,
> >
> > Currently Node.js Client is tied to specified version of C++ Client due to 
> > the following PR:
> > https://github.com/apache/pulsar-client-node/pull/235
> >
> > Should we bump up the version of Node.js Client even when there is no 
> > update except for C++ Client’s upgrade(at least for critical bug fixies)?
> >
> >
> > Best Regards,
> > Yuto
> >
> > Yuto Furuta
> > Yahoo Japan Corp.
> > E-mail: yfur...@yahoo-corp.jp

Re: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 4

2023-04-17 Thread Yuto Furuta 
+1 (non-binding)

* verify checksum and signatures
* build the source
* run producer, consumer, consumer_listener (source/npm)

Regards,

Yuto Furuta

差出人: Baodi Shi 
送信日時: 2023年4月14日 18:12
宛先: dev@pulsar.apache.org 
件名: [VOTE] Pulsar Node.js Client Release 1.8.2 Candidate 4

Hi everyone,

This is the first release candidate for Apache Pulsar Node.js client,
version 1.8.2.

It fixes the following issues:
https://github.com/apache/pulsar-client-node/pulls?q=is%3Apr+label%3Arelease%2Fv1.8.2+is%3Aclosed

Please download the source files and review this release candidate:
- Download the source package, verify shasum and asc
- Follow the README.md to build and run the Pulsar Node.js client.

The release candidate package has been published to the npm registry:

https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.npmjs.com%2Fpackage%2Fpulsar-client%2Fv%2F1.8.2-rc.4&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Ca14b3d60007641e8d58f08db3cc86e9d%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638170603764950233%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bKG26QUm5gWo1CuJc3AHOcHgMb1KWPkjiAkYeM1VHWA%3D&reserved=0<https://www.npmjs.com/package/pulsar-client/v/1.8.2-rc.4>

You can install it by `npm i pulsar-client@1.8.2-rc.4
--pulsar_binary_host_mirror=
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-client-node%2F%2560&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Ca14b3d60007641e8d58f08db3cc86e9d%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638170603764950233%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=m%2Fhe8LW3RSogO%2FnPl%2FAzik217g%2FPAH0cBneu%2FXFTuxw%3D&reserved=0<https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/%60>
and verify the package.

You can refer to this repository to verify tls related features:

https://github.com/shibd/pulsar-client-tls-test

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Source files:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-client-node%2Fpulsar-client-node-1.8.2-rc.4%2F&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Ca14b3d60007641e8d58f08db3cc86e9d%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638170603764950233%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TUQ7OMPmRmeXJWD%2Fty53ForqI9Y6JMUF6VogHew7mHo%3D&reserved=0<https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node/pulsar-client-node-1.8.2-rc.4/>

Pulsar's KEYS file containing PGP keys we use to sign the release:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownloads.apache.org%2Fpulsar%2FKEYS&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Ca14b3d60007641e8d58f08db3cc86e9d%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638170603764950233%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=K8gGLEtq%2BLYSYC6kYdseBEMmGzJgSdEzNBUmx5C%2BM%2Fg%3D&reserved=0<https://downloads.apache.org/pulsar/KEYS>

SHA-512 checksum:
2bcfd0155abe653924d974839307c2bc980c982252e83c6442b1a368262057d4401eef186ec2b962ec973deedd81a899469ecee6afc61bd5718fa548c7c510ad
 ./apache-pulsar-client-node-1.8.2.tar.gz

The tag to be voted upon:
v1.8.2-rc.4(7b3de1f)
https://github.com/apache/pulsar-client-node/releases/tag/v1.8.2-rc.4

Please review and vote on the release candidate #1 for the version
1.8.2, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


Thanks,
Baodi Shi

Re: [VOTE] Pulsar Client C++ Release 3.2.0 Candidate 3

2023-05-10 Thread Yuto Furuta 
+1(non-binding)

Verified:
  - Verified checksum and signatures
  - Build from source code on MacOS
  - Verified produce and consume

差出人: Baodi Shi 
送信日時: 2023年5月9日 10:47
宛先: dev@pulsar.apache.org 
件名: Re: [VOTE] Pulsar Client C++ Release 3.2.0 Candidate 3

+1(non-binding)

Verify:

   - SHA512 for source code.
   - Compilation on MacOS M1(13.2.1)
   - Run SampleProducer and SampleConsumer


Thanks,
Baodi Shi


On May 7, 2023 at 10:53:32, Yunze Xu  wrote:

> This is the third release candidate for Apache Pulsar Client C++, version
> 3.2.0.
>
> It fixes the following issues:
> https://github.com/apache/pulsar-client-cpp/milestone/3?closed=1
>
> *** Please download, test and vote on this release. This vote will stay
> open
> for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided for
> convenience.
>
> Source and binary files:
>
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-client-cpp%2Fpulsar-client-cpp-3.2.0-candidate-3%2F&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Cf2c3576a396a4f9efeae08db502f6a42%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638191936796372639%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2YOV4X7YLdYBBMl%2F9XbaaPhVZyapDDjAd1oxreXTFbc%3D&reserved=0
>
> SHA-512 checksums:
>
> 4422088c9d16e91caf90f6991a0ca0e3a5f50328c3503acf90641b100fe72b1fef7bec782cc693b947d53841d61470a56175a29d27fb609b937a6f79486b
> apache-pulsar-client-cpp-3.2.0.tar.gz
>
> The tag to be voted upon:
> v3.2.0-candidate-3 (1dad87bb3b804d2aa8542ac48e4c35228ac2f1bf)
> https://github.com/apache/pulsar-client-cpp/releases/tag/v3.2.0-candidate-3
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownloads.apache.org%2Fpulsar%2FKEYS&data=05%7C01%7Cyfuruta%40yahoo-corp.jp%7Cf2c3576a396a4f9efeae08db502f6a42%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C638191936796372639%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JhG7VyPM5r52DyD%2F2srJQXBeLChi5K2uXkOxE2xfaUg%3D&reserved=0
>
> Please download the source package, and follow the README to compile and
> test.
>