[
https://issues.apache.org/jira/browse/KAFKA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196241#comment-16196241
]
Andy Chambers commented on KAFKA-5836:
--------------------------------------
We're using the confluent schema registry. It is my understanding that if you
have schema "a" at position "n" in the topology, and schema b at position
"n+1", and then you add a node into the topology before the one using schema
"a", then KS will try to register a as a new version of subject b.
> 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)
