[ https://issues.apache.org/jira/browse/LUCENE-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695939#comment-13695939 ]
Robert Muir commented on LUCENE-5080: ------------------------------------- {quote} Maybe instead we can have CMS.reset(int,int) to avoid that case? {quote} Fine by me. if we decide we dont like it later, we can just remove it. > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org