[
https://issues.apache.org/jira/browse/KAFKA-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521243#comment-17521243
]
Matthias J. Sax commented on KAFKA-13813:
-----------------------------------------
The change is intentionally, as users wanted to get SQL join semantics, while
the old behavior is different to SQL semantics.
Currently, you can still use the old API to get the old behavior. If we want to
keep the old behavior, we need to find a way to give users control over it. –
If we do this, we should do it before we remove the old and already deprecated
API.
Seems, we might need a KIP for this. – While un-deprecating the old API might
be the simplest way, it seems hard to reason for users (ie, understand the
difference between both – would be very subtle), thus, designing something new
and more explicit might be a better way forward?
> left/outer joins can wait indefinitely for emitted record with suprious
> record fix
> ----------------------------------------------------------------------------------
>
> Key: KAFKA-13813
> URL: https://issues.apache.org/jira/browse/KAFKA-13813
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Clive Cox
> Priority: Major
>
> With the fix in https://issues.apache.org/jira/browse/KAFKA-10847 records
> will be emitted after the grace period but only when a new record is
> processed. This means its possible to wait for arbitrary long time for a
> record to be emitted.
> This also means one can not recreate the previous semantics of emitting
> immediately records or even now guaranteed emitting after the grace period.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
