nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Payne (JIRA)" <>
Subject [jira] [Commented] (NIFI-380) Create ExecuteProcess processor
Date Fri, 06 Mar 2015 17:02:38 GMT


Mark Payne commented on NIFI-380:


All looks good. Do we want to remove the constraint that for periodic batches of output we
require textual output? The main reason for doing this was because it seemed to make sense
that binary data shouldn't be arbitrarily chopped apart, and by requiring it to be text we
avoided partial lines to be written out by reading/writing a line at a time.

However, I believe you mentioned somewhere that you can see a good use to have binary data
arbitrarily chopped. If so, we can enable this and add another property that indicates whether
or not the output that should be line-delimited.

Otherwise, I vote +1 to merge to develop.


> Create ExecuteProcess processor
> -------------------------------
>                 Key: NIFI-380
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 0.0.2
>         Attachments: 0002-NIFI-380-Initial-import-of-ExecuteProcess-processor.patch,
> this processor should behave similar to ExecuteStreamCommand but is a source processor,
rather than taking in flowfiles. Also, it needs to support the ability to periodically transfer
a FlowFile with the output of the command, even if the command has not finished, and then
create a new FlowFile

This message was sent by Atlassian JIRA

View raw message