lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1013) IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box"
Date Mon, 01 Oct 2007 13:20:51 GMT

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

Yonik Seeley commented on LUCENE-1013:
--------------------------------------

> fix LogByteSizeMergePolicy to allow setting of the max by either MB or by doc count
+1

> IndexWriter.setMaxMergeDocs gives non-backwards-compatible exception "out of the box"
> -------------------------------------------------------------------------------------
>
>                 Key: LUCENE-1013
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1013
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.3
>
>
> Yonik hit this (see details in LUCENE-994): because we have switched
> to LogByteSizeMergePolicy by default in IndexWriter, which uses MB to
> limit max size of merges (setMaxMergeMB), when an existing app calls
> setMaxMergeDocs (or getMaxMergeDocs) it will hit an
> IllegalArgumentException on dropping in the new JAR.
> I think the simplest solution is to fix LogByteSizeMergePolicy to
> allow setting of the max by either MB or by doc count, just like how
> in LUCENE-1007 allows flushing by either MB or docCount or both.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


Mime
View raw message