[jira] [Commented] (NIFI-3560) Improvement needed for all List Processors

["Joseph Witt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898214#comment-15898214 ] 

Joseph Witt commented on NIFI-3560:
-----------------------------------

You mention all List processors are needing to support listing to one or more source systems at once.  Besides ListSFTP what others did you have in mind?

Also, alternatively, why not add 100 ListFTP processors onto the flow to pull data from each source specifically?  Can you describe the downside you see of that approach?  The upsides are it lets you specifically control behavior to a given source, specific scheduling, specific credentials, lifecycle (start/stop).  The downside is that it is "lots of things on the graph" but the alternative is "lots of things in a config file" so I'd like to more fully understand the concern.

Thanks


> Improvement needed for all List Processors
> ------------------------------------------
>
>                 Key: NIFI-3560
>                 URL: https://issues.apache.org/jira/browse/NIFI-3560
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.1.1
>            Reporter: Vamsi Gummalla
>
> Current Implementation of List processor is such that they can be run in a loop. 
> Example Use case:- If we need to monitor 100 FTP servers, we have to create 100 ListFTP processor rather having one ListFTP processor which can get required fields as input and loop it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)