What should be done to stabilize the API here?

[rtyler]

I think with the recent work from @jakesandlund and @osheroff we've been bringing the Producer and Consumer APIs into parity and simplifying things a bit.

I'd like to push towards a 1.0 release with a stable API that we can all rely on and then move towards semver releases.

@osheroff please move the tickets you want to see in 1.0 accordingly, anything else we should aim to accomplish in 1.0?

[osheroff]

one thing on my todo list has been to allow librdkafka (and java) specific parameters to be passed in -- I need in some cases to limit the buffer size of rdkafka, and there's no elegant way to do this.

Other than that, to me a 1.0 is probably about trying to get feature parity best we can between java/rdkafka. It's tricky since with 0.8.3 the whole java client will be rewritten, but hey.

Note that I've had a MRI-based consumer eating away at 5-10k QPS in zendesk's production for some months now; so at least the consumer path is pretty solid!

[rtyler]

@osheroff you've got write access to this repository, will you create issues and stick them in the 1.0 milestone for all your wishlist items?

[barockok]

@rtyler Is there any plan to support librdkafka 0.9 ? I thought it would be nice, since kafka 0.9 already implemented balanced (high level) consumer, so I guess it would be possible to create consumer group for MRI.