You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Nissim Shiman (Jira)" <ji...@apache.org> on 2020/03/04 17:46:00 UTC

[jira] [Created] (NIFI-7225) FetchSFTP processor: "routing to not.found" error given when Private Key Path property is invalid

Nissim Shiman created NIFI-7225:
-----------------------------------

             Summary: 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.11.3, 1.10.0
            Reporter: Nissim Shiman


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)