Folks,
I have a NiFi 1.0 deployed in a non-secure cluster across 3 nodes.
I have a flow pipeline that reads from a Kafka topic using ConsumeKafka and
kicks off an ExecuteStreamCommand mediated job based on attributes included
in the notification message.
What I observe is that jobs are being ki
to the recently released 1.1 release
> to see if the same behavior occurs.
>
> -Bryan
>
>
> On Thu, Dec 1, 2016 at 3:39 PM, A.B. Srinivasan
> wrote:
>
>> Folks,
>>
>> I have a NiFi 1.0 deployed in a non-secure cluster across 3 nodes.
>>
>> I have
Hello all,
I have a Java program being invoked within a ExecuteStreamCommand processor.
Prior to the invocation of the ExecuteStreamCommand, I set up the
'filename' property containing the output file into which the
ExecuteStreamCommand processor directs its output stream.
This works pretty well
result as a Gist:
> https://gist.github.com/ijokarumawak/0476ca8693058c1909a5842bab903fa3
>
> Hope this helps.
> Please let us know if you're seeing different result, there may be a
> corner case.
>
> Thanks,
> Koji
>
> On Tue, Dec 13, 2016 at 4:14 PM, A.B. Sri