[jira] [Commented] (NIFI-202) ProcessContext should expose Run Duration

["Mark Payne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261253#comment-14261253 ] 

Mark Payne commented on NIFI-202:
---------------------------------

After discussing this with others, this is not a good idea. Processors like GetSFTP often expose a 'Batch Size' property for exactly this reason. The intent of the Run Duration is for the framework to know how long to schedule a Processor to run so that the FlowFiles can be more efficiently batched. This is using the value for a very different reason and may not be appropriate. Specifically, Run Duration cannot go beyond 2 seconds whereas GetSFTP may want to batch for 10 seconds - or a minute - or more.

Closing ticket as Won't Fix.

> ProcessContext should expose Run Duration
> -----------------------------------------
>
>                 Key: NIFI-202
>                 URL: https://issues.apache.org/jira/browse/NIFI-202
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.0.1
>            Reporter: Mark Payne
>            Priority: Minor
>             Fix For: 0.0.1
>
>         Attachments: 0003-NIFI-202-Expose-Run-Duration-in-ProcessContext.patch
>
>
> If a Processor has to perform some expensive operation before processing a FlowFile (obtain a connection to a remote system, for instance) it can should be able to process for the full duration of the Run Duration without returning for the sake of efficiency (by not releasing the resources until the Rn Duration ends). I.e., give the developer the ability (but not require them) to handle the run duration themselves when it makes sense.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)