kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthias J. Sax (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KAFKA-6451) Simplify KStreamReduce
Date Fri, 26 Jan 2018 22:56:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matthias J. Sax reassigned KAFKA-6451:

    Assignee: Tanvi Jaywant

> 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: Tanvi Jaywant
>            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

View raw message