[
https://issues.apache.org/jira/browse/NIFI-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333775#comment-14333775
]
ASF subversion and git services commented on NIFI-333:
------------------------------------------------------
Commit c8810c04d8dcb6823c7e59e85158a0c3cb18675f in incubator-nifi's branch
refs/heads/develop from [~danbress]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=c8810c0 ]
NIFI-333 - Removing exception handling in SegmentContent
>From Mark - 'Theres no exception that could get thrown in there unless
theres something weird - in which case the framework should catch it and
handle it'
> Some Processors catch java.land.Exception and route to 'failure', instead of
> catching ProcessException
> ------------------------------------------------------------------------------------------------------
>
> Key: NIFI-333
> URL: https://issues.apache.org/jira/browse/NIFI-333
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Daniel Ueberfluss
>
> The consequence of this is that if the framework throws a
> FlowFileAccessException, for example, the Processor is catching that and then
> routing to failure, when the framework should be able to catch it and roll
> back the ProcessSession. Specifically, we are seeing this because on of the
> content repository containers ran out of disk space and files were then
> routed to 'failure'. Instead, the session should have been rolled back and
> the FlowFile processed again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
