You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Michael Moser (JIRA)" <ji...@apache.org> on 2016/04/01 17:18:25 UTC

[jira] [Created] (NIFI-1721) MockProcessContext getMaxConcurrentTasks is always 1; should return correct number

Michael Moser created NIFI-1721:
-----------------------------------

             Summary: MockProcessContext getMaxConcurrentTasks is always 1; should return correct number
                 Key: NIFI-1721
                 URL: https://issues.apache.org/jira/browse/NIFI-1721
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Tools and Build
            Reporter: Michael Moser
            Priority: Trivial


There is a method in the ProcessContext API where a processor can call getMaxConcurrentTasks() to learn how it's been configured.  When testing with the Mock framework, the MockProcessContext getMaxConcurrentTasks() always returns 1.

In a Mock TestRunner, you can set your test to run with multiple threads using TestRunner.setThreadCount().  The MockProcessContext should return the number of threads that was set using TestRunner.setThreadCount().



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