[
https://issues.apache.org/jira/browse/LUCENE-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468560#comment-16468560
]
Adrien Grand commented on LUCENE-8298:
--------------------------------------
I think we should try to avoid adding {{set}} on MutableBits. It puts too much
pressure on the live docs format? Also the ability to un-hard-delete is a bit
scary to me because of the documents that got marked as deleted because they
failed indexing. Maybe {{PendingSoftDeletes}} should manage their bits directly
instead of relying on the live docs format?
Also do we need to detect null values more proactively now that the
NumericDocValuesField constructor allows to pass nulls?
> Allow DocValues updates to reset a value
> ----------------------------------------
>
> Key: LUCENE-8298
> URL: https://issues.apache.org/jira/browse/LUCENE-8298
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: 7.4, master (8.0)
> Reporter: Simon Willnauer
> Priority: Major
> Fix For: 7.4, master (8.0)
>
> Attachments: LUCENE-8298.patch, LUCENE-8298.patch
>
>
> Today once a document has a value in a certain DV field this values
> can only be changed but not removed. While resetting / removing a value
> from a field is certainly a corner case it can be used to undelete a
> soft-deleted document unless it's merged away.
> This allows to rollback changes without rolling back to another
> commitpoint
> or trashing all uncommitted changes. In certain cenarios it can be used to
> "repair" history of documents in distributed systems.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
