@naga_satish  I think the solution you will find easiest is to use a CSV record reader and writer.  In the reader you tell schema/settings it is pipe delimited, and escaped with quotes.  In the writer you choose same schema no quotes.  It should be straight forward use case for RecordReaders in UpdateRecord/QueryRecord/LookupRecord or other RecordReader based processors.     If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.     Thanks, Steven ... View more

@Makaveli  You can use File Filter Regex in ListSFTP to control which files come out of this processor.   Otherwise, you need to use ListSftp->UpdateAttribute->RouteOnAttribute to make sure the file name ends as suggested above.  Once you have a solid route of the files you want, then connect to FetchSFTP. ... View more

@Makaveli  The solution you are looking for here is updateAttribute to create your string of the date format you want.  todayString =  {now():format('YYYY_MM_dd_mm')} Then in routeOnText you use this attribute like this:  newRoute =    ${filename:endsWith(_${todayString}}   If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.   Thanks, Steven ... View more

@ravisro  I think the only way you can do this is to make a custom process that interacts with the NiFI Api to complete your actions.   If you use the NiFI UI,  with developer tools open,  you can watch/record all of the api calls the UI uses against the api to perform the action manually.  Next, duplicate the required actions in your processor.       I would love to see you post this same question in the NiFi Slack...  ... View more

@ravisro   This is a great question.  I would love to see some of the NiFi pros here respond.  However, you may only find a better response on NiFI Mailing list or ApacheNiFi slack:   http://nifi.apache.org/mailing_lists.html(invite link for slack channel here)   In the meantime, one of the ways i have accomplished this in the past, is documenting the root level Controller Service Ids for each environment (DEV,STAGING,PROD) and swapping these into the template before importing the template to the environment.   It's a clunky solution, but it works.   I have used this since before NiFi Registry.  With Registry in the mix,  I am forced to use the NiFI API to update the flows to appropriate controller service.  Again clunky, which is why I would love to hear more comments from other community members.   If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.   Thanks, Steven ... View more

@manas_mandal786  Thanks for providing template.  The next thing I wanted to look at was configs so you read my mind.   I was able to import your template, start the context service, and add success/failure routes for each test to an output port (so i can see results are success/fail).  With the workflow setup I execute 2 curl calls:   curl -L -X POST 'http://localhost:8009/report' -H 'Content-Type: multipart/form-data' -F test=test curl -L -X POST 'http://localhost:8009/report' -H 'Content-Type: multipart/form-data' -H 'ReportType: test' -F test=test   And my canvas looks like this:     I did not get any warnings.  Everything worked as expected.  If you are still getting issues,  i suspect it is something to do with your environment (windows) not being able to store the metadata for the StandardSSLContext Service. This store will hold the client connection until you send the response.  In your case that part does not seem to be working.   Look for any errors/warnings in nifi-app.log while testing.  You may see warnings in the Controller Services window on the StandardSSLContext.   You may need to set each processor to DEBUG in order to find more info in the nifi-app.log.        ... View more

@manas_mandal786    I sometimes see these errors when a long amount of time is spent testing within the flow from the handhttprequest through to the handlehttpresponse.  You no longer have an active connection to the original requesting client.  If you test the flow entirely with a single request do you still get the error? ... View more

@vatodorov19   I have used tons of self signed certs and not had issues.   Maybe you need to just adjust the method to create the self signed certs and/or the keystore and truststores based on known working nifi samples.   SSL, Certs, Keystores, Versions, and SSL Context Services each are all very finicky so getting them right can be as easy as a config change, or adjustment in the commands to kick of cert/keystore creations. ... View more

@Namitjain   This should absolutely work.  I would suggest you update the post with information about the exact issue you are having. Be sure to include your configuration of the putS3 Processor.   I also recommend not routing failure back on the processor itself in testing.  Route to another proc, or an output port during testing.   When a flowfile goes to failure,  inspect it.  Look at the attributes on the flowfile, it often has info on why it failed.   If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.   Thanks, Steven ... View more