Slack digest for #dev - 2020-03-11

2020-03-10 15:23:51 UTC - Liam Condon: hey y'all - I'm finishing up some work on the NodeJS client to add topic schema support (and documentation for this "new" functionality) and am a bit curious about a few things. most importantly, where should serialization/deserialization actually occur for

deadletter policy related

Hi Team, I have a requirement and not sure if that is already part of Apache pulsar. We heavily rely on KeyShared subscriptions and need to understand if a functionality is already available. Question: If a message is in exception and moved to deadletter queue, will all the other messages of sam

[GitHub] [pulsar-client-node] lcartercondon opened a new pull request #81: Support seting topic schema when creating producers/consumers

lcartercondon opened a new pull request #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81 Added class to allow setting topic schema when creating producers/consumers --

[GitHub] [pulsar-client-node] mkaufmaner commented on a change in pull request #81: Support seting topic schema when creating producers/consumers

mkaufmaner commented on a change in pull request #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#discussion_r391024315 ## File path: src/ProducerConfig.cc ## @@ -33,6 +33,11 @@ static const std::s

[GitHub] [pulsar-client-node] mkaufmaner commented on a change in pull request #81: Support seting topic schema when creating producers/consumers

mkaufmaner commented on a change in pull request #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#discussion_r391025022 ## File path: src/SchemaInfo.h ## @@ -0,0 +1,45 @@ +/** + * Licensed to the A

[GitHub] [pulsar-client-node] lcartercondon commented on a change in pull request #81: Support seting topic schema when creating producers/consumers

lcartercondon commented on a change in pull request #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#discussion_r391029285 ## File path: src/ProducerConfig.cc ## @@ -33,6 +33,11 @@ static const std

[GitHub] [pulsar-client-node] lcartercondon commented on a change in pull request #81: Support seting topic schema when creating producers/consumers

lcartercondon commented on a change in pull request #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#discussion_r391030456 ## File path: src/ProducerConfig.cc ## @@ -33,6 +33,11 @@ static const std

[GitHub] [pulsar-client-node] lcartercondon commented on a change in pull request #81: Support seting topic schema when creating producers/consumers

lcartercondon commented on a change in pull request #81: Support seting topic schema when creating producers/consumers URL: https://github.com/apache/pulsar-client-node/pull/81#discussion_r391030537 ## File path: src/SchemaInfo.h ## @@ -0,0 +1,45 @@ +/** + * Licensed to th

Re: deadletter policy related

Hi Arun, Currently, the dead letter policy only worked for a shared subscription. It doesn't work for the subscriptions that have ordering implications such as "failover", "key_shared", and "exclusive". To better understand your requirements, what are the actions when a key is moved to a dead let

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

equanz commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-597964706 It seems that `setTimeout` callback function run after pulsar client was destructed. I think if use `setTimeout` in this case,