Re: PIP for gRPC protocol handler

Christophe, Thank you for putting this up. I have moved your proposal to pulsar wiki and assign the proposal with PIP-59. https://github.com/apache/pulsar/wiki/PIP-59%3A-gPRC-Protocol-Handler - Sijie On Thu, Mar 5, 2020 at 7:27 AM Christophe Bornet wrote: > Dear Pulsar team, > > I'd like to p

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

alijmlzd commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595434563 > For my use case, I worked around the problem by always creating the producer right before I emit a message. Flushing and closi

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

alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595336522 I tried 2.4 of the client as it was the one recommended by Kafkaesque, but the problem was still there for me. Didn't bother goi

PIP for gRPC protocol handler

Dear Pulsar team, I'd like to propose the following PIP on a gRPC protocol handler : https://gist.github.com/cbornet/f0a18c4528c2be129bb120cc231b62c6 See https://github.com/apache/pulsar/issues/271 for a discussion on having gRPC as an alternative protocol for Pulsar. I also have a MVP of the feat

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

alijmlzd commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595282893 @alexyans No, but I will try that and share my result. By the way, what version you recommend to start? -

Jenkins build is back to normal : pulsar-website-build #927

See

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

alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595136257 @alijmlzd did you try rolling back to an older version? Any luck finding one? --

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

alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595133166 I have the same problem. Sending a message immediately after initializing the producer works fine, so it can't be a TLS handshak

Slack digest for #dev - 2020-03-05

2020-03-04 10:35:30 UTC - Konstantinos Papalias: Hi @Devin G. Bost thanks for the insight, can you elaborate a bit more on what you mean with a `Pulsar consumer` for deploying functions ? Is there any source code you could share as a reference if it's not sensitive info ? 2020-03-04 10:39:4