+1
Checked the signatures, complied and ran the pular perf tool (produce
and consume) against a standalone cluster.
On Wed, Feb 16, 2022 at 5:29 PM PengHui Li wrote:
>
> +1
>
> - Checked the signatures
> - Run produce and consume on a standalone
>
> Penghui
>
> On Thu, Feb 17, 2022 at 12:45 AM M
The Apache Pulsar team is proud to announce Apache Pulsar Go Client version
0.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
.apache.org/repos/dist/dev/pulsar/KEYS
> > to verify signature
> >
> > because
> > https://dist.apache.org/repos/dist/release/pulsar/KEYS
> > does not contain Chris's KEY.
> >
> > Hideaki Oguni
> > Yahoo Japan Corp.
> > E-mail: hog...@yahoo-corp.
ksums:
8ab27de0adce2324c93936c0df15eceffd91a060ed275320ff167e5c9cfeb681107b17d80712ab1baa01b0abfd8f467d0b3d6ab38398d1dda025c47792b97fe1
apache-pulsar-client-go-0.7.0-src.tar.gz
Thanks.
Chris Kellogg
oll this release? If so then you should look at
> the PR and decide if you want to include it.
>
> Sent from my iPhone
>
> > On Oct 21, 2021, at 6:52 PM, Chris Kellogg wrote:
> >
> > What's the policy for waiting on PRs to merge? I was hoping to cut a
&
o master.
> https://github.com/apache/pulsar-client-go/pull/528
>
> --
> Thanks
> Xiaolong Ran
>
> Enrico Olivelli 于2021年10月21日周四 下午2:33写道：
>
> > Chris,
> >
> > Il Gio 21 Ott 2021, 04:09 Chris Kellogg ha
> scritto:
> >
> > > Hello,
> > >
Hello,
It's been a while since the last go client release (July 25th). There have
been many fixes that have gone in since then and I think it's time for a
new release.
I would like to volunteer to coordinate the next go client release. Please
let me know if that works and If there are things that
It seems like an application can already do something like this without any
changes to the clients?
An application could read the message properties and then figure out the
next time interval it should use the for the ReconsumeLater method. The
leveling concept could be a small piece of code the a
I would like to propose adding support for dynamic proxy roles. Currently,
the only way to provide proxy roles is through the broker.conf file. This
makes it challenging to automate cluster provisioning. Additionally, the
hardcoding of the proxy roles in the broker.conf makes it difficult to
revoke
The Pulsar code base uses different terms (principal, role, client-id,
app-id, etc..) when referring to authentication and authorization.
Different places use different terms that may or may not mean the same
thing. All these different terms get overloaded and make it confusing to
reason about the
10 matches
Mail list logo
