@ANKIT PATEL Here's a sample flow. For simplicity, instead of reding from FTP location, I am reading from local path. I have 3 processors in my flow. ListFile - Will list the files in the directory I passed in the Configuration tab. Similar to ListFTP, just local. FetchFile - Will fetch the files that I will mention. Again, similar to FetchFTP, but just local. PutFile - Will write the data. If you pay attention, ListFile processor is giving me the list of the files in folder, and since the downstream processor is stopped, the flow files are queued up. So I went ahead and did a "List Queue" to see the flow files which are queued up. I saw something like this. These are called as "flow files" in NiFi. If you click the "i" button to the leftmost side, you will see Attributes tab as shown below. You can see many attributes, but the main attributes that we need in this example are absolute.path - The location from where the file is filename - The name of the file These are the properties regarding the data we are about to fetch. Now FetchFile can read these files from the given directory and I can tell my FetchFile processor to read these files by using these "attributes" as shown below. Since I have the directory name information available in the form an attribute, I can use it while storing the data as well and hence mimicking the exact directory structure from the source. Hope that helps!
... View more
