bpot / poseidon / 259

Builds Branch Commit Type Ran Committer Via Coverage
259 master Karafka as an aleternative for Poseidon Pull #120 web-flow travis-ci pending completion
257 master Recover when messages are removed from kafka OffsetOutOfRange error can also happen when the returned offset is a positive number but corresponding messages started from the offset were retentioned. By @ymattw: https://github.com/bpot/poseidon/pu... Pull #119 alexcastano travis-ci pending completion
256 master Unmaintained push bpot travis-ci pending completion
255 master Fix usage of String.bytes (Enumerator in 1.9.3 and jruby) to pass CI. Pull #109 ovy-altiscale travis-ci pending completion
254 master Remove duplicate line in producer documentation Pull #117 Ben-M travis-ci pending completion
253 master rm test Pull #113 liukgg travis-ci pending completion
252 master test Pull #113 liukgg travis-ci pending completion
251 master rm specs to pass ci check Pull #111 liukgg travis-ci pending completion
250 master spec opt Pull #111 liukgg travis-ci pending completion
249 master optimize MessageToSend#initialize Pull #111 liukgg travis-ci pending completion
248 master Remove leftover test code from library. Add test for one partition case. Pull #109 ovy-altiscale travis-ci pending completion
247 master Add seek_to_offset functionality to PartitionConsumer. As it turns out, it's a simple matter of changing where the next fetch will be requested (a state variable). The method accepts the same special offsets as the constructor. Pull #110 ovy-altiscale travis-ci pending completion
246 master Add Ruby implementation of Kafka's partition hasher (based on key). Test that it matches results from Java. Not hooked up yet (future commits), but can already be used manually by a client. Pull #109 ovy-altiscale travis-ci pending completion
245 master ignore under-replicated errors Pull #105 skandragon travis-ci pending completion
244 master Reset offset to :earliest_offset whenever OffsetOutOfRange happens OffsetOutOfRange error can also happen when the returned offset is a positive number but corresponding messages started from the offset were retentioned Pull #102 ymattw travis-ci pending completion