@Biswajit Chakraborty If you are using GetFTP processor then after pulling files then processor going to add getftp.remote.source attribute to the flowfile, then you can use this flowfile attribute then prepare filename in update attribute processor Add new property in update attribute filename ${filename}_${getftp.remote.source} //add remote source name to the filename as you can change the way of using expression language to change filename as following ${filename:append(${getftp.remote.source})} //result 711866091328995HDF04-1 (or) ${filename}${getftp.remote.source} //result 711866091328995HDF04-1 Example:- if you are having filename value as 711866091328995 and getftp.remote.source value as HDF04-1 then output flowfile from update attribute will have filename as 711866091328995_HDF04-1 //because we are adding remote source value to filename with underscore (or) if you are having issue with the same filenames and they are getting overwritten, The FlowFile will also have an attribute named uuid, By using UUID(which is a unique identifier for this FlowFile) as filename, will keep every filename as unique so that we are not going to have any overwriting issues. Configs:- filename ${uuid} ... View more

@Cesar Rodrigues Use RouteText Processor (The data is then routed according to these rules, routing each line of the text individually) and then configure the processor as Route text Configs:- Routing Strategy Route to each matching Property Name Matching Strategy Contains Ignore Leading/Trailing Whitespace true Ignore Case true Grouping Regular Expression No value set flowfile1 |1| more text //checks the line having the content and routes to flowfile1 relation flowfile2 |8| more text //checks the line having the content and routes to flowfile1 relation Input:- Some fixed text |1| more text Another field |8| more text Last one |1| more text Output:- Flowfile1:- as we are checking if the contents having |1| more text so the following lines will routes to flowfile1 relationship Some fixed text |1| more text Last one |1| more text Flowfile2:- lines having |8| more text will route to this relation Another field |8| more text Flow:- ... View more

@Murat Menteşe Instead of GetHTTP processor use InvokeHTTP processor,InvokeHTTP Processor accepts incoming connections. Use Generate Flowfile Processor and add all your URL's in GenerateFlowfile processors as each line having one URL in it. Generate Flowfile Processor:- Configs:- As shown in the above screenshot add all URL's one per each line in CustomText property and In Scheduling tab change the frequency of run. SplitText:- We are Triggering GenerateFlowfile processor and we are going to have onefile having all url's in it so we are going to split the file into 1 Line as new flowfile now. Configs:- Line Split Count 1 THen connect Splits relation from SplitText processor to ExtractText processor. ExtractText:- We are going to Extract the contents of flowfile and adding as flowfile attribute in this processor then the extracted attribute is going to be used in InvokeHTTP processor. Add new property in this processor by clicking on + sign at right corner URL (.*) Configs:- ControlRate:- it's an optional processor as we are going to control the rate of flowfiles that are going to InvokeHTTP processor. Rate Control Criteria flowfile count Maximum Rate 1 Rate Controlled Attribute No value set Time Duration 1 min so with this configs we are going to process one flowfile per 1 min but you can change all this configs as per your requirements. InvokeHTTP:- we have configured RemoteURL property as ${URL} , this URL attribute we have added in ExtractText Processor. So we don't need to use Seperate GetHTTP processors for each Request by following above approach. Flow:- GenerateFLowFIle //keep all URL's and schedule to run SplitText //Split into one line Extract Text //extracting URL from content of ff and adding as attribute ControlRate(optional) //control the rate of flowfiles passed to next processor InvokeHTTP //Use the extracted URL attribute and Get Response. I'm attaching my xml here save, use as reference and modify as per your requirements. hcc-168913-gethttp.xml ... View more

@Yogesh Singh If you are using NiFi 1.2+ then you can use Three ConverRecord processors in parallel to read your Csv file and create 3 different CsvRecordSetwriter with your required columns in it and processors will give you 3 different files. Flow:- ConvertRecord Processor:- Read the source file that having Name,Age,Sex,Country,City,PostalCode and writes the file with Name, Age, Country I have attached .xml and i have implemented for one convert record processor which is going to read the csv file and result only Name,City columns as an output file. You can save the xml file,upload to your nifi instance and enhance CsvRecordSetwriter as per your requirements. Example:- Input Csv File:- Name,Age,Sex,Country,City,PostalCode hcc,21,M,US,OR,32811 HDP,22,F,US,OR,32746 Output Csv file:- Name,City hcc,OR HDP,OR So in Convert Record i have setup Csv Reader which is going to read the incoming flowfile and CsvRecordSetWriter which is going to output only the required columns that we have mentioned in the controller service. Xml file:- convertrecord.xml ConvertRecord example:- https://community.hortonworks.com/articles/115311/convert-csv-to-json-avro-xml-using-convertrecord-p.html https://blogs.apache.org/nifi/entry/record-oriented-data-with-nifi Flow:- (or) If you are using NiFi version prior to <1.2 then you need to use 1.execute stream command processor//Delete the header of the file using tail as command Path and command arguments as -n;+2 ,connect output stream relation to next processor 2.Split Text //to split the content of csv file to one line count, connect splits relation to next processor 3.Extract Text //add new properties and matching regex values that can extract the each value as header,connect success to all three parallel replace text processors. 4.Three Replace Text in parallel //specifying your required attribute names that you want on each file then each processor will result the required file. 5. MergeContent(optional) //to merge the each small flowfile content as one file before storing into directory. Extract text Example:- https://community.hortonworks.com/questions/160868/how-to-extracttext-from-flow-file-using-nifi-proce-1.html Replace text Example:- https://community.hortonworks.com/questions/158910/parsing-json-formatted-csv-file-using-nifi.html MergeContent Example:- https://community.hortonworks.com/questions/149047/nifi-how-to-handle-with-mergecontent-processor.html Let us know if you are having any issues..!! ... View more