You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Dennis Jaheruddin (Jira)" <ji...@apache.org> on 2020/06/21 00:06:00 UTC

[jira] [Commented] (NIFI-2903) GetKafka cannot handle null value in Kafka offset cause NullPointerException

    [ https://issues.apache.org/jira/browse/NIFI-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141238#comment-17141238 ] 

Dennis Jaheruddin commented on NIFI-2903:
-----------------------------------------

Recommending to close this as the linked issue indicates it is resolved in ConsumeKafka, and recent versions of Nifi do not even ship GetKafka anymore.

> 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
>            Priority: Major
>
> 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
(v8.3.4#803005)