[
https://issues.apache.org/jira/browse/LUCENE-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394674#comment-16394674
]
Simon Willnauer commented on LUCENE-8198:
-----------------------------------------
ah nevermind I think we need to add a new method something like this:
{code:java}
public long addAndUpdateDocument(Term term, Iterable<? extends IndexableField>
doc, Field... dvUpdates){code}
which is a combination of:
{code:java}
addDocument(Iterable<? extends IndexableField> doc) + updateDocValues(Term
term, Field... fields){code}
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
