Since the APIs are super different, I expect migrating from the old to the new consumer will involve some re-write of the app that does the consuming. In most such cases, the upgrade path involves running both versions side-by-side for a while, validating results and then retiring the old version. Sometimes migration of offsets is needed and Grant published a tool for that a while back.
Having a rolling upgrade plan between both APIs is pretty involved and I'm not sure there's a real demand for it (i.e. it sounds good to have it, but that's probably not how people will end up migrating). Gwen On Thu, Jan 5, 2017 at 3:42 PM, radai <radai.rosenbl...@gmail.com> wrote: > im all for (working towards) getting rid of old code, but there's still no > solid migration path - you'll be "stranding" users on deprecated, no longer > maintained code with no "safe" way out that does not involve downtime > (specifically old and new consumers cannot correctly divide up partitions > between themselves if both operate within the same group on the same topic). > > On Thu, Jan 5, 2017 at 3:10 PM, Gwen Shapira <g...@confluent.io> wrote: > >> Very strong support from me too :) >> >> On Thu, Jan 5, 2017 at 12:09 PM, Vahid S Hashemian >> <vahidhashem...@us.ibm.com> wrote: >> > Hi all, >> > >> > There was some discussion recently on deprecating the old consumer ( >> > https://www.mail-archive.com/dev@kafka.apache.org/msg59084.html). >> > Ismael suggested to cover the discussion and voting of major deprecations >> > like this under a KIP. >> > >> > So I started KIP-109 ( >> > https://cwiki.apache.org/confluence/display/KAFKA/KIP- >> 109%3A+Old+Consumer+Deprecation >> > ) and look forward to your feedback and comments. >> > >> > We'd like to implement this deprecation in the upcoming 0.10.2.0 release. >> > >> > Thanks. >> > --Vahid >> > >> >> >> >> -- >> Gwen Shapira >> Product Manager | Confluent >> 650.450.2760 | @gwenshap >> Follow us: Twitter | blog >> -- Gwen Shapira Product Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter | blog
