[jira] [Updated] (KAFKA-3576) Unify KStream and KTable API
[
https://issues.apache.org/jira/browse/KAFKA-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-3576:
-
Assignee: Damian Guy (was: Guozhang Wang)
> Unify KStream and KTable API
>
>
> Key: KAFKA-3576
> URL: https://issues.apache.org/jira/browse/KAFKA-3576
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
>Reporter: Matthias J. Sax
>Assignee: Damian Guy
> Labels: api
> Fix For: 0.10.1.0
>
>
> For KTable aggregations, it has a pattern of
> {{table.groupBy(...).aggregate(...)}}, and the data is repartitioned in an
> inner topic based on the selected key in {{groupBy(...)}}.
> For KStream aggregations, though, it has a pattern of
> {{stream.selectKey(...).through(...).aggregateByKey(...)}}. In other words,
> users need to manually use a topic to repartition data, and the syntax is a
> bit different with KTable as well.
> h2. Goal
> To have similar APIs for aggregations of KStream and KTable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-3576) Unify KStream and KTable API
[
https://issues.apache.org/jira/browse/KAFKA-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang updated KAFKA-3576:
-
Description:
For KTable aggregations, it has a pattern of
{{table.groupBy(...).aggregate(...)}}, and the data is repartitioned in an
inner topic based on the selected key in {{groupBy(...)}}.
For KStream aggregations, though, it has a pattern of
{{stream.selectKey(...).through(...).aggregateByKey(...)}}. In other words,
users need to manually use a topic to repartition data, and the syntax is a bit
different with KTable as well.
.h2 Goal
To have similar APIs for aggregations of KStream and KTable
> Unify KStream and KTable API
>
>
> Key: KAFKA-3576
> URL: https://issues.apache.org/jira/browse/KAFKA-3576
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
>Reporter: Matthias J. Sax
>Assignee: Guozhang Wang
> Labels: api
> Fix For: 0.10.1.0
>
>
> For KTable aggregations, it has a pattern of
> {{table.groupBy(...).aggregate(...)}}, and the data is repartitioned in an
> inner topic based on the selected key in {{groupBy(...)}}.
> For KStream aggregations, though, it has a pattern of
> {{stream.selectKey(...).through(...).aggregateByKey(...)}}. In other words,
> users need to manually use a topic to repartition data, and the syntax is a
> bit different with KTable as well.
> .h2 Goal
> To have similar APIs for aggregations of KStream and KTable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KAFKA-3576) Unify KStream and KTable API
[ https://issues.apache.org/jira/browse/KAFKA-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3576: --- Fix Version/s: 0.10.1.0 > Unify KStream and KTable API > > > Key: KAFKA-3576 > URL: https://issues.apache.org/jira/browse/KAFKA-3576 > Project: Kafka > Issue Type: Sub-task > Components: streams >Reporter: Matthias J. Sax >Assignee: Guozhang Wang > Labels: api > Fix For: 0.10.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
