nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Witt (JIRA)" <>
Subject [jira] [Updated] (NIFI-583) Allow ExecuteProcess to consume an incoming flowfile
Date Wed, 03 Jun 2015 15:07:38 GMT


Joseph Witt updated NIFI-583:
    Fix Version/s: 0.2.0

> Allow ExecuteProcess to consume an incoming flowfile
> ----------------------------------------------------
>                 Key: NIFI-583
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 0.1.0
>            Reporter: Ricky Saltzer
>            Assignee: Ricky Saltzer
>             Fix For: 0.2.0
>         Attachments: NIFI-583.1.patch
> In some cases it would be really nice to allow a FlowFile to trigger an OS action. For
instance, after a daily dump of data is written to an Impala table in HDFS, I would like to
execute a refresh on the table via the shell. 
> As it stands, the ExecuteProcess processor will allow a FlowFile in a connection to trigger
execution, but unless your connection has an expiration set, the FlowFile will stay there
indefinitely. The main issue here is that it will continue to re-execute your ExecuteProcess
processor over and over. 
> As far as I know, there's only two clear ways around this. (1) - you can use the ExecuteStreamCommand,
instead, but *only* if that command can properly handle STDIN. (2) - you can set your ExecuteProcess
processor to execute on a schedule (e.g. 1 per minute) and expire the FlowFile before it can
re-execute (e.g. 10 seconds). 
> It would be useful if the ExecuteProcess processor consumed the FlowFile, and passed
it through a "passthrough" relationship of some kind. A second option would be to make it
configurable (false by default) to drop the FlowFile, or to pass it through a second relationship,
that way it doesn't break anyone's current pipelines. 

This message was sent by Atlassian JIRA

View raw message