Hey Manikumar,

This looks good. Do we have to keep the current behavior when handling old
DeleteTopics versions? I'm wondering if it would be better to return an
UNKNOWN_ERROR (say) and let the client raise that to the user instead of
just timing out.

Thanks,
Jason

On Fri, Jul 20, 2018 at 10:00 AM, Manikumar <[email protected]>
wrote:

> Bumping this thread.
>
> On Tue, Jul 10, 2018 at 10:33 PM Manikumar <[email protected]>
> wrote:
>
> > Waiting for one more binding vote to pass this minor KIP.  Appreciate
> your
> > vote.
> >
> > On Wed, Jul 4, 2018 at 7:03 PM Eno Thereska <[email protected]>
> > wrote:
> >
> >> +1 (non binding)
> >>
> >> On Wed, Jul 4, 2018 at 1:19 PM, Kamal Chandraprakash <
> >> [email protected]> wrote:
> >>
> >> > +1 (non-binding)
> >> >
> >> > On Wed, Jul 4, 2018 at 5:22 PM Magnus Edenhill <[email protected]>
> >> wrote:
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > 2018-07-04 13:40 GMT+02:00 Satish Duggana <[email protected]
> >:
> >> > >
> >> > > > +1
> >> > > >
> >> > > > Thanks,
> >> > > > Satish.
> >> > > >
> >> > > > On Wed, Jul 4, 2018 at 4:11 PM, Daniele Ascione <
> >> [email protected]>
> >> > > > wrote:
> >> > > >
> >> > > > > +1
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Daniele
> >> > > > >
> >> > > > > Il giorno mar 3 lug 2018 alle ore 23:55 Harsha <[email protected]
> >
> >> ha
> >> > > > > scritto:
> >> > > > >
> >> > > > > > +1.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > Harsha
> >> > > > > >
> >> > > > > > On Tue, Jul 3rd, 2018 at 9:22 AM, Ted Yu <[email protected]
> >
> >> > > wrote:
> >> > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > +1
> >> > > > > > >
> >> > > > > > > On Tue, Jul 3, 2018 at 9:05 AM, Mickael Maison <
> >> > > > > > [email protected] >
> >> > > > > > >
> >> > > > > > > wrote:
> >> > > > > > >
> >> > > > > > > > +1 (non binding)
> >> > > > > > > > Thanks for the KIP
> >> > > > > > > >
> >> > > > > > > > On Tue, Jul 3, 2018 at 4:59 PM, Vahid S Hashemian
> >> > > > > > > > < [email protected] > wrote:
> >> > > > > > > > > +1 (non-binding)
> >> > > > > > > > >
> >> > > > > > > > > --Vahid
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > From: Gwen Shapira < [email protected] >
> >> > > > > > > > > To: dev < [email protected] >
> >> > > > > > > > > Date: 07/03/2018 08:49 AM
> >> > > > > > > > > Subject: Re: [VOTE] KIP-322: Return new error code for
> >> > > > > > > > DeleteTopics
> >> > > > > > > > > API when topic deletion disabled.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > +1
> >> > > > > > > > >
> >> > > > > > > > > On Tue, Jul 3, 2018 at 8:24 AM, Manikumar <
> >> > > > > > [email protected] >
> >> > > > > > >
> >> > > > > > > > > wrote:
> >> > > > > > > > >
> >> > > > > > > > >> Manikumar < [email protected] >
> >> > > > > > > > >> Fri, Jun 29, 7:59 PM (4 days ago)
> >> > > > > > > > >> to dev
> >> > > > > > > > >> Hi All,
> >> > > > > > > > >>
> >> > > > > > > > >> I would like to start voting on KIP-322 which would
> >> return
> >> > new
> >> > > > > error
> >> > > > > > > > > code
> >> > > > > > > > >> for DeleteTopics API when topic deletion disabled.
> >> > > > > > > > >>
> >> > > > > > > > >>
> >> > > > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.
> >> > > > > > > > action?pageId=87295558
> >> > > > > > > > >
> >> > > > > > > > >>
> >> > > > > > > > >> Thanks,
> >> > > > > > > > >>
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > --
> >> > > > > > > > > *Gwen Shapira*
> >> > > > > > > > > Product Manager | Confluent
> >> > > > > > > > > 650.450.2760 | @gwenshap
> >> > > > > > > > > Follow us: Twitter <
> >> > > > > > > > > https://twitter.com/ConfluentInc
> >> > > > > > > > >> | blog
> >> > > > > > > > > <
> >> > > > > > > > > http://www.confluent.io/blog
> >> > > > > > > > >>
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
>

Reply via email to