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

2020-06-20 Thread Dennis Jaheruddin (Jira)


[ 
https://issues.apache.org/jira/browse/NIFI-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


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

2017-07-28 Thread Milan Baran (JIRA)

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

Milan Baran commented on NIFI-2903:
---

[~joewitt] Acctually, I've used ConsumerKafka from beginning and I did not 
realize this bug is about GetKafka until now. Well, I just fixed it in 
KafkaConsumer processor form 0.10.* version and I can make pull request, but 
unfortunately I lost my GPG key from Apache foundation. Is it still needed 
these days to contribute to a Apache project?

> 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)


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

2017-07-27 Thread Joseph Witt (JIRA)

[ 
https://issues.apache.org/jira/browse/NIFI-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


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

2017-07-27 Thread Milan Baran (JIRA)

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

Milan Baran commented on NIFI-2903:
---

Any progress?

> 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)


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

2016-10-17 Thread Mark Payne (JIRA)

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

Mark Payne commented on NIFI-2903:
--

Excellent. I would be happy to review a PR if you submit one.

> 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.3.4#6332)


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

2016-10-17 Thread Kurt Hung (JIRA)

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

Kurt Hung commented on NIFI-2903:
-

[~markap14] Agree, to send an empty FlowFile is a better solution, since a null 
value is a valid message for Kafka protocol but not an error.
Sure, I'm interested in NiFi, it helps me develop my projects in a short time.

> 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.3.4#6332)


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

2016-10-17 Thread Mark Payne (JIRA)

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

Mark Payne commented on NIFI-2903:
--

[~kurthung1224] This is a good find. I think that rather than sending to a 
'failure' relationship the FlowFile should still go to the 'success' 
relationship. The FlowFile would just have no content, but it would have the 
appropriate attribute for the message key. Do you agree? Is this something that 
you're interested in tackling & contributing back to the community?

> 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.3.4#6332)