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:56:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Andy LoPresto updated NIFI-6192:
--------------------------------
Priority: Major (was: Blocker)
> 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)