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-2602) Default merge policy should take deletions into account
Date Sun, 15 Aug 2010 00:50:16 GMT

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

Yonik Seeley commented on LUCENE-2602:
--------------------------------------

Great - I meant to add this as a default for solr quite some time ago.
REMINDER (to self mainly, or anyone else willing): need to verify that solr correctly picks
up this default (i.e doesn't accidentally override it).
I know there were related issues like SOLR-1444.

> Default merge policy should take deletions into account
> -------------------------------------------------------
>
>                 Key: LUCENE-2602
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2602
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 3.1, 4.0
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.1, 4.0
>
>
> LUCENE-1634 added a calibrateSizeByDeletes; we had a TODO to default this to true as
of 3.0 but we missed it.  I'll fix it now for 3.1 and 4.0.  While this is technically a change
in back-compat (for 3.x), I think it's fine to make an exception here; this should be a big
win for indices that have high doc turnover with time.

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message