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

KTableRepartitionMap should handle null inputs

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.10.0.0
    • Fix Version/s: 0.10.0.1
    • Component/s: streams
    • Labels:
      None

      Description

      When calling KTable.groupBy on the result of a KTable-KTable join, NPEs are raised:

      {{org.apache.kafka.streams.kstream.internals.KTableRepartitionMap$
      > KTableMapProcessor.process(KTableRepartitionMap.java:88)}}

      The root cause is that the join is expected to emit null values when no match is found, but KTableRepartitionMap is not set up to handle this case.

      On the users email list, Guozhang Wang described a plan of action:

      I think this is actually a bug in KTableRepartitionMap
      that it actually should expect null grouped keys; this would be a
      straight-forward fix for this operator, but I can make a pass over all the
      repartition operators just to make sure they are all gracefully handling
      null keys.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                guozhang Guozhang Wang
                Reporter:
                jeff.klukas@gmail.com Jeff Klukas
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: