lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3828) Impossible to delete doc by docId, undeleteAll or setNorm(docId..)
Date Mon, 27 Feb 2012 17:46:48 GMT


Yonik Seeley commented on LUCENE-3828:

bq. The problem is IndexWriter executes query deletes per segment (unfortunately with AtomicReaderContext.docBase==0).

Ahhhh, so no way to get a true top-level reader for anything that needs to be cross-segment
(like joins, grouping, etc.)  Bummer.
> Impossible to delete doc by docId, undeleteAll or setNorm(docId..)
> ------------------------------------------------------------------
>                 Key: LUCENE-3828
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: core/index
>    Affects Versions: 4.0
>            Reporter: Andrzej Bialecki 
> It appears that there is a major regression in the trunk API. It's no longer possible
> 1. delete document by internal id (even though you can iterate and retrieve docs by internal
> 2. undelete all deleted (but not yet reclaimed) documents
> 3. set norm value on a specific document (by internal id)
> The lack of #1 means that you have to use delete by term or by query, which in turn means
that now we require that documents have a unique primary key (otherwise you won't be able
to delete a particular document that shares terms with other docs). IMHO this item is critical
and should be fixed.
> The lack of #2 might not be critical but it still comes handy in some situations.
> The lack of #3 means that you have to update the whole doc if you just want to correct
one field, which might be ok for the time being - it's a special case of not having updateable
fields in general. But it's quite inconvenient if all you want to do is to adjust a weight
of doc without reindexing, something that is possible with 3.x.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message