[
https://issues.apache.org/jira/browse/KAFKA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318939#comment-16318939
]
Dmitry Minkovsky edited comment on KAFKA-2984 at 1/9/18 6:56 PM:
-----------------------------------------------------------------
I was thinking something like
https://groups.google.com/d/msg/confluent-platform/jOr7pW4qH_A/rnYRph3oCAAJ,
but I guess that's not related to these internals.
Out of curiosity, what did you mean in that reply by:
> One thing you need to keep in mind, is out-of-order data. Thus, you should
> also check the offset of the currently processed record via the
provided context from init().
Why would the processor receive data out-of-order if it's working a single
partition?
was (Author: dminkovsky):
I was thinking something like
https://groups.google.com/d/msg/confluent-platform/jOr7pW4qH_A/rnYRph3oCAAJ,
but I guess that's not related to these internals.
> KTable should send old values along with new values to downstreams
> ------------------------------------------------------------------
>
> Key: KAFKA-2984
> URL: https://issues.apache.org/jira/browse/KAFKA-2984
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Affects Versions: 0.10.0.0
> Reporter: Yasuhiro Matsuda
> Assignee: Yasuhiro Matsuda
> Fix For: 0.10.0.0
>
>
> Old values are necessary for implementing aggregate functions. KTable should
> augment an event with its old value. Basically KTable stream is a stream of
> (key, (new value, old value)) internally. The old value may be omitted when
> it is not used in the topology.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
