[
https://issues.apache.org/jira/browse/KAFKA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208523#comment-16208523
]
Andy Chambers commented on KAFKA-5836:
--------------------------------------
Agree that bumping the application id would resolve the issue by creating
completely new internal topics. But v2 isn't really "changing" the input
topics. It is reading two new topics (c and d) and processing those
independently of the original a and b. The required processing on a and b
remains the same and the state that has been built up remains valid and might
take quite a while to build from scratch if you're using kafka as an event log.
> Kafka Streams - API for specifying internal stream name on join
> ---------------------------------------------------------------
>
> Key: KAFKA-5836
> URL: https://issues.apache.org/jira/browse/KAFKA-5836
> Project: Kafka
> Issue Type: New Feature
> Components: streams
> Affects Versions: 0.11.0.0
> Reporter: Lovro Pandžić
> Labels: api, needs-kip
>
> Automatic topic name can be problematic in case of streams operation
> change/migration.
> I'd like to be able to specify name of an internal topic so I can avoid
> creation of new stream and data "loss" when changing the Stream building.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
