kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-5836) Kafka Streams - API for specifying internal stream name on join
Date Wed, 18 Oct 2017 20:22:00 GMT

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

Guozhang Wang commented on KAFKA-5836:
--------------------------------------

[~andy.chambers@fundingcircle.com] Ah I understands now. I think I agree with you that this
scenario can falls into this JIRA.

To unblock your use case, could you specify the join operator of topic c and d after the join
operator of a and b in your code constructing the topology with builder?. I think by doing
this the index of the storeName will be assigned with a larger value to get you around this
issue (in the near term).

> 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)

Mime
View raw message