:22 PM
To: dev@kafka.apache.org
Subject: Re: Metadata class doesn't "expose" topics with errors
Hello Paolo,
I'm looking at your PR for KIP-204 now. Will reply on the discussion thread
/ PR diff file directly if I find anything.
Guozhang
On Tue, Oct 24, 2017 at 5:45 AM, Paolo Patierno <
<http://paolopatierno.wordpress.com/>
>
>
> ________
> From: Guozhang Wang <wangg...@gmail.com>
> Sent: Tuesday, October 24, 2017 12:52 AM
> To: dev@kafka.apache.org
> Subject: Re: Metadata class doesn't "expose" topics with errors
>
...@gmail.com>
Sent: Tuesday, October 24, 2017 12:52 AM
To: dev@kafka.apache.org
Subject: Re: Metadata class doesn't "expose" topics with errors
Hello Paolo,
The reason we filtered the errors in the topics in the generated Cluster is
that Metadata and its "fetch()" returne
Hello Paolo,
The reason we filtered the errors in the topics in the generated Cluster is
that Metadata and its "fetch()" returned Cluster is a common class that is
used among all clients (producer, consumer, connect, streams, admin), and
is treated as a high-level representation of the current
Finally another plan could be to use nesting of runnable calls.
The first one for asking metadata (using the MetadataRequest which provides us
all the errors) and then sending the delete records requests in the
handleResponse() of such metadata request.
Paolo Patierno
Senior Software Engineer
I'd like just to add that in my specific case I could resolve creating a new
NodeProvider implementation like LeaderForProvider in order to send the request
to the right leader for each topic.
The drawback of this solution is not grouping topics for the same leader so not
having only one
