[
https://issues.apache.org/jira/browse/KAFKA-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341677#comment-16341677
]
Matthias J. Sax commented on KAFKA-6451:
----------------------------------------
Thanks for the PR [~tanvijaywant31]. Just wanted to point out, that this JIRA
is assigned to [~sssanthalingam] – it would have been better to first leave a
comment and ask if you can take it over from [~sssanthalingam].
[~sssanthalingam]: is it ok for you, to reassign the JIRA to [~tanvijaywant31]
or do you insist in working on it? Would be great if you two could fnd an
agreement. Thanks a lot.
> Simplify KStreamReduce
> ----------------------
>
> Key: KAFKA-6451
> URL: https://issues.apache.org/jira/browse/KAFKA-6451
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
> Assignee: siva santhalingam
> Priority: Minor
> Labels: beginner, newbie
>
> If we do aggregations, we drop records with {{key=null}} or {{value=null}}.
> However, in {{KStreamReduce}} we only early exit if {{key=null}} and process
> {{value=null}} – even if we only update the state with it's old value and
> also only send the old value downstream (ie, we still compute the correct
> result), it's undesired and wasteful and we should early exit on
> {{value=null}}, too.
> This problem might occur for {{KStreamAggregate}} or other processors, too,
> and we need to double check those to make sure we implement consistent
> behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
