<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Best approach for getting files from 100+ ftp server using Listsftp/Getsftp in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218592#M180493</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;    I have a project that need to fetch files from over 100 ftp servers. If I use listsftp + fetchsftp approach, I will need over 100+ listsftp component for each of the ftp servers. The template will become so complicated and difficult to manage. If I use getsftp approach, I have to manage how to fetch only new files. Did anyone come across a problem like this? I need some suggestion how to handle this type of problem.&lt;/P&gt;&lt;P&gt;    Thanks&lt;/P&gt;&lt;P&gt;Fan.&lt;/P&gt;</description>
    <pubDate>Sat, 11 Aug 2018 09:04:35 GMT</pubDate>
    <dc:creator>dick_fan</dc:creator>
    <dc:date>2018-08-11T09:04:35Z</dc:date>
    <item>
      <title>Best approach for getting files from 100+ ftp server using Listsftp/Getsftp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218592#M180493</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;    I have a project that need to fetch files from over 100 ftp servers. If I use listsftp + fetchsftp approach, I will need over 100+ listsftp component for each of the ftp servers. The template will become so complicated and difficult to manage. If I use getsftp approach, I have to manage how to fetch only new files. Did anyone come across a problem like this? I need some suggestion how to handle this type of problem.&lt;/P&gt;&lt;P&gt;    Thanks&lt;/P&gt;&lt;P&gt;Fan.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Aug 2018 09:04:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218592#M180493</guid>
      <dc:creator>dick_fan</dc:creator>
      <dc:date>2018-08-11T09:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: Best approach for getting files from 100+ ftp server using Listsftp/Getsftp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218593#M180494</link>
      <description>&lt;P&gt;I would start by creating a database or data file of your 100 ftp servers and credentials.  Use NiFi to query this data and then send the results downstream into your data flow where downstream NiFi processors are configured dynamically using ${attributes} from the flow files generated by querying the ftp data.  This will make your data flow very simple and dynamic.&lt;/P&gt;&lt;P&gt;If this answer helps, please choose ACCEPT.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 19:55:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218593#M180494</guid>
      <dc:creator>stevenmatison</dc:creator>
      <dc:date>2018-08-13T19:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: Best approach for getting files from 100+ ftp server using Listsftp/Getsftp</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218594#M180495</link>
      <description>&lt;P&gt;I have modified the GetSFTP Processor to accept parameters send from the attributes of the flowfile&lt;/P&gt;</description>
      <pubDate>Tue, 09 Oct 2018 21:37:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Best-approach-for-getting-files-from-100-ftp-server-using/m-p/218594#M180495</guid>
      <dc:creator>dick_fan</dc:creator>
      <dc:date>2018-10-09T21:37:32Z</dc:date>
    </item>
  </channel>
</rss>

