lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée (JIRA) <>
Subject [jira] Commented: (LUCENE-879) Document number integrity merge policy
Date Sat, 12 May 2007 17:19:15 GMT


Nicolas Lalevée commented on LUCENE-879:

That was I was talking about, storing in Lucene just an ID referencing the data in another
storage. So this Lucene-stored ID became the document-id you try to fix.

I have also done some experimentation about making the storage external, but I realized that
what I was coding was exactly the same as storing an ID in Lucene. But I didn't tried to "fix"
the document id.

> Document number integrity merge policy
> --------------------------------------
>                 Key: LUCENE-879
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 2.1
>            Reporter: Karl Wettin
>            Priority: Minor
>         Attachments: LUNCENE-879.diff, LUNCENE-879.diff
> This patch allows for document numbers stays the same even after merge of segments with
> Consumer needs to do this:
> indexWriter.setSkipMergingDeletedDocuments(false);
> The effect will be that deleted documents are replaced by a new Document() in the merged
segment, but not marked as deleted. This should probably be some policy thingy that allows
for different solutions such as keeping the old document, et c.
> Also see

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