[jira] [Commented] (NIFI-12930) FetchFile on failure during StandardProcessSession.importFrom should route to failure instead of rollback
[ https://issues.apache.org/jira/browse/NIFI-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830755#comment-17830755 ] ASF subversion and git services commented on NIFI-12930: Commit 1e78a66a44135191c73ac726c5e424113d9fbfaa in nifi's branch refs/heads/support/nifi-1.x from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1e78a66a44 ] NIFI-12930 Catch FlowFileAccessException in FetchFile when importing a fetched file we cannot be sure if the problem is reading the source file or writing to the content repository. So we need to route to failure to allow flow designers to choose how to handle this. This closes #8542 Signed-off-by: David Handermann (cherry picked from commit d5ff51b6e4ee6907057b0838f627542f64b9f686) > FetchFile on failure during StandardProcessSession.importFrom should route to > failure instead of rollback > - > > Key: NIFI-12930 > URL: https://issues.apache.org/jira/browse/NIFI-12930 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Consider a scenario involving corrupt files on a disk. > FetchFile during the importFrom call can fail in such cases as would any > process. But the current handling calls rollback instead of routing to > failure. As a result the flow could be stuck in an endless loop trying the > same objects over and over and not giving the flow designer a chance to > reasonably handle such cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12930) FetchFile on failure during StandardProcessSession.importFrom should route to failure instead of rollback
[ https://issues.apache.org/jira/browse/NIFI-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830754#comment-17830754 ] ASF subversion and git services commented on NIFI-12930: Commit d5ff51b6e4ee6907057b0838f627542f64b9f686 in nifi's branch refs/heads/main from Joe Witt [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d5ff51b6e4 ] NIFI-12930 Catch FlowFileAccessException in FetchFile when importing a fetched file we cannot be sure if the problem is reading the source file or writing to the content repository. So we need to route to failure to allow flow designers to choose how to handle this. This closes #8542 Signed-off-by: David Handermann > FetchFile on failure during StandardProcessSession.importFrom should route to > failure instead of rollback > - > > Key: NIFI-12930 > URL: https://issues.apache.org/jira/browse/NIFI-12930 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Consider a scenario involving corrupt files on a disk. > FetchFile during the importFrom call can fail in such cases as would any > process. But the current handling calls rollback instead of routing to > failure. As a result the flow could be stuck in an endless loop trying the > same objects over and over and not giving the flow designer a chance to > reasonably handle such cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12930) FetchFile on failure during StandardProcessSession.importFrom should route to failure instead of rollback
[ https://issues.apache.org/jira/browse/NIFI-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830717#comment-17830717 ] Jim Steinebrey commented on NIFI-12930: --- No problem. Thx > FetchFile on failure during StandardProcessSession.importFrom should route to > failure instead of rollback > - > > Key: NIFI-12930 > URL: https://issues.apache.org/jira/browse/NIFI-12930 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Consider a scenario involving corrupt files on a disk. > FetchFile during the importFrom call can fail in such cases as would any > process. But the current handling calls rollback instead of routing to > failure. As a result the flow could be stuck in an endless loop trying the > same objects over and over and not giving the flow designer a chance to > reasonably handle such cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12930) FetchFile on failure during StandardProcessSession.importFrom should route to failure instead of rollback
[ https://issues.apache.org/jira/browse/NIFI-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17830716#comment-17830716 ] Joe Witt commented on NIFI-12930: - [~jrsteinebrey]I have it assigned to me as there is already a PR that addresses it. Thanks > FetchFile on failure during StandardProcessSession.importFrom should route to > failure instead of rollback > - > > Key: NIFI-12930 > URL: https://issues.apache.org/jira/browse/NIFI-12930 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Joe Witt >Assignee: Joe Witt >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Consider a scenario involving corrupt files on a disk. > FetchFile during the importFrom call can fail in such cases as would any > process. But the current handling calls rollback instead of routing to > failure. As a result the flow could be stuck in an endless loop trying the > same objects over and over and not giving the flow designer a chance to > reasonably handle such cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
