Mike,
Yes, it's a bit of a compromise. But honestly, when you use
ExecuteStreamCommand you're stepping a bit outside of NiFi, and its
probably going to be less than ideal. As Joe said, writing your own
processor would allow you to handle things a bit more directly and
efficiently. However, ExecuteStreamCommand allows you to put together a
proof of concept, and from there you can decide if the gains from writing
your own processor are worth it for your case. Let us know if there's
anything else we can do to help.
Brandon
On Thu, Apr 23, 2015 at 12:59 PM mbwagne <[email protected]> wrote:
> Brandon's approach did work. Thanks Brandon!
>
> My concern is I'm tarring up a directory in a shell script just to unpack
> in
> a nifi processor. That seems like a lot of unnecessary IO. I wish I could
> trigger GetFile on the completion of the ExecuteStreamCommand via the
> success route.
>
>
>
> --
> View this message in context:
> http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/ExecuteStreamCommand-with-output-directory-tp1177p1219.html
> Sent from the Apache NiFi (incubating) Developer List mailing list archive
> at Nabble.com.
>
