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

[jira] [Work stopped] (KAFKA-3430) Allow users to set key in KTable.toStream() and KStream

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

Work on KAFKA-3430 stopped by Bill Bejeck.
------------------------------------------
> Allow users to set key in KTable.toStream() and KStream
> -------------------------------------------------------
>
>                 Key: KAFKA-3430
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3430
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Bill Bejeck
>              Labels: api
>             Fix For: 0.10.0.0
>
>
> Currently KTable.toStream does not take any parameters and hence users who wants to set the key need to do two steps:
> {code}table.toStream().map(...){code} in order to do so. We can make it in one step by providing the mapper parameter in toStream.
> And similarly today users usually need to call {code} KStream.map() {code} in order to select the key before aggregation-by-key operation if the original stream is does not contain keys. 
> We can consider adding a specific function in KStream to do so:
> {code}KStream.selectKey(mapper){code}
> which essential is the same as
> {code}KStream.map(/* mapper that does not change the value, but only the key */){code}



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