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

Posted to jira@kafka.apache.org by "Bill Bejeck (Jira)" <ji...@apache.org> on 2020/04/04 15:48:00 UTC

[jira] [Comment Edited] (KAFKA-9739) StreamsBuilder.build fails with StreamsException "Found a null keyChangingChild node for OptimizableRepartitionNode"

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

Bill Bejeck edited comment on KAFKA-9739 at 4/4/20, 3:47 PM:
-------------------------------------------------------------

merged to 2.4 via [https://github.com/apache/kafka/pull/8416]


was (Author: bbejeck):
cherry-picked to 2.4 via [https://github.com/apache/kafka/pull/8416]

> StreamsBuilder.build fails with StreamsException "Found a null keyChangingChild node for OptimizableRepartitionNode"
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9739
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9739
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.3.0, 2.4.0, 2.4.1
>            Reporter: Artur Poliachenko
>            Assignee: Bill Bejeck
>            Priority: Major
>             Fix For: 2.3.2, 2.6.0, 2.4.2, 2.5.1
>
>         Attachments: streams-exception-log.txt, topology-definition-fragment.java, topology-description.txt
>
>
> We created a topology using Streams DSL (topology description is available in the attached topology-description.txt, no optimization).
> Topology works fine with {{topology.optimization=none}}, however it fails to build with StreamsException "Found a null keyChangingChild node for OptimizableRepartitionNode" if we set {{topology.optimization=all}} (exception stack trace is attached streams-exception-log.txt).
> We used [https://zz85.github.io/kafka-streams-viz/] to visualize topology and try to guess what might be upsetting optimizer, yet did not manage to figure it out ourselves.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)