[jira] [Created] (KAFKA-3817) KTableRepartitionMap should handle null inputs

["Jeff Klukas (JIRA)" <ji...@apache.org>]

Jeff Klukas created KAFKA-3817:
----------------------------------

             Summary: KTableRepartitionMap should handle null inputs
                 Key: KAFKA-3817
                 URL: https://issues.apache.org/jira/browse/KAFKA-3817
             Project: Kafka
          Issue Type: Bug
          Components: streams
    Affects Versions: 0.10.0.0
            Reporter: Jeff Klukas
            Assignee: Guozhang Wang
             Fix For: 0.10.0.1


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] 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)