[
https://issues.apache.org/jira/browse/NIFI-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103188#comment-16103188
]
Joseph Witt commented on NIFI-2903:
-----------------------------------
[~milan.baran] does not look like there has been a contribution for this issue
yet. However, I strongly recommend using the ConsumeKafka processors instead.
They are more efficient and better designed. Not sure if this null issue
exists (or even how such a thing could be null) but consider that if an option
for you.
> GetKafka cannot handle null value in Kafka offset cause NullPointerException
> ----------------------------------------------------------------------------
>
> Key: NIFI-2903
> URL: https://issues.apache.org/jira/browse/NIFI-2903
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0, 0.7.0
> Reporter: Kurt Hung
>
> The GetKafka processor does not handle the condition of null value that
> exists in Kafka offset, which would cause the processor hang on and generate
> a NullPointerException after 30 sec. It's easy to reproduce this issue; I use
> the kafka-python to insert a key-value pair ("abc", None), and create a
> GetKafka processor to consume the topic I've created. This issue would happen
> immediately, and moreover, the processor could't consume rest offsets.
> Temporary I customize a GetKafka processor for a "Failure" relationship to
> handle null values exist in Kafka offset to prevent this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
