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

massakam commented on issue #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#issuecomment-604198539 In the case of Python and Go libraries, it seems that binary data and deserialized data can be obtained from diffe

[GitHub] [pulsar-client-node] massakam closed issue #78: Error: Failed to send message: AlreadyClosed

massakam closed issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78 This is an automated message from the Apache Git Service. To respond to the message, please

[GitHub] [pulsar-client-node] massakam merged pull request #85: Create reference for client

massakam merged pull request #85: Create reference for client URL: https://github.com/apache/pulsar-client-node/pull/85 This is an automated message from the Apache Git Service. To respond to the message, please log on to Git

[GitHub] [pulsar-client-node] sijie commented on issue #85: Create reference for client

sijie commented on issue #85: Create reference for client URL: https://github.com/apache/pulsar-client-node/pull/85#issuecomment-604173500 @yosiat this is cool! Thank you for your contribution! This is an automated message fro

#TGIPulsar Episode 003 - Secure a Pulsar cluster with TLS

Hi all, Our weekly live stream "TGI Pulsar" ( https://www.youtube.com/channel/UCywxUI5HlIyc0VEKYR4X9Pg/live) continues this week. In this week's episode, we are going to talk about how to secure a Pulsar cluster with TLS. It will cover not only brokers and proxies but also bookies as well. If you

Re: Unable to consume messages, need to re-subscribe or restart

Hi Gaurav, There are a couple of things to check. 1) Which version of Pulsar are you using? 2) Which language of Pulsar client are you using? 3) Did your consumers acknowledge the messages after processing them? 4) When the issue happens, did you happen to capture the stats of the topic? You can

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

+1 On Tue, Mar 24, 2020 at 11:26 PM anonymitaet _ wrote: > +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 re

[GitHub] [pulsar-client-node] yosiat commented on issue #85: Create reference for client

yosiat commented on issue #85: Create reference for client URL: https://github.com/apache/pulsar-client-node/pull/85#issuecomment-604069164 @hrsakai @sijie can you please review this PR ? This is an automated message from the

Unable to consume messages, need to re-subscribe or restart

Hi, We recently started using apache pulsar instead of apache Kafka, we are experiencing problem with our apache pulsar consumer. Suddenly after sometime apache pulsar, consumer stops consuming messages and backlog keeps increasing. We did not found any error in logs. Post restarting consumer a

[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-603934481 > isn't it a breaking change for them to support automatic encoding/decoding? This is a great point - I

[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-603868358 @sijie tried out creating a reference to a client from the producer but it didn't help (tried with InstanceAccesor) and it created

[GitHub] [pulsar-client-node] yosiat opened a new pull request #85: Create reference for client

yosiat opened a new pull request #85: Create reference for client URL: https://github.com/apache/pulsar-client-node/pull/85 Since we don’t have reference for the client, v8 can garbage collect this instance, which can cause the next code: ``` const Pulsar = require('pulsar-client'

Build failed in Jenkins: pulsar_release_nightly_snapshot #763

See Changes: [github] [cleanup] Enable checkstyle in pulsar-client-admin module (#6596) [github] [Issue 6043] Support force deleting subscription (#6383) [github] [minor]Fix style in pulsar-client

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

See Changes: [github] [cleanup] Enable checkstyle in pulsar-client-admin module (#6596) [github] [Issue 6043] Support force deleting subscription (#6383) [github] [minor]Fix style in pulsar-client-admin (#66

[GitHub] [pulsar-client-node] massakam edited a comment on issue #81: Support seting topic schema when creating producers/consumers

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

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

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