lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-2086) When resolving deletes, IW should resolve in term sort order
Date Fri, 20 Nov 2009 18:14:39 GMT


Yonik Seeley commented on LUCENE-2086:

bq. Though, you need relatively high density of deletions to see that.

Yep, but re-indexing a whole bunch of documents is a common case - and that will give a very
high density (often consecutive terms).
Also, it may be a complete index build / rebuild, where all the terms will be consecutive.
 Solr, for instance, can't tell if there are any duplicates when building an index from scratch,
so it must use update().  There is a way to tell Solr not to enforce duplicate overwriting
(overwrite=false param) but I doubt many people do that, and it risks user error (using it
when there are dups in the docs being added, or already in the index).

> When resolving deletes, IW should resolve in term sort order
> ------------------------------------------------------------
>                 Key: LUCENE-2086
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 3.1
>         Attachments: LUCENE-2086.patch
> See java-dev thread "IndexWriter.updateDocument performance improvement".

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:
For additional commands, e-mail:

View raw message