GitHub user tisonkun added a comment to the discussion: Ruby Client Support
One alternative is using the
[REST](https://pulsar.apache.org/docs/next/client-libraries-rest/) or
[WebSocket](https://pulsar.apache.org/docs/next/client-libraries-websocket/)
interface which is language-agnostic. IIR
GitHub user tisonkun added a comment to the discussion: Ruby Client Support
There is a http://github.com/apache/pulsar-client-ruby repo but it's halted.
There were several efforts trying to wrap the C++ client to a Ruby gem and you
may find some released gems at https://rubygems.org/gems/pulsa
Great catch, Enrico. I saw the returned `null` in
`BookieServiceInfoSerde#deserialize`, but I didn't know its impact.
Thanks,
Michael
On Wed, Sep 21, 2022 at 8:30 AM Haiting Jiang wrote:
>
> Sure, I have added the release label in this PR.
>
> BTW, the 2.10.2 release is almost ready for RC1 exc
GitHub user michaeljmarshall added a comment to the discussion: Ruby Client
Support
I don't know of any active work being done on a Pulsar Ruby Client. I know
almost nothing about Ruby, but is it possible to use the Pulsar C++ Client in
your Ruby code? Our Python client is currently a wrapper
Hi Christophe,
I think this is a very good idea!
I agree with Enrico that the body should depend on the record schema, but
it could also be done as a follow-up task.
Another thing to think about could be an optional batching mechanism that
would take a batch of records and send them as a list of
Sure, I have added the release label in this PR.
BTW, the 2.10.2 release is almost ready for RC1 except that there is
an owasp ci failure on branch-2.10. Please help take a look.
https://github.com/apache/pulsar/pull/17765
Thanks,
Haiting
On Wed, Sep 21, 2022 at 3:18 PM Enrico Olivelli wrote:
bharatbhushan1705 commented on issue #287:
URL:
https://github.com/apache/pulsar-helm-chart/issues/287#issuecomment-1253503381
@michaeljmarshall Could you please help me here with some quick steps to
solve locally at lease.
--
This is an automated message from the Apache Git Service.
To
Hello folks,
I have found that since Pulsar 2.10 you cannot set a custom BookieId anymore.
The fix is easy
https://github.com/apache/pulsar/pull/17762
I am pretty sure it worked on Pulsar 2.8 (I sent out a patch for
supporting the bookieId on the Helm Chart).
I think that we should cherry-pick t
