You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/04/04 00:22:25 UTC

[jira] [Commented] (KAFKA-3497) Streams ProcessorContext should support forward() based on child name

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

Guozhang Wang commented on KAFKA-3497:
--------------------------------------

Thanks [~kawamuray]. I think we can consider even replacing the "int childIndex" parameter with childname. Migrating to Kafka Streams subtasks.

> Streams ProcessorContext should support forward() based on child name
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-3497
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3497
>             Project: Kafka
>          Issue Type: Improvement
>          Components: kafka streams
>    Affects Versions: 0.10.0.1
>            Reporter: Yuto Kawamura
>
> Currently {{ProcessorContext}} only supports {{forward(K, V)}} which forwards KV to all children and {{forward(K, V, int childIndex)}} which forwards KV to  specific children that is identified by an index of children List.
> While letting a Processor to issue messages which have arbitrary different downstream destination, it is not handy to keep ordering of calling {{addProcessor}}(or {{addSink}}) and childIndex consistent.
> Here I'd like to suggest introducing another signature {{forward(K, V, String childName)}} which allows to use child name(first argument to addProcessor or addSink) to indicate the destination downstream.
> Thread on user mailing list: http://mail-archives.apache.org/mod_mbox/kafka-users/201604.mbox/<CA...@mail.gmail.com>



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