[ANNOUNCE] Apache Pulsar Node.js client 1.3.0 released

The Apache Pulsar team is proud to announce Apache Pulsar Node.js client version 1.3.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

RE: [VOTE] Pulsar Node.js Client Release 1.3.0 Candidate 1

Closing the vote with 2 +1 and no -1. 2 +1 bindings are: * Nozomi * Hiroyuki -- Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Hiroyuki Sakai Sent: Monday, March 15, 2021 1:07 PM To: dev@pulsar.apache.org Subject: Re: [VOTE] Pulsar Node.js

Re: Enhancements to Pulsar IO

Hi Enrico, Thanks for taking the initiative for improvements on Pulsar IO! I have questions in regards to the following statements *Problem 1: Pulsar Sinks must declare at compile time the data type they support* > So I would like to see Sink and let the implementation deal with Record that wil

[GitHub] [pulsar-dotpulsar] blankensteiner closed issue #6: Support - Schema

blankensteiner closed issue #6: URL: https://github.com/apache/pulsar-dotpulsar/issues/6 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to g

[Ecosystem] SQS connector for Pulsar is available!

Hi Pulsar enthusiasts, As we know, both Pulsar and AWS SQS are popular message systems and they have welcoming and rapidly expanding communities. Many users want to be able to leverage the benefits of Pulsar and SQS. There comes a good news: today, StreamNative ships the first-ever release of

Re: Proposal to change how git checkout is done for PR builds

+1 That was the behavior we used to have in Jenkins. -- Matteo Merli On Wed, Mar 17, 2021 at 8:15 AM Michael Marshall wrote: > > +1 > > I like the idea that this change would give PRs the benefit of any recently > fixed flaky tests without needing to rebase. Rebasing to pick up fixes to > flak

Re: Proposal to change how git checkout is done for PR builds

+1 I like the idea that this change would give PRs the benefit of any recently fixed flaky tests without needing to rebase. Rebasing to pick up fixes to flaky tests slows down development. Further, I think this sounds like a safer paradigm for maintaining a pristine master branch. Michael On We

Enhancements to Pulsar IO

Hello everyone, I would like to share some proposals about Pulsar IO. Based on my experience porting a nontrivial connector for Cassandra from Kafka Connect to Pulsar IO, I would like to identify some places where we can improve the Pulsar IO API for both native Pulsar connectors and to improve f

Re: Proposal to change how git checkout is done for PR builds

Il giorno mer 17 mar 2021 alle ore 08:56 Lari Hotari ha scritto: > > Dear Pulsar community members, > > I would like to propose a change how Pull Request (PR) builds are handled > in Pulsar CI. > > In GitHub Actions, the default way to handle PR builds is to checkout > GitHub provided merge_commit

Proposal to change how git checkout is done for PR builds

Dear Pulsar community members, I would like to propose a change how Pull Request (PR) builds are handled in Pulsar CI. In GitHub Actions, the default way to handle PR builds is to checkout GitHub provided merge_commit_sha . GitHub's merge_commit_sha is explained in this documentation: https://do

[GitHub] [pulsar-manager] LutzWeischerFujitsu opened a new issue #376: build fails on AArch64, Fedora 33

LutzWeischerFujitsu opened a new issue #376: URL: https://github.com/apache/pulsar-manager/issues/376 [jw@cn06 pulsar-manager]$ ./gradlew build -x test Downloading https://services.gradle.org/distributions/gradle-4.8.1-bin.zip ...