[
https://issues.apache.org/jira/browse/NIFI-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992914#comment-16992914
]
ASF subversion and git services commented on NIFI-6924:
-------------------------------------------------------
Commit 452ca98c29eeda6a89c60350e4577f82138d7ef0 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=452ca98 ]
NIFI-6924: When seeking to the appropriate offset for a content claim, ensure
that if there are not enough bytes in the underlying resource claim that a
ContentNotFoundException is thrown. Also cleaned up error-handling case in
StandardProcessSession to ensure that we close the existing InputStream before
calling handleContenttNotFoundException, since this method may itself throw an
Exception
This closes #3924.
Signed-off-by: Bryan Bende <[email protected]>
> If content is missing from ContentRepository but the Resource Claim exists,
> ContentNotFoundException is not being thrown
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6924
> URL: https://issues.apache.org/jira/browse/NIFI-6924
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the `read(ContentClaim)` method of FileSystemRepository is called, it
> ensures that the File exists on disks. It then skips to the appropriate
> offset. However, if the Resource Claim does not contain enough content, an
> EOFException is thrown instead of a ContentNotFoundException.
> As a result, the FlowFile is not cleaned up from the system but instead is
> rolled back into its original FlowFile Queue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
