This is the Pulsar community weekly update for 2019-12-21 ~ 2020-01-03, with updates on Pulsar Summit, Hacker news, and bug fixes for 2.5.0 release.
[CI] Efforts are continued to make GitHub Actions stable enough so that we can move CI from ASF Jenkins to GitHub Actions.
[Protocol Handler] A discussion thread about adding NSQ Protocol Support using the protocol handler framework.
[Pulsar Go Client] The development work for
pulsar-client-go continues towards the first apache release.
[Broker] Allow for namespace default of offload threshold (Release: 2.5.0).
[Broker] Fix read 0 entries cause message stop dispatch (Release: 2.5.0).
[Stats] Fix wrong redelivery count while redeliver when consumer disconnected (Release: 2.5.0).
[Client][Java] Add SentConnectFrame state check when running
handleError (Release: 2.5.0).
[Client][C++] Fix CPP client schema version (Release: 2.5.0).
[Proxy] Proxy doesn't use the right ca certificate to connect to brokers (Release: 2.5.0).
[Broker] ReadHandle.readAsync that does not catch the exception cause stalling consumption (Release: 2.5.0).
[Flink] Cache Pulsar client to make it shared among tasks in a process (Release: 2.5.0).
[Client][Reader] Fix reader builder clone error (Release: 2.5.0).
Pulsar.Client 0.12.0 released with delayed messages support.
The first Pulsar Summit will be held in April 2020 at San Francisco. The Call for Presentation and pre-registration are open.
Pulsar ranked 1st in Hacker News on Jan 2. Many engineers talked about "Why chooses Pulsar over Kafka, RabbitMQ, Kinesis or other MQ", "Pulsar features", and other topics.
From Apache Spark connector to Apache Pulsar basic concepts (by Bartosz Konieczny)