[
https://issues.apache.org/jira/browse/NIFI-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268729#comment-15268729
]
ASF GitHub Bot commented on NIFI-1721:
--------------------------------------
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/408
NIFI-1721 updated mock framework to return correct number of threads from
mock context
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-1721
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/408.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 #408
----
commit 304cf64452eafe1e669d61df44775e63ca15c01f
Author: Pierre Villard <[email protected]>
Date: 2016-05-03T13:40:59Z
NIFI-1721 updated mock framework to return correct number of threads from
mock context
----
> 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
> Labels: beginner
>
> 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)
