On Thu, Aug 22, 2019 at 7:44 PM Deng Joey wrote:
> Hi, Pulsar Team,
>
> Could you please help to clarify the question as in the title for me?
>
> Here is the scene:
>
> 1. Assuming there are three partitions, and messages with a specified key
> was sent to partition 1 using hash algorithm.
> 2.
The release process looks good to me. +1
Masahiro, thank you for driving this.
- Sijie
On Thu, Aug 22, 2019 at 11:08 PM Masahiro Sakamoto
wrote:
> I have published experimentally the Node.js client version 0.0.1-rc.1
> to the npm repository according to the release procedure.
> https://www.npm
I have published experimentally the Node.js client version 0.0.1-rc.1
to the npm repository according to the release procedure.
https://www.npmjs.com/package/pulsar-client
Now we can install the Node.js client with the following command:
$ npm install pulsar-client
If there are no problems with
massakam opened a new pull request #49: Bump the master version to 0.1.0
URL: https://github.com/apache/pulsar-client-node/pull/49
I have already created `branch-0.0` to perform the first release, so I will
bump the master version to `0.1.0-rc.0`.
--
Hi, Pulsar Team,
Could you please help to clarify the question as in the title for me?
Here is the scene:
1. Assuming there are three partitions, and messages with a specified key was
sent to partition 1 using hash algorithm.
2. Scale the partition to six, then messages with the same key might
nkurihar merged pull request #48: Change initial version to 0.0.1
URL: https://github.com/apache/pulsar-client-node/pull/48
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
2019-08-21 11:25:55 UTC - Vladimir Shchur: @Vladimir Shchur has joined the
channel
2019-08-21 14:23:45 UTC - Kendall Magesh-Davis: Has there been any work on a
New Relic integration for pulsar?
2019-08-21 17:30:53 UTC - Matteo Merli: Not that I know of
2019-08-21 17:42:27 UTC - Ken
