kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3817) KTableRepartitionMap should handle null inputs
Date Fri, 08 Jul 2016 15:37:11 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367817#comment-15367817

ASF GitHub Bot commented on KAFKA-3817:

Github user asfgit closed the pull request at:


> 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:
>            Reporter: Jeff Klukas
>            Assignee: Guozhang Wang
>             Fix For:
> 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

View raw message