You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Simon Willnauer (JIRA)" <ji...@apache.org> on 2018/03/11 21:14:00 UTC
[jira] [Commented] (LUCENE-8198) Add ability to persist deletes
across merges
[ https://issues.apache.org/jira/browse/LUCENE-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394655#comment-16394655 ]
Simon Willnauer commented on LUCENE-8198:
-----------------------------------------
here is a [link|https://github.com/s1monw/lucene-solr/commit/a7978711f31bce3eca79320c7cb4281d76416022] to the patch on github to link lines or comment directly.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org