You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/12/08 21:13:00 UTC
[jira] [Commented] (NIFI-4680) Improve error handling in
Publish/Consume Kafka processors
[ https://issues.apache.org/jira/browse/NIFI-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284212#comment-16284212 ]
ASF subversion and git services commented on NIFI-4680:
-------------------------------------------------------
Commit c138987bb46b975379daa00e57c42f498b6ef207 in nifi's branch refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=c138987 ]
NIFI-4656, NIFI-4680: This closes #2330. Fix error handling in consume/publish kafka processors. Address issue with HortonworksSchemaRegistry throwing RuntimeException when it should be IOException. Fixed bug in ConsumeerLease/ConsumKafkaRecord that caused it to report too many records received
Signed-off-by: joewitt <jo...@apache.org>
> Improve error handling in Publish/Consume Kafka processors
> ----------------------------------------------------------
>
> Key: NIFI-4680
> URL: https://issues.apache.org/jira/browse/NIFI-4680
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.5.0
>
>
> While reviewing NIFI-4639, I encountered a couple of issues surrounding how NiFi handles errors in the Publish and Consume Kafka processors.
> If interacting with the Hortonworks Schema Registry and unable to connect to it, the Exception that was thrown was a RuntimeException instead of an IOException. This resulted in ConsumeKafkaRecord continuing to try to parse every record it received. This could cause it to take a very long time to stop the processor in such a case.
> On the publisher side if this happened, some flowfiles were transferred back to their original queues and then attempted to transfer to failure. As a result, the session would rollback instead of transferring anything to failure, and an error message would indicate that flowfile was already transferred.
> When attempting to rollback consumed records, a NPE was thrown if reading from the beginning of the topic (no offsets had been committed).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)