me piece of
> code), whereas the KStream is unbounded and hence you need to window it in
> order to materialize it so that if there is a late record from the KTable,
> it may still find the matching record from the windowed KStream. Is that
> right?
>
>
> Guozhang
>
>
>
>
that was in the record stream (+you can't specify a windows for
a KStream-KTable).
On Wed, Jul 20, 2016 at 11:14 AM, Nicolas PHUNG <nsphung.apa...@gmail.com>
wrote:
> Hi,
>
> Thank you for your answer @Matthias. Indeed, I need a kind of symmetric
> join. However, KStream-KStream join doe
eed a symmetric join (ie, lookup for both directions), you can
> > either use a KTable-KTable or KStream-KStream join. Not sure, if this
> > might work for your use case.
> >
> > -Matthias
> >
> >
> > On 07/19/2016 01:36 PM, Nicolas PHUNG wrote:
>
,
Nicolas PHUNG
are only attempted for
> retriable errors. If a message is too large, retrying won't help (it will
> still be too large). However, if a leader is not available, then a retry
> will happen as the leader may be available then.
>
> Ismael
>
> On Wed, Apr 20, 2016 at 1:00 PM, Nicolas
going to take a look if someone else has filed a related issue about it.
Regards,
Nicolas PHUNG
On Thu, Apr 7, 2016 at 5:15 AM, christopher palm <cpa...@gmail.com> wrote:
> Hi Thanks for the suggestion.
> I lowered the broker message.max.bytes to be smaller than my payload so
> tha
it but with no further step to resolve the issue. Do
you have any informations regarding this ?
Is it possible in Kafka to somehow reread the topic and drop corrupt
message ?
Regards,
Nicolas PHUNG
