You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2019/04/05 20:58:00 UTC

[jira] [Commented] (NIFI-6192) Executing Flow Files via API passing dynamic variables

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

Andy LoPresto commented on NIFI-6192:
-------------------------------------

Hi Andrea, thanks for submitting your feature request. I changed the priority and the flags because this is not a blocker and it would not be a patch. This is a new feature request. Please provide further details around your use case. 25,000 flowfiles is a very manageable number for even a single NiFi node. Please explain why this doesn't work for your situation, and how you expect the 3rd party web app to transfer specific variable values to the incoming flowfile in your flow. Thank you. 

> Executing Flow Files via API passing dynamic variables 
> -------------------------------------------------------
>
>                 Key: NIFI-6192
>                 URL: https://issues.apache.org/jira/browse/NIFI-6192
>             Project: Apache NiFi
>          Issue Type: Wish
>          Components: Core Framework
>    Affects Versions: 1.7.1
>            Reporter: Andrea
>            Priority: Major
>              Labels: features, usability
>
> In all our use test cases for a major project we have the need to pass dynamic variables during the execution of a NiFi workflow , and consume these variables in several processors.
> We cannot achieve this using registry variables as our test case apply to a workflow/flowfile that need to be executed 100 times per minute , everytime with a set of different variable values.
> We have found people workarounding this issue creating n-flowfiles , but for us this means having something like 25.000 different flowfiles
> *Use Test Cases*
> 1) From a Web App we need to trigger the execution of a flowfile passing user defined parameters
> 2) From a 3rd Party App Scheduler we need to trigger the execution of a flowfile passing 3rd Party App parameters
>  
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)