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/05/12 15:55:12 UTC
[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
was:
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)