Mike, You could also create a wrapper script for your application and call that from ExecuteStreamCommand. The wrapper would call your application, tar up the output, and steam that out. Follow that with UnpackContent, and continue from there.
Brandon On Mon, Apr 20, 2015, 5:07 PM Joe Witt <[email protected]> wrote: > Mike, > > Consider using GetFile to a parent directory of the > executestreamcommand output and telling it to recurse for files. > > Keep in mind though no matter what if the process doesn't write files > with some sort of flag you have a race condition. GetFile let's you > do things to reduce the risk of the inherent race condition though. > For instance, you can tell it to only pick up data that is a certain > age as indicated by its last modified date. > > Does this sound like it would take care of it? > > Thanks > Joe > > On Mon, Apr 20, 2015 at 4:45 PM, mbwagne <[email protected]> > wrote: > > I have an ExecuteStreamCommand Processor that runs an application that > > generates an output directory with several files and subdirectories (no > > option to specify output stream). How would I pickup the output from that > > command from another processor, ensuring the command has completely > finished > > (i.e. GetFile would start right away)? > > > > > > > > -- > > View this message in context: > http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/ExecuteStreamCommand-with-output-directory-tp1177.html > > Sent from the Apache NiFi (incubating) Developer List mailing list > archive at Nabble.com. >
