You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2013/06/27 18:25:20 UTC

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

Robert Muir created LUCENE-5080:
-----------------------------------

             Summary: 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