Chris,
Il Gio 21 Ott 2021, 04:09 Chris Kellogg ha scritto:
> 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.
>
Good idea
+1
Enrico
> I would like to volunteer to c
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
Hello,
I've encountered situation that results in a hanging debezium connector.
The rootcause is that the debezium task can throw unchecked exception and
that situation is not handled.
PR with the unit test and fix: https://github.com/apache/pulsar/pull/12441
I'd appreciate reviews and feedback.
Hi Vijaya,
Can you report the issue in the Flink Jira? We will follow up on the memory
leak issue.
The source connector was released as part of Flink 1.14 is a new
implementation based on the new Flink source API. If you are using Flink
1.12 or older versions, you can use this connector (
https:/
Thanks Masahiro!
- Sijie
On Tue, Oct 19, 2021 at 4:34 AM Masahiro Sakamoto
wrote:
> The Apache Pulsar team is proud to announce Apache Pulsar Node.js client
> version 1.3.2 and 1.4.1.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> commodity hardware. It provides si
blankensteiner commented on issue #92:
URL: https://github.com/apache/pulsar-dotpulsar/issues/92#issuecomment-947754149
Does the broker close an active connection when the token expires? Or is it
just validated when the connection is established and then first becomes a
problem when reconn
