[
https://issues.apache.org/jira/browse/UIMA-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burn Lewis resolved UIMA-4625.
------------------------------
Resolution: Fixed
Changed --process_thread_count to --process_pipeline_count
Also no longer warn about deprecated old options --- instead silently accept
them and document them as aliases. Silently ignore the obsolete
--classpath_order option but now reject the obsolete --number_of_instances if
its value is not 1 as with 2.0 ducc_reserve always returns only one.
> Change the option --process_thread_count to --process_pipeline_count
> --------------------------------------------------------------------
>
> Key: UIMA-4625
> URL: https://issues.apache.org/jira/browse/UIMA-4625
> Project: UIMA
> Issue Type: Improvement
> Components: DUCC
> Reporter: Burn Lewis
> Assignee: Burn Lewis
> Priority: Minor
> Fix For: 2.1.0-Ducc
>
>
> The word "thread" has caused some confusion since each UIMA pipeline may use
> multiple threads. This is really the per-process scaleout ... the number of
> work-items each JP can process simultaneously
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
