Here's a better formatted version. Email decided to switch back to RTF.
Welcome to NiFi! This can certainly be done. The processor you're looking for to execute arbitrary URLs is the InvokeHTTP processor [1]. So your flow would be GetFile -> SplitText -> ExtractText (to get the URL to an attribute) -> InvokeHTTP. In the InvokeHTTP you'll use the expression language [2] to reference the proper attribute. For the second part, under the configuration for getFile if you uncheck "Keep Source File" it'll only get the dog.txt once then get rid of the file afterwards. Also as a note, I am in the process of making a RouteText processor that will make it much easier to work with individual lines of text. You can check out the ticket here [3]. [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html [2] https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html [3] https://issues.apache.org/jira/browse/NIFI-942 Hope this helps! Joe - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com - - - - - - Joseph Percivall linkedin.com/in/Percivall e: joeperciv...@yahoo.com On Monday, September 21, 2015 5:01 PM, Joe Percivall <joeperciv...@yahoo.com.INVALID> wrote: Welcome to NiFi! This can certainly be done. The processor you're looking for to execute arbitrary URLs is the InvokeHTTP processor [1]. So your flow would be GetFile -> SplitText -> ExtractText (to get the URL to an attribute) -> InvokeHTTP. In the InvokeHTTP you'll use the expression language [2] to reference the proper attribute. For the second part, under the configuration for getFile if you uncheck "Keep Source File" it'll only get the dog.txt once then get rid of the file afterwards. Also as a note, I am in the process of making a RouteText processor that will make it much easier to work with individual lines of text. You can check out the ticket here [3]. [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.InvokeHTTP/index.html[2] https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html[3] https://issues.apache.org/jira/browse/NIFI-942 Hope this helps!Joe- - - - - - Joseph Percivalllinkedin.com/in/Percivalle: joeperciv...@yahoo.com On Monday, September 21, 2015 8:59 AM, wizz <rober...@johansyah.com> wrote: Hi Guys, I am new to Nifi, it looks great but I am exploring what it can be done. Is it possible to have something similar to this flow: GetFile --> SplitText --> GetHttp --> Zip? 1. GetFile gets file (dog.txt) which contains list of link: http://pic.pedigreedatabase.com/dogbreeds/samoyed.jpg http://pic.pedigreedatabase.com/dogbreeds/bichon_frise.jpg http://pic.pedigreedatabase.com/dogbreeds/norwich_terrier.jpg http://pic.pedigreedatabase.com/dogbreeds/west_highland_white_terrier.jpg 2. SplitText will get each of the line of text 3. The line feeds to GetHttp to property URL which it will download the file and save it accordingly Is this possible guys? It seems the properties of processor is immutable and the only dynamic is when the expression language is allowed in the property. Another question would be, the source text (dog.txt) it seems being executed multiple times, how do I mark it that the NiFi got the inputs each line and no repeat? Thanks!! -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/Dynamic-Properties-for-Processor-tp2895.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
