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 mana
+1 (binding)
It's very useful and a similar approach is widely used in our
production environment.
Thanks,
Haiting
On Tue, Oct 18, 2022 at 10:47 PM Michael Marshall wrote:
>
> +1 (binding)
>
> Great proposal, Christophe.
>
> Thanks,
> Michael
>
> On Tue, Oct 18, 2022 at 8:11 AM Alexander Preu
Congratulations, Haiting!
Best,
Jun
From: Yunze Xu
Sent: Wednesday, October 19, 2022 23:23
To: dev@pulsar.apache.org
Subject: Re: [ANNOUNCE] Haiting Jiang as a new PMC member in Apache Pulsar
Congrats!
Thanks,
Yunze
On Tue, Oct 18, 2022 at 4:06 PM Hang Chen
Oops.
I forgot to mention another important item. I added it below(in bold).
Pros:
- It supports more distributed load balance operations(bundle assignment)
in a sequentially consistent manner
- For really large clusters, by a partitioned system topic, BSC can be more
scalable than the current sin
Hi,
On Wed, Oct 19, 2022 at 2:06 AM 丛搏 wrote:
> Hi, Heesung:
> I have some doubts.
> I review your PIP-192: New Pulsar Broker Load Balancer. I found that
> unload topic uses the leader broker to do, (Assigning, Return) uses
> the lookup request broker. why (Assigning, Return) not use a leader
>
Congrats!
Thanks,
Yunze
On Tue, Oct 18, 2022 at 4:06 PM Hang Chen wrote:
>
> Hi all,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Haiting Jiang
> (https://github.com/Jason918) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
> He is very act
>
> I think we could shrink the connectors a lot by removing from the NAR
> archives dependencies that are already present in the
> pulsar-functions-instance.
>
I mean java-instance.jar
Le mer. 19 oct. 2022 à 12:29, Christophe Bornet a
écrit :
> The pulsar-all docker image is pretty big. I assum
>
> The pulsar-all docker image is pretty big. I assume we will continue
> to build and package additional connectors. It would be great to
> figure out how to make it smaller at some point.
>
I think we could shrink the connectors a lot by removing from the NAR
archives dependencies that are alrea
Hi community,
Recently, I've submitted the following doc contribution guides to the
Pulsar GitHub repos [1].
They provide a set of guides offering best-practice suggestions for
contributing documentation to Pulsar with detailed instructions on the
contribution workflow and conventions.
Please fo
I just tested and the HTTP Sink works fine with the ClickHouse HTTP ingest
API.
Create table in ClickHouse:
CREATE TABLE test
(
col1 String
) ENGINE = MergeTree()
PRIMARY KEY (col1)
Create Sink:
bin/pulsar-admin sinks create -a
pulsar-io/http/target/pulsar-io-http-2.11.0-SNAPSHOT.nar -i my-to
Hi, Heesung:
I have some doubts.
I review your PIP-192: New Pulsar Broker Load Balancer. I found that
unload topic uses the leader broker to do, (Assigning, Return) uses
the lookup request broker. why (Assigning, Return) not use a leader
broker?
I can think of a few reasons:
1. reduce leader broker
11 matches
Mail list logo