[jira] [Updated] (NIFI-4969) Failed to import versioned flow when processor uses "Event Driven" scheduling
[ https://issues.apache.org/jira/browse/NIFI-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-4969: -- Resolution: Fixed Fix Version/s: 1.6.0 Status: Resolved (was: Patch Available) > Failed to import versioned flow when processor uses "Event Driven" scheduling > - > > Key: NIFI-4969 > URL: https://issues.apache.org/jira/browse/NIFI-4969 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > Fix For: 1.6.0 > > > Create a flow where a processor has scheduling strategy set to event-driven > with concurrent tasks set to 0. Start version control on the flow, and them > try to import a new process group using the flow from previous step. > The error is because during import we set the concurrent tasks value before > the scheduling strategy, and StandardProcessorNode line 630 throws an > exception if the tasks is < 1 and strategy is not event driven. > The exception also does not report any message so it is hard to figure out > what the issue is. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-4969) Failed to import versioned flow when processor uses "Event Driven" scheduling
[ https://issues.apache.org/jira/browse/NIFI-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Bende updated NIFI-4969: -- Status: Patch Available (was: Open) > Failed to import versioned flow when processor uses "Event Driven" scheduling > - > > Key: NIFI-4969 > URL: https://issues.apache.org/jira/browse/NIFI-4969 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.5.0 >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Major > > Create a flow where a processor has scheduling strategy set to event-driven > with concurrent tasks set to 0. Start version control on the flow, and them > try to import a new process group using the flow from previous step. > The error is because during import we set the concurrent tasks value before > the scheduling strategy, and StandardProcessorNode line 630 throws an > exception if the tasks is < 1 and strategy is not event driven. > The exception also does not report any message so it is hard to figure out > what the issue is. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
