[
https://issues.apache.org/jira/browse/NIFI-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269386#comment-15269386
]
ASF subversion and git services commented on NIFI-1721:
-------------------------------------------------------
Commit 194fc048fb856c079e1e55e746b82375b836397d in nifi's branch
refs/heads/master from [~pvillard]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=194fc04 ]
NIFI-1721 updated mock framework to return correct number of threads from mock
context
Signed-off-by: Matt Burgess <[email protected]>
This closes #408
> 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)
