Hi Chris Thanks for the links, but yes I've read them before and I'm using similar flows in other use cases. In both examples from the link a process is splitting data up in two flows, flow A and flow B. In flow A you use a wait process blocking the rest of flow A. In the end of flow B you have a notify process which trigger flow A. My issue is that I only have 1 flow. Could be something like this where the issue is that the outpu of the ExecuteProcess use static filenames (stupid I know). So if the Execute process runs multiple times before the GetFile is done, it will overwrite old files. Therefore I need some way to block the PutFile and Execute Process, until the GetFile is done or that the output folder is empty GetData - UpdateAttribute - WAIT (or block until output folder from ExecuteProcess is empty) - PutFile - ExecuteProcess - GetFile - NOTIFY - do something more.
regards Jens Den tir. 24. mar. 2020 kl. 11.37 skrev Chris Sampson < [email protected]>: > Have you looked at some Wait-Notify examples (it does sound like what > you're wanting to use): > > https://gist.github.com/ijokarumawak/20125d663d2116c6dae1eecae8d7acbc > > > https://pierrevillard.com/2018/06/27/nifi-workflow-monitoring-wait-notify-pattern-with-split-and-merge/ > > Your Notify should be on a different "branch" of your Flow than your Wait > - send duplicate copies of FlowFiles to the Wait and also to the part of > your flow that does the "real" processing. > > > *Chris Sampson* > IT Consultant > *Tel:* 07867 843 675 > [email protected] > > > > On Tue, 24 Mar 2020 at 10:05, Jens M. Kofoed <[email protected]> > wrote: > >> Hi >> >> I'm trying to build a flow, where a putfile process is only allow to >> write a file, if the previous file has finished the following block in the >> flow. But I can't works it out with my wait notify. Since the first file >> can't go through the wait block because the notify is coming after the >> wait block. >> >> kind regards >> Jens >> >
