Simon Willnauer commented on LUCENE-8198:

I agree with you on all that. I also wonder if we can then implement "undelete" 
easily which would be very beneficial. One idea would be to change the 
updateDocument method to this: __
public long updateDocument(Term term, Iterable<? extends IndexableField> doc, 
Field... dvUpdates){code}
this would be 100% bwc and would allow to do this as well. I didn't think of 
such a simple way of doing it. I think the change would be very simple to 

> Add ability to persist deletes across merges
> --------------------------------------------
>                 Key: LUCENE-8198
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8198
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: 7.3, master (8.0)
>            Reporter: Simon Willnauer
>            Assignee: Simon Willnauer
>            Priority: Major
>         Attachments: LUCENE-8198.patch
> This allows conditionally persist deletes on a per document basis to prevent 
> them from being merged away. This expert feature is useful to maintain 
> history of documents in the index where otherwise a duplicate storage 
> mechanism would be needed. For instance features like CouchDBs changes API 
> can be build on top of persistent deletes. While using persistent deletes has 
> a considerably small overhead at merge time or when deletes applied to fully 
> deleted segments, there is no impact if persistent deletes are unused.

This message was sent by Atlassian JIRA

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

Reply via email to