[ https://issues.apache.org/jira/browse/KAFKA-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818443#comment-16818443 ]
Matthias J. Sax commented on KAFKA-8236: ---------------------------------------- Not 100% sure if this needs a KIP. > Incorporate version control for Kafka Streams Application Reset > --------------------------------------------------------------- > > Key: KAFKA-8236 > URL: https://issues.apache.org/jira/browse/KAFKA-8236 > Project: Kafka > Issue Type: Improvement > Components: streams, tools > Reporter: Boyang Chen > Priority: Minor > Labels: needs-kip > > Inspired by Spark mlflow which supports versioning log, we should be > considering expose a special versioning tag for KStream applications to easy > rollback bad code deploy. The naive approach is to store the versioning info > in consumer offset topic so that when we perform rollback, we know where to > read from the input, and where to cleanup the changelog topic. Essentially, > this is an extension to our current application reset tool. -- This message was sent by Atlassian JIRA (v7.6.3#76005)