[
https://issues.apache.org/jira/browse/KAFKA-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177620#comment-15177620
]
ASF GitHub Bot commented on KAFKA-3324:
---------------------------------------
GitHub user miguno opened a pull request:
https://github.com/apache/kafka/pull/1001
KAFKA-3324: NullPointerException in StreamPartitionAssignor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/miguno/kafka KAFKA-3324
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1001.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1001
----
commit fb21a1bc4ecf36a35ecc142d885acb11ca373196
Author: Michael G. Noll <mich...@confluent.io>
Date: 2016-03-03T10:22:47Z
KAFKA-3324: NullPointerException in StreamPartitionAssignor (Kafka Streams)
----
> NullPointerException in StreamPartitionAssignor (Kafka Streams)
> ---------------------------------------------------------------
>
> Key: KAFKA-3324
> URL: https://issues.apache.org/jira/browse/KAFKA-3324
> Project: Kafka
> Issue Type: Bug
> Components: kafka streams
> Affects Versions: 0.10.0.0
> Reporter: Michael Noll
>
> KAFKA-3311 changed
> {{streams/src/main/java/org/apache/kafka/streams/processor/internals/StreamPartitionAssignor.java}},
> which unfortunately triggers NPEs consistently at this line:
> {code}
> for (Map.Entry<String, Set<TaskId>> entry :
> internalSourceTopicToTaskIds.entrySet()) {
> {code}
> The naive bug fix -- a simple null check -- seems to resolve the problem. PR
> incoming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
