+1 (non-binding). small nit pick - just because you returned a response to user doesnt mean the memory id no longer used. for some cases the actual "point of termination" may be the deserializer (really impl-dependant), but generally, wouldnt it be "nice" to have an explicit dispose() call on responses (with the addition that getting the next batch of data from a consumer automatically disposes the previous results)
On Mon, Dec 5, 2016 at 6:53 AM, Edoardo Comar <eco...@uk.ibm.com> wrote: > +1 (non binding) > -------------------------------------------------- > Edoardo Comar > IBM MessageHub > eco...@uk.ibm.com > IBM UK Ltd, Hursley Park, SO21 2JN > > IBM United Kingdom Limited Registered in England and Wales with number > 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 > 3AU > > > > From: Mickael Maison <mickael.mai...@gmail.com> > To: dev@kafka.apache.org > Date: 05/12/2016 14:38 > Subject: [VOTE] KIP-81: Bound Fetch memory usage in the consumer > > > > Hi all, > > I'd like to start the vote for KIP-81: > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 81%3A+Bound+Fetch+memory+usage+in+the+consumer > > > Thank you > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU >
