I continue to struggle with ExecuteStreamCommand, and am hoping one of you
from our user community can help me with the following:
1. Can ExecuteStreamCommand be used as I am trying to use it?
2. Can you direct me to an example where ExecuteStreamCommand is configured
to do something similar to my use case?
My use case:
The incoming flowfiles in my flow path are 7z zips. Based on what I've
researched so far, NiFi's native processors don't handle unpacking of 7z
files.
I want to read the 7z files as STDIN to ExecuteStreamCommand.
I'd like the processor to call out to a 7za app, which will unpack the 7z.
One incoming flowfile will yield multiple output files. Let's say twelve in
this case.
My goal is to output those twelve as new flowfiles out of
ExecuteStreamCommand, to its output stream path.
I can't yet get this to work. Best I've been able to do is configure
ExecuteStreamCommand to unpack ${filename} to a temporary output directory
on disk. Then I have another path in my flow polling that directory every
few minutes looking for new data. Am hoping to eliminate that intermediate
write/read to/from disk by keeping this all within the flow and JVM memory.
Thanks very much in advance for any assistance.
