kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6273) Allow names for windowing joins
Date Mon, 27 Nov 2017 19:16:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267292#comment-16267292

Matthias J. Sax commented on KAFKA-6273:

Thanks for the JIRA. All public API changes require a KIP, https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

> Allow names for windowing joins
> -------------------------------
>                 Key: KAFKA-6273
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6273
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 1.0.0
>            Reporter: Matthias
>              Labels: needs-kip
> Currently, the internal name of a windowing join is generated at runtime using a counter
to ensure uniqueness within a running topology. 
> If a topology is changed and redeployed, different names can be generated for the same
window. This can result in lost windowing state without intervention modifying offsets to
re-consume the input topics.
> https://kafka.apache.org/10/javadoc/org/apache/kafka/streams/kstream/Joined.html
> The proposed change would be to add an optional configuration parameter "joinName" to
Joined. If provided, this would be used by KStreamImpl to generate internal names when building
a join. If not provided the existing name generation would be used. (Since this is an opt-in,
optional parameter there would be no impact on existing code.)
> Let me know if this should be a KIP instead. The change would be something along [these

This message was sent by Atlassian JIRA

View raw message