Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Branch: master
Commits on May 1, 2015
  1. Merge pull request #24 from terrancesnyder/master

    Updates to fix issue when reading snappy
Commits on Apr 6, 2015
  1. @terrancesnyder

    update version #

    terrancesnyder authored
  2. @terrancesnyder

    pre-install notes

    terrancesnyder authored
  3. @terrancesnyder

    pre-install notes

    terrancesnyder authored
  4. @terrancesnyder
  5. @terrancesnyder

    More real world example

    terrancesnyder authored
    More real world example including reading AVRO from kafka
  6. @terrancesnyder


    terrancesnyder authored
    Not required with latest snappy lib - serializes just fine
  7. @terrancesnyder
Commits on Mar 31, 2013
  1. bumped gemspec for bugfix

    Ale authored
  2. changed ambiguous method send for push

    Ale authored
  3. updated and bumped gemspec

    Ale authored
  4. updated gemspec

    Ale authored
  5. Merge pull request #20 from MichaelXavier/producer-send-rename

    Rename producer/multi-producer methods to push
Commits on Mar 5, 2013
  1. @MichaelXavier

    Rename producer/multi-producer methods to push

    MichaelXavier authored
    Send is problematic in ruby because it is defined on all objects as a
    way to dynamically send method calls (messages). You do not want to have
    any methods in your interface that define send.
    This would resolve #18
Commits on Feb 16, 2013
  1. @guillermo

    Add kafka-subscribe and kafka-publish commands

    guillermo authored
    *kafka-subscribe* and *kafka-publish* are command line programs to help
    in the task of debugging a kafka installation.
Commits on Dec 19, 2012
  1. Merge pull request #15 from bcotton/snappy-compression

    Added Snappy compression
Commits on Dec 11, 2012
  1. @watersofoblivion

    Added support for Snappy compression to the Consumer, and added compr…

    Bob Cotton authored watersofoblivion committed
    …ession (Snappy and GZip) to the Producer and MultiProducer.
    To enable snappy compression, include the following in your Gemfile (This branch is necessary until a pending pull request is accepted):
        gem "snappy", "0.0.4", :git => "git://", :branch => "snappy-streaming"
Commits on Sep 12, 2012
  1. bumped version for bugfixes

    Alejandro Crosa authored
  2. Merge branch 'ls/gemspec' of

    Alejandro Crosa authored
    …into liamstewart-ls/gemspec
  3. Specs specified in s.test_files rather than s.files.

    Liam Stewart authored
  4. Replace deprecated rubygems/gempackagetask with package_task.

    Liam Stewart authored
    Don't specify rubygems_version - set when package created.
    Specify files in lib/spec with globs.
  5. bumped version

    Alejandro Crosa authored
  6. added contributor

    Alejandro Crosa authored
  7. bumping version for gem push

    Alejandro Crosa authored
  8. Merge pull request #12 from liamstewart/ls/multi_producer

    Multiproduce support
Commits on Sep 11, 2012
  1. Remove code that now lives in the Encode module.

    Liam Stewart authored
  2. Add a MultiProducer module.

    Liam Stewart authored
    Like Producer, but doesn't have a fixed topic and partition. 'send' sends
    a single message or a set of messages to the same topic/partition using the
    'produce' request type. 'multi_send' sends groups of messages across
    partitions/topics using the 'multiproduce' request type.
  3. Add an Encoder module.

    Liam Stewart authored
    Provides methods for encoding messages, produce requests, and multiproduce
  4. Add a ProducerRequest class.

    Liam Stewart authored
    A ProducerRequest instance is a very simple wrapper around a topic, partition,
    and set of messages.
  5. Make the default host/port constants in the IO module.

    Liam Stewart authored
Commits on Aug 9, 2012
  1. Merge pull request #11 from ept/compression

    Add consumer support for transparent gzip compression
  2. Merge pull request #10 from ept/spec-warning

    Fix a warning about top-level constant reference while running the specs
  3. @ept
Something went wrong with that request. Please try again.