[jira] [Updated] (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 ] Matthias J. Sax updated KAFKA-3430: --- Affects Version/s: 0.10.0.0 > 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 >Affects Versions: 0.10.0.0 >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.15#6346)
[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3430: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1222 [https://github.com/apache/kafka/pull/1222] > 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)
[jira] [Updated] (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 ] Bill Bejeck updated KAFKA-3430: --- Status: Patch Available (was: Open) Submitted PR for KAFKA-3430 Allow users to set key in KTable.toStream and in KStream. With KStream the method selectKey was added to enable getting a key from values before perfoming aggregation-by-key operations on original streams that have null keys. > 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)
[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3430: - Labels: api (was: ) > 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: kafka streams >Reporter: Guozhang Wang > 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)
[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3430: - Fix Version/s: (was: 0.10.0.1) 0.10.0.0 > 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: kafka streams >Reporter: Guozhang Wang > 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)
[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3430: - Component/s: kafka streams > 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: kafka streams >Reporter: Guozhang Wang > Fix For: 0.10.0.1 > > > 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)
[jira] [Updated] (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 ] Guozhang Wang updated KAFKA-3430: - Description: 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} was: 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, value){code} > 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 >Reporter: Guozhang Wang > Fix For: 0.10.0.1 > > > 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)