[ 
https://issues.apache.org/jira/browse/KAFKA-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on KAFKA-2872 stopped by Bill Bejeck.
------------------------------------------
> Error starting KafkaStream caused by sink not being connected to parent 
> source/processor nodes
> ----------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-2872
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2872
>             Project: Kafka
>          Issue Type: Bug
>          Components: kafka streams
>    Affects Versions: 0.9.0.0
>            Reporter: Bill Bejeck
>            Assignee: Bill Bejeck
>
> When starting the KafkaStream I get the following Exception:
> Exception in thread "main" java.util.NoSuchElementException: id: SINK
>       at 
> org.apache.kafka.streams.processor.internals.QuickUnion.root(QuickUnion.java:40)
>       at 
> org.apache.kafka.streams.processor.TopologyBuilder.makeNodeGroups(TopologyBuilder.java:387)
>       at 
> org.apache.kafka.streams.processor.TopologyBuilder.topicGroups(TopologyBuilder.java:339)
>       at 
> org.apache.kafka.streams.processor.internals.StreamThread.<init>(StreamThread.java:139)
>       at 
> org.apache.kafka.streams.processor.internals.StreamThread.<init>(StreamThread.java:120)
>       at 
> org.apache.kafka.streams.KafkaStreaming.<init>(KafkaStreaming.java:110)
>       at bbejeck.ProcessorDriver.main(ProcessorDriver.java:35)
> The TopologyBuilder is being built like so:
> topologyBuilder.addSource("SOURCE", new StringDeserializer(), new 
> StringDeserializer(), "src-topic")
>                 .addProcessor("PROCESS", new 
> GenericProcessorClient(replaceVowels), "SOURCE")
>                 .addSink("SINK", "dest-topic", new StringSerializer(), new 
> StringSerializer(), "PROCESS");
> Looks to me the cause of the error is that in  TopologyBuilder.addSink method 
> the sink  is never connected with it's parent.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to