Go to file
R. Tyler Croy 7af7e3ec5b Avoid call to rb_string_value_cstr() which doesn't handle binary strings from Ruby properly
Fixes #32
2014-09-10 20:00:07 -07:00
ext/hermann Avoid call to rb_string_value_cstr() which doesn't handle binary strings from Ruby properly 2014-09-10 20:00:07 -07:00
lib Propagate system broker errors into Hermann::Result objects 2014-09-10 11:04:14 -07:00
scripts Refactor out the necessity for Hermann::Timeout and just rely in a Ruby-based busyloop 2014-09-09 16:45:17 -07:00
spec Avoid call to rb_string_value_cstr() which doesn't handle binary strings from Ruby properly 2014-09-10 20:00:07 -07:00
.gitignore Restructure the Hermann gem extension build process to use rake-compiler 2014-08-29 18:37:10 -07:00
.travis.yml
Gemfile Add Hermann::Timeout abstraction for 1.8/1.9 compatible timeout support 2014-09-09 14:40:10 -07:00
Gemfile.lock Add Hermann::Timeout abstraction for 1.8/1.9 compatible timeout support 2014-09-09 14:40:10 -07:00
LICENSE.md
README.md Add the gitter chat link to the readme 2014-09-02 14:01:55 -07:00
Rakefile Add a Rake task for running integration tests 2014-09-09 11:18:08 -07:00
hermann.gemspec Restructure the Hermann gem extension build process to use rake-compiler 2014-08-29 18:37:10 -07:00

README.md

Hermann

Gitter chat

A Ruby gem implementing a Kafka Publisher and Consumer

This library wraps the librdkafka library which is implemented in C. This library must be installed before we can use the Hermann gem.

Usage

Usage is modelled on the kafka-rb gem and is fairly straightforward.

  • Kafka 0.8 is supported.
  • Ruby 1.8.7 and Ruby 2.1.1 have been tested, but JRuby and versions

    = 1.8 should work as long as the librdkafka library is installed.

  • This is an early alpha version of the gem, so expect bumps in the road.

Note: The current implementation needs work to ensure thread safety.

Both Consumers and Producers now hold their own references to their Kafka state, and should be able to coexist nicely.

The brokers list and partition specification for Consumers are now working, as well. Producers will detect the number of partitions in a topic and randomly spread their messages over the set of partitions.

Consumers currently do not remember their "last message", nor do they yet coordinate partition (re)assigment within consumer groups.

Consumer

require 'hermann'

# Initialize requires topic, brokers list, and partition number

c = Hermann::Consumer.new( "device_actions", "localhost:9092", 0 )
c.consume() do
  |msg| puts("Received: #{msg}")
end

Producer

require 'hermann'

p = Hermann::Producer.new( "device_actions", "localhost:9092" )

messages = [ "Locate", "Scream", "Wipe", "Degauss" ]
messages.each do
    |msg| p.push(msg)
end

Questions?

Stan Campbell can be reached at stan.campbell3 at( @ ) gmail.com