Hi community
My team is faced with a very weird issue and still can't find the cause of
it. Once per two weeks our producers get timeouts during sending
data/metadata into Kafka cluster. In most cases, the issue was with leaders
of the same kafka broker. During this issue, we found nothing in our
Hi Matthias, thanks for the reply.
>> Can you elaborate? What is the behavior you expect?
I want my GlobalKTable reading records from a topic A, that is populated
within the same job
(so I want my table changing at runitme). The producer of A, takes a
key-mapped stream.
Next I perform a left join
I have had some success.
Is it okay for us to update Cwiki with the setup steps which I've got ? or
too generic?
On 16 May 2018 at 23:04, M. Manna wrote:
> Must have missed that in Kafka-run-class.bat which sets suspend=n by
> default. Thanks for pointing that out, giving it a try.
>
>
>
> And
Can you share what you plan to write (on the mailing list) ?
Thanks
On Thu, May 17, 2018 at 9:15 AM, M. Manna wrote:
> I have had some success.
>
> Is it okay for us to update Cwiki with the setup steps which I've got ? or
> too generic?
>
> On 16 May 2018 at 23:04, M. Manna wrote:
>
> > Must
>> So, are you implying that `GlobalKTable` can not consume records from a
>> topic populated at runtime by the same job,
>> but it needs instead a pre-populated topic either some other application
>> populating it?
No, I did not indent to imply this. During runtime, GlobalKTable will
still consum
