Dear all,
Kafka consumer has exposed join rate metric from
consumer-coordinator-metrics. I'm wondering if there a possibility to
expose it on the broker side? As descriptions say join group rebalance is a
signal of unhealthy consumption and it's hard to get this from the client
side.
join-rateThe
Hello Matthias,
thank you for the explanation.
Streaming back to a topic and consuming this as a KTable does respect the null
values as deletes, correct? But at the price of some overhead.
Is there any (historical, technical or emotional;-)) reason that no simple
one-step stream-to-table operatio
We can't disable time-based indexing. What is the issue you are facing?
On Thu, Oct 25, 2018 at 6:04 PM Ashwin Sinha
wrote:
> Hi Users,
>
> How to turn off time-based index files in Kafka (.timeindex files). Tried
> searching for it in topic and broker configs documentation but could not
> find
Hi Patrik,
Just to drop one observation in... Streaming to a topic and then consuming
it as a table does create overhead, but so does reducing a stream to a
table, and I think it's actually the same in either case.
They both require a store to collect the table state, and in both cases,
the store
Hi,
What is the email address, if I want to add ServiceNow to the powered by
page?
-Rohan
Hi Pradeep
The poll , pause and resume need to happen in the same thread -- in the
same while loop.
If a scheduler is the trigger for pause or resume, do not call pause
/resume from the scheduler thread. Instead set a
variable in the class that has the poll loop. The poll loop can check the
varia
I don't know your overall application setup. However, a KStream
semantically models immutable facts and there is not update semantic.
Thus, it seems semantically questionable, to allow changing the
semantics from facts to updates (the other way is easier IMHO, and thus
supported via KTable#toStream
