scott wilburn commented on NIFI-4621:
I have also wanted to see this feature for ListSFTP and other List processors
that do not allow an incoming relationship. In my case, I would like to use an
external table to configure NiFi connections. To accomplish this, I would first
read in my configuration, then create flowfiles for each connection that
contains the configuration parameters as attributes. It doesn't work for SFTP
unless it can read attributes from an incoming flowfile to use as configuration
parameters, such as username, directory, etc. I had a conversation with devs in
the dev email distro. The recommendation was to create a new processor which
does not keep state. The incoming flowfile would trigger the list, which would
then generate zero or more output flowfiles, one for each remote file matching.
You should be able to follow the email chain discussion I had in the dev email
archive for subject "ListSFTP incoming relationship". I was thinking about
building a custom processor to do this also before I read your jira.
> Allow inputs to ListSFTP
> Key: NIFI-4621
> URL: https://issues.apache.org/jira/browse/NIFI-4621
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: Soumya Shanta Ghosh
> Assignee: Puspendu Banerjee
> Priority: Critical
> ListSFTP supports listing of the supplied directory (Remote Path)
> out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password"
> / "Private Key Passphrase".
> The password can change at a regular interval (depending on organization
> policy) or the Hostname or the Remote Path can change based on some other
> This is a case to allow ListSFTP to leverage the use of Nifi Expression
> language so that the values of Hostname, Password and/or Remote Path can be
> set based on the attributes of an incoming flow file.
This message was sent by Atlassian JIRA