Yeah, I'm supportive of this. On Thu, Aug 25, 2016 at 9:26 AM Ismael Juma <ism...@juma.me.uk> wrote:
> Hi Gwen, > > We have a few recent stories of people using Connect and Streams in > production. That means the new Java Consumer too. :) > > Ismael > > On Thu, Aug 25, 2016 at 5:09 PM, Gwen Shapira <g...@confluent.io> wrote: > > > Originally, we suggested keeping the beta label until we know someone > > successfully uses the new consumer in production. > > > > We can consider the recent KIPs enough, but IMO it will be better if > > someone with production deployment hanging out on our mailing list > > will confirm good experience with the new consumer. > > > > Gwen > > > > On Wed, Aug 24, 2016 at 8:45 PM, Ismael Juma <ism...@juma.me.uk> wrote: > > > Hi all, > > > > > > We currently say the following in our documentation: > > > > > > "As of the 0.9.0 release we have added a new Java consumer to replace > our > > > existing high-level ZooKeeper-based consumer and low-level consumer > APIs. > > > This client is considered beta quality."[1] > > > > > > Since then, Jason and the community have done a lot of work to improve > it > > > (including KIP-41 and KIP-62), we declared it API stable in 0.10.0.0 > and > > > it's the only option for those that need security support. Yes, it > still > > > has bugs, but so does the old consumer and all development is currently > > > focused on the new consumer. > > > > > > As such, I propose we remove the beta label for the next release and > > switch > > > our tools to use the new consumer by default unless the zookeeper > > > command-line option is present (for compatibility). This is similar to > > what > > > we did it for the new producer in 0.9.0.0, but backwards compatible. > > > > > > Thoughts? > > > > > > Ismael > > > > > > [1] http://kafka.apache.org/documentation.html#consumerapi > > > > > > > > -- > > Gwen Shapira > > Product Manager | Confluent > > 650.450.2760 | @gwenshap > > Follow us: Twitter | blog > > > -- Thanks, Neha
