Re: [VOTE] Pulsar Client Go Release 0.1.0 Candidate 1

+1 Thanks xiaolong for your great work On 2020/3/25, 13:43, "xiaolong ran" wrote: Hi everyone, Please review and vote on the release candidate #1 for the version 0.1.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific co

Re: Kafka-on-Pulsar: bring the native Kafka protocol support to Apache Pulsar

Awesome +1 On Wed, 25 Mar 2020 at 10:36, Sijie Guo wrote: > > Hi all, > > We are super excited to share that StreamNative and OVHcloud have just > open-sourced the Kafka-on-Pulsar (a.k.a KoP) protocol handler today. KoP is a > protocol handler that handles the Kafka 2.0+ protocol. It can be ins

Re: [VOTE] Pulsar Client Go Release 0.1.0 Candidate 1

+1 On Wed, 25 Mar 2020 at 11:13, xiaolong ran wrote: > > Hi everyone, > > Please review and vote on the release candidate #1 for the version 0.1.0, as > follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the first release ca

[VOTE] Pulsar Client Go Release 0.1.0 Candidate 1

Hi everyone, Please review and vote on the release candidate #1 for the version 0.1.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This is the first release candidate for Apache Pulsar Go client, version 0.1.0. It fixes the follo

Re: [Discuss] Create the first release of Apache Pulsar-client-go

Hello everyone: Vote results: Binding: - Penghui Li - Jia Zhai - Sijie Guo Non-binding: - ran Leon - 丛搏 - lan.liang - Ali Ahmed - Guangning E I am starting the release process of 0.1.0. If you have any pull requests that must be included in 0.1.0, please let me know. > 在 2020年3月20日，下午7:2

Kafka-on-Pulsar: bring the native Kafka protocol support to Apache Pulsar

Hi all, We are super excited to share that StreamNative and OVHcloud have just open-sourced the Kafka-on-Pulsar (a.k.a KoP) protocol handler today. KoP is a protocol handler that handles the Kafka 2.0+ protocol. It can be installed to your Pulsar brokers (2.5.0 or newer version) to enable native K

[GitHub] [pulsar-client-node] hrsakai commented on issue #9: Support Logger and Options for Custom Logger

hrsakai commented on issue #9: Support Logger and Options for Custom Logger URL: https://github.com/apache/pulsar-client-node/issues/9#issuecomment-603636222 Closed by https://github.com/apache/pulsar-client-node/pull/82 This

[GitHub] [pulsar-client-node] hrsakai closed issue #9: Support Logger and Options for Custom Logger

hrsakai closed issue #9: Support Logger and Options for Custom Logger URL: https://github.com/apache/pulsar-client-node/issues/9 This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [Discuss] Create the first release of Apache Pulsar-client-go

+1 On Sun, Mar 22, 2020 at 9:01 PM ran leon wrote: > That's so cool! +1 > > On 2020/03/20 11:22:03, xiaolong ran wrote: > > Hello committers, > > > > Since: > > - A lot of users use [pulsar-client-go]( > https://github.com/apache/pulsar-client-go < > https://github.com/apache/pulsar-client-go>)

Re: Pulsar Release 2.5.1 Discussion

+1 On Mon, Mar 23, 2020 at 6:42 PM PengHui Li wrote: > Thanks Guangning E work for this. > > Thanks, > Penghui > On Mar 23, 2020, 11:37 AM +0800, Jia Zhai , wrote: > > 👍 > > > > Best Regards. > > > > > > Jia Zhai > > > > Beijing, China > > > > Mobile: +86 15810491983 > > > > > > > > > > On Mon,

[GitHub] [pulsar-client-node] yosiat edited a comment on issue #83: Consumer with message listener dies after some time

yosiat edited a comment on issue #83: Consumer with message listener dies after some time URL: https://github.com/apache/pulsar-client-node/pull/83#issuecomment-603287205 @hrsakai @sijie can you please look at this PR? I would appreciate your help here. -

[GitHub] [pulsar-client-node] yosiat commented on issue #78: Error: Failed to send message: AlreadyClosed

yosiat commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-603524312 @sijie sounds like a good approach, I tried my approach of creating napi ref, but couldn't find a way to implement it. I wi

[GitHub] [pulsar-client-node] sijie commented on issue #78: Error: Failed to send message: AlreadyClosed

sijie commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-603522717 @alexyans @yosiat I think we can let Producer object keep a reference to the client. So if your application keeps references to Pro

[GitHub] [pulsar-client-node] lcartercondon commented on issue #81: Support seting topic schema when creating producers/consumers

lcartercondon commented on issue #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#issuecomment-603416184 @massakam I think this is fine - any user of a schema'd topic is (with this implementation) still responsible

[GitHub] [pulsar-client-node] lcartercondon commented on issue #81: Support seting topic schema when creating producers/consumers

lcartercondon commented on issue #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#issuecomment-603398011 This simply allows the NodeJS client to specify the schema when creating the producer or consumer - it doesn'

[GitHub] [pulsar-client-node] yosiat commented on issue #17: Support Registration of MessageListener

yosiat commented on issue #17: Support Registration of MessageListener URL: https://github.com/apache/pulsar-client-node/issues/17#issuecomment-603288173 hey @k2la, this feature exists in the client, see issue: https://github.com/apache/pulsar-client-node/issues/62 I did a fix fo

[GitHub] [pulsar-client-node] yosiat commented on issue #83: Consumer with message listener dies after some time

yosiat commented on issue #83: Consumer with message listener dies after some time URL: https://github.com/apache/pulsar-client-node/pull/83#issuecomment-603287205 @hrrsakai @sijie can you please look at this PR? I would appreciate your help here. ---

Jenkins build is back to normal : pulsar_release_nightly_snapshot #762

See

Slack digest for #dev - 2020-03-24

2020-03-23 11:50:52 UTC - Lin Yiming: @Lin Yiming has joined the channel

Build failed in Jenkins: pulsar-website-build #943

See Changes: [github] ProducerBusy and ConsumerBusy exceptions are unretriable ones (#6595) [github] [PulsarAdmin] Topics to async (#6593) -- [...truncated 3.93 MB...