[
https://issues.apache.org/jira/browse/KAFKA-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103420#comment-17103420
]
John Roesler commented on KAFKA-7224:
-------------------------------------
Hi Maatari,
Yeah, it probably seems beside the point because it is beside the point. I
probably shouldn’t have mentioned it. I guess I was just thinking that when the
general problem is “I get too many updates in the output”, some of those are
idempotent, while others are non-idempotent. If we eliminate the idempotent
updates, then maybe the number of updates on the output side drops below the
“too many” threshold and the problem goes away.
Of course, if you want a guarantee, such as a rate limit or that you don’t emit
_any_ result until some specific time, then of course you need something with
those semantics, which is orthogonal to whether there are idempotent updates or
not.
> KIP-328: Add spill-to-disk for Suppression
> ------------------------------------------
>
> Key: KAFKA-7224
> URL: https://issues.apache.org/jira/browse/KAFKA-7224
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: John Roesler
> Priority: Major
>
> As described in
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-328%3A+Ability+to+suppress+updates+for+KTables]
> Following on KAFKA-7223, implement the spill-to-disk buffering strategy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
