[
https://issues.apache.org/jira/browse/KAFKA-7748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317483#comment-17317483
]
Chris Osborn commented on KAFKA-7748:
-------------------------------------
This feature would be helpful for nightly batch processing aggregation use
cases. Does anyone have a working example of how they have worked around this
problem?
> Add wall clock TimeDefinition for suppression of intermediate events
> --------------------------------------------------------------------
>
> Key: KAFKA-7748
> URL: https://issues.apache.org/jira/browse/KAFKA-7748
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Affects Versions: 2.1.0
> Reporter: Jonathan Gordon
> Priority: Major
> Labels: needs-kip
>
> Currently, Kafka Streams offers the ability to suppress intermediate events
> based on either RecordTime or WindowEndTime, which are in turn defined by
> stream time:
> {{Suppressed.untilTimeLimit(final Duration timeToWaitForMoreEvents, final
> BufferConfig bufferConfig)}}
> It would be helpful to have another option that would allow suppression of
> intermediate events based on wall clock time. This would allow us to only
> produce a limited number of aggregates independent of their stream time
> (which in our case is event time).
> For reference, here's the relevant KIP:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-328%3A+Ability+to+suppress+updates+for+KTables#KIP-328:AbilitytosuppressupdatesforKTables-Best-effortratelimitperkey]
> And here's the relevant Confluent Slack thread:
> https://confluentcommunity.slack.com/archives/C48AHTCUQ/p1544468349201700
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
