lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-8198) Add ability to persist deletes across merges
Date Wed, 14 Mar 2018 08:24:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398236#comment-16398236
] 

ASF subversion and git services commented on LUCENE-8198:
---------------------------------------------------------

Commit b627fae03215fe52dee70638299e0b7c62b79c99 in lucene-solr's branch refs/heads/branch_7x
from [~simonw]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=b627fae ]

LUCENE-8200: Allow doc-values to be updated atomically together with a document

Today we can only update a document by deleting all previously indexed
documents for the given term. In some cases like when deletes are not
`final` in the way that documents that are marked as deleted should not
be merged away a `soft-delete` is needed which is possible when doc-values
updatea can be done atomically just like delete and add in updateDocument(s)

This change introduces such a soft update that reuses all code paths from deletes
to update all previously updated documents for a given term instead of marking it
as deleted. This is a spinnoff from LUCENE-8198


> 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


Mime
View raw message