You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2016/04/29 17:24:12 UTC

[jira] [Resolved] (UIMA-4861) When migrating to DUCC 2.1.0 must handle renamed properties

     [ https://issues.apache.org/jira/browse/UIMA-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Burn Lewis resolved UIMA-4861.
------------------------------
    Resolution: Fixed

Rename old property if in site properties during the merge.  Drop the limit on pipelines-per-process so user has full control.  Make the limit on pipelines-per-job restrict the max-processes so the JD is not overloaded.Updated docs.

> When migrating to DUCC 2.1.0 must handle renamed properties
> -----------------------------------------------------------
>
>                 Key: UIMA-4861
>                 URL: https://issues.apache.org/jira/browse/UIMA-4861
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Burn Lewis
>            Assignee: Burn Lewis
>            Priority: Minor
>             Fix For: 2.1.0-Ducc
>
>
> ducc.threads.limit has been renamed as ducc.job.max.pipelines.count



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