[
https://issues.apache.org/jira/browse/NIFI-9990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534407#comment-17534407
]
David Handermann commented on NIFI-9990:
----------------------------------------
Thanks for reporting this issue [~jmkofoed]. The FTP 550 reply code indicates
that the file is unavailable for some reason, but does not provide the specific
reason. The current file-not-found handling uses a specific message string
search, and otherwise throws a general {{IOException}} as you have observed. I
submitted a pull request to make the not-found detection more flexible, which
should improve the behavior.
> FetchFTP routing "File not found" to comms.failure NOT to "fileNotFound"
> ------------------------------------------------------------------------
>
> Key: NIFI-9990
> URL: https://issues.apache.org/jira/browse/NIFI-9990
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.16.1
> Reporter: Jens M Kofoed
> Assignee: David Handermann
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> FetchFTP does not route "file not found" to the correct relationship (
> "not.found")
> FetchFTP[id=5044bc51-71c2-37ed-9d7d-5d21b2e74f21] Failed to fetch content for
> FlowFile[filename=filename.txt] from filename ./filename.txt on remote host
> myserver:21 due to java.io.IOException: 550 File not found
> ; {*}+{color:#172b4d}routing to comms.failure{color}+{*}:
> java.io.IOException: 550 File not found
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
