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

ASF GitHub Bot commented on NIFI-4969:
--------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi/pull/2539

    NIFI-4969 Fixing error when importing versioned flow with a processor…

    … that uses event driven scheduling
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi NIFI-4969

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/2539.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2539
    
----
commit 51fad617ba18c41009a54194b2fc67c385f9e478
Author: Bryan Bende <bbende@...>
Date:   2018-03-13T16:42:33Z

    NIFI-4969 Fixing error when importing versioned flow with a processor that 
uses event driven scheduling

----


> 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)

Reply via email to