[
https://issues.apache.org/jira/browse/LUCENE-8961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920958#comment-16920958
]
Adrien Grand commented on LUCENE-8961:
--------------------------------------
This feels too unsafe to me for CheckIndex. For instance, what if idField is
the corrupt field, you could end up with missing ids or the wrong ids? I'm fine
with adding more information to the CheckIndex status in order to make it
easier to do this kind of hacks on top of CheckIndex, but I'd like to keep
CheckIndex something that is rock solid.
> CheckIndex: pre-exorcise document id salvage
> --------------------------------------------
>
> Key: LUCENE-8961
> URL: https://issues.apache.org/jira/browse/LUCENE-8961
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Christine Poerschke
> Priority: Minor
> Attachments: LUCENE-8961.patch
>
>
> The
> [CheckIndex|https://github.com/apache/lucene-solr/blob/releases/lucene-solr/8.2.0/lucene/core/src/java/org/apache/lucene/index/CheckIndex.java]
> tool supports the exorcising of corrupt segments from an index.
> This ticket proposes to add an extra option which could first be used to
> potentially salvage the document ids of the segment(s) about to be exorcised.
> Re-ingestion for those documents could then be arranged so as to repair the
> data damage caused by the exorcising.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
