Skip to content

Reader interface #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 29 commits into
base: master
Choose a base branch
from
Open

Reader interface #1

wants to merge 29 commits into from

Conversation

lukfugl
Copy link

@lukfugl lukfugl commented Mar 20, 2020

Adds reader interface alongside producer and consumer.

lukfugl and others added 29 commits June 3, 2019 10:49
can send from a producer and receive and acknowledge from a consumer
so that Producer::send can just take the Message cpp-side

also fix service_url handling in bin/example-*
also, switch the using Module#prepend to decorate C++ defined methods
with ruby, rather than `_` prefixes
leave the placeholder in the C++ binding code, but don't actually bind
it, and don't use it in the example
to see if it makes a difference for where bundler puts the bindings.so
file. right now it's putting it in `lib/` instead of in `lib/pulsar/`
and use them in the example producer and consumer
and fix the topic name back to what it had been
still allow passing in the enum value integer directly, but also for
convenience translate a set of symbols too and from the enum values
This should fix this error that I ran into when using listen_in_thread:
```
bundler: failed to load command: ./client.rb (./client.rb)
LocalJumpError: no block given (yield)
  /home/docker/.gem/ruby/2.6.0/bundler/gems/pulsar-client-ruby-f915f9680abd/lib/pulsar/consumer.rb:42:in `listen'
  /home/docker/.gem/ruby/2.6.0/bundler/gems/pulsar-client-ruby-f915f9680abd/lib/pulsar/consumer.rb:48:in `block in listen_in_thread'
```
including allowing forwarding Hash argument from Client#subscribe
accidentally built and published .3 without the fix
inverted logic error checking sufficient environment, and a bare `gets`
tries to read from ARGV[0], when present, instead of the intended STDIN
@@ -1 +1,114 @@
# Apache Pulsar Ruby client

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be really useful to put just a broad checklist of the status of this as far as features, for example, let's call out that batch publishing and batch ack don't work yet.

@@ -0,0 +1,24 @@
# Confirm Licensing and Copyright

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh didn't see this file before. Some of this is specific to us, so we might want to strip it out? If we want to keep this file as the current state of the project, we should point the README at this file

@cristovao-alves-apilio
Copy link

Can this be approved and merged please? 😃

@tc-joegiralt
Copy link

Is this project dead in the water?

@addisonj
Copy link

Hi @tc-joegiralt, no it is not. Instructure has been leading the development and much of the development has happened in their fork here: https://github.com/instructure/pulsar-client-ruby

The goal is to get that all mainlined under apache, but there needs to be work put into the release process under Apache that has blocked this.

That should we should still get the code merged here first and then we can work towards getting the release process in place

@Seitk
Copy link

Seitk commented Mar 10, 2023

Just in case someone is still giving hope on pulsar client ruby, I am developing a forked version on my own and at least working.
https://github.com/Seitk/pulsar-client-ruby

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants