[jira] [Assigned] (NIFI-12930) FetchFile on failure during StandardProcessSession.importFrom should route to failure instead of rollback

2024-03-25 Thread Joe Witt (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Witt reassigned NIFI-12930:
---

Assignee: Joe Witt  (was: Jim Steinebrey)

> 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] [Assigned] (NIFI-12930) FetchFile on failure during StandardProcessSession.importFrom should route to failure instead of rollback

2024-03-25 Thread Jim Steinebrey (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jim Steinebrey reassigned NIFI-12930:
-

Assignee: Jim Steinebrey

> 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: Jim Steinebrey
>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)