You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2021/01/04 18:43:00 UTC
[jira] [Updated] (NIFI-7225) FetchSFTP processor: "routing to
not.found" error given when Private Key Path property is invalid
[ https://issues.apache.org/jira/browse/NIFI-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-7225:
-----------------------------
Fix Version/s: 1.13.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> FetchSFTP processor: "routing to not.found" error given when Private Key Path property is invalid
> -------------------------------------------------------------------------------------------------
>
> Key: NIFI-7225
> URL: https://issues.apache.org/jira/browse/NIFI-7225
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.10.0, 1.11.3
> Reporter: Nissim Shiman
> Assignee: Tim Smith
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> In apache nifi 1.8.0, for the FetchSFTP processor, if the "Private Key Path" property was a directory, this would be flagged immediately as a configuration issue.
> In apache 1.10 (and later) a directory is an acceptable value here, but then on runtime, the "not.found" relationship is hit, even though the remote file exists.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)