[jira] [Commented] (LUCENE-5080) CMS setters cannot work unless you setMaxMergeCount before you setMaxThreadCount

["Michael McCandless (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694841#comment-13694841 ] 

Michael McCandless commented on LUCENE-5080:
--------------------------------------------

+1
                
> CMS setters cannot work unless you setMaxMergeCount before you setMaxThreadCount
> --------------------------------------------------------------------------------
>
>                 Key: LUCENE-5080
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5080
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>
> {code}
>   public void setMaxThreadCount(int count) {
>     ...
>     if (count > maxMergeCount) {
>       throw new IllegalArgumentException("count should be <= maxMergeCount (= " + maxMergeCount + ")");
>     }
> {code}
> but:
> {code}
>    public void setMaxMergeCount(int count) {
>     ...
>     if (count < maxThreadCount) {
>       throw new IllegalArgumentException("count should be >= maxThreadCount (= " + maxThreadCount + ")");
>     }
> {code}
> So you must call them in a magical order. I think we should nuke these setters and just have a CMS(int,int)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org