[
https://issues.apache.org/jira/browse/LUCENE-8961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921391#comment-16921391
]
Christine Poerschke commented on LUCENE-8961:
---------------------------------------------
Thanks [~jpountz] for your input.
The latest attached patch facilitates potential salvaging of terms by making
the {{CheckIndex}} class extensible so that developer's own deriving classes
could:
* customise the checkIntegrity call
* filter the fields being checked
* intercept any (field,term) pairs e.g. for logging purposes
It seems to me to be a rather awkward change though and if out-of-the-box
{{CheckIndex}} would not support id salvaging then a stand-alone tool just for
that purpose might be a cleaner solution? Either way, I won't have bandwidth to
pursue this further in the near future i.e. just sharing things 'as is' in case
it might help others in the meantime.
> 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, 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
