I guess this topic is created by Kafka Streams.
Kafka Streams has it's own topic creation(zookeeper node creation)
implementation and not using core's AdminUtils to create internal use
topics such as XX-changelog:
https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/str
HI Javier,
Not sure but just wondering if this could be related to your case:
https://issues.apache.org/jira/browse/KAFKA-4024?focusedCommentId=15458639&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15458639
Are you sure that metadata expiration is exactly the trigg
r");
}
for (Foo foo : event.getFoos()) {
context.forward(key, buildMessage(meta, foo), "FooProcessor");
}
}
...
}
```
> Guozhang
>
> On Sun, Apr 3, 2016 at 9:29 AM, Yuto KAWAMURA
> wrote:
>
>> Hi Guozhang,
>>
>>
>&g
.map((key, value) -> processor.process(key, value)
/* => KeyValueWithDestination */)
.branch(predicates);
for (int i = 0; i < branches.length; i++) {
branches[i].to(destTopics[i]);
}
```
> Guozhang
>
> On Fri, Apr 1, 2016 at 1:20 AM, Yuto KAWAMURA
> wrote:
>
>
When I tried to implement a task which does kinda dispatching to
downstream processors or sinks, looks like relying on
context.forward(K, V, int childIndex) is the only way now.
I have a question why this method implemented using childIndex(which
is just an index of children "List" that based on or
