Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-6451

Simplify KStreamReduce

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0.0
    • Fix Version/s: 1.1.0
    • Component/s: streams
    • Labels:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                tanvijaywant31 Tanvi Jaywant
                Reporter:
                mjsax Matthias J. Sax
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: