You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Kenny Williams (JIRA)" <ji...@apache.org> on 2019/03/27 20:28:00 UTC

[jira] [Commented] (KAFKA-8167) Document named stateful operators

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

Kenny Williams commented on KAFKA-8167:
---------------------------------------

I was looking for this documentation and could not find it. This feature is mentioned in a blog article [here|https://www.confluent.io/blog/kafka-streams-take-on-watermarks-and-triggers]. I was linked to the [KIP|https://cwiki.apache.org/confluence/display/KAFKA/KIP-307%3A+Allow+to+define+custom+processor+names+with+KStreams+DSL] for this feature via a Slack conversation. Examples uses of this feature would be great. 

> Document named stateful operators
> ---------------------------------
>
>                 Key: KAFKA-8167
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8167
>             Project: Kafka
>          Issue Type: Task
>          Components: documentation, streams
>    Affects Versions: 2.1.0, 2.2.0, 2.1.1, 2.3.0, 2.1.2, 2.2.1
>            Reporter: John Roesler
>            Priority: Major
>
> In KIP-372 / KAFKA-7406, we added the ability to name all persistent resources in support of topology compatibility. We missed documenting it, though, or at least, I couldn't find the docs.
>  
> Since this feature is a higher-level, cross-cutting concern, we should add a section to the docs describing the compatibility problem and the full set of practices that you can employ to achieve compatibility by naming persistent resources.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)