Uwe, Sorry for the lack of response. We do not yet have a good way to share templates. Our core way of doing so has been almost exclusively via the wiki [1]. We do have plans to address this in the future with an extension and template repository, highlighted in a feature proposal [2].
[1] https://cwiki.apache.org/confluence/display/NIFI/Example+Dataflow+Templates [2] https://cwiki.apache.org/confluence/display/NIFI/Extension+Registry On Wed, Feb 24, 2016 at 1:10 AM, Uwe Geercken <[email protected]> wrote: > Aldrin, > > I took a different approach. I store the info if a job is running > externally in mongodb. so the master writes to mongo when it starts and > when it ends. > > I then have a seperate part in the flow tjat checks the state of the > master process in mongo. actually quite simple. > > I will have to finalize the flow and add more details. > > Is there already a place to share templates? > > rgds > > Uwe > -- > Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail > gesendet. > > > Am 23.02.2016, 15:03, Aldrin Piri <[email protected]> schrieb: >> >> Uwe, >> >> Based on your description, one way I see it being supported by NiFi is >> the "master" process runs as an ExecuteProcess processor and then the >> result/output of this is directed to one or more ExecuteStreamCommand >> processors that carry on follow on processing. >> >> If that does not work, are there additional constraints/criteria that >> extend beyond this process? What is the relationship like between the >> follow-on processes? >> >> >> On Tue, Feb 23, 2016 at 5:11 AM, Uwe Geercken <[email protected]> >> wrote: >> >>> Hi Aldrin, >>> >>> I still have problem getting started. So I write up a little bit more. >>> >>> I have a master process that runs first. Then I have multiple other >>> processes that are supposed to run only after the master process has >>> finished. The processes are external processes. >>> >>> So a typical flow would be that the master starts. The other processes >>> don't start because the master process is still running and has not >>> completed. Once the master process completes, the other processes can >>> start. >>> >>> I hope this helps and you can give me another hint of how to do that. >>> >>> Rgds, >>> >>> Uwe >>> >>> *Gesendet:* Montag, 22. Februar 2016 um 22:28 Uhr >>> *Von:* "Aldrin Piri" <[email protected]> >>> *An:* [email protected] >>> *Betreff:* Re: ExecuteProcess >>> Uwe, >>> >>> Welcome to the community! >>> >>> If you are looking for one process to be kicked off by another, there is >>> a related processor to ExecuteProcess called ExecuteStreamCommand and I >>> believe should what you are looking for. ExecuteStreamCommand will accept >>> FlowFiles from incoming connections and use those to drive processing. In >>> this case, you could have whatever stimulus you are waiting for drive >>> follow on execution. >>> >>> If this does not solve what you are looking for, could you please >>> provide some additional details about your needs that are unmet by the >>> ExecuteStreamCommand approach? >>> >>> Thanks! >>> >>> On Mon, Feb 22, 2016 at 2:47 PM, Uwe Geercken <[email protected]> >>> wrote: >>>> >>>> Hello, >>>> >>>> I am new to Nifi and have a general question for the ExecuteProcess >>>> processor. >>>> >>>> Is it possible with Nifi to run a process and have a second process >>>> wait until the first one finished? How would I do that? It looks like >>>> though that this processor does not allow for an incomming connection, so I >>>> wonder if there is a different strategy I could take. >>>> >>>> Tahnks for your valuable help. >>>> >>>> Uwe >>>> >>> >>
