[
https://issues.apache.org/jira/browse/LUCENE-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956206#comment-13956206
]
Uwe Schindler commented on LUCENE-2446:
---------------------------------------
One idea to make the whole thing more hidden to the user:
I am not sure if we need the abstract checkIntegrity() on the public
AtomicReader abstract interface - because it only applies to disk-based
indexes. Would it be not enough to have it on SegmentReader? I know we might
need some instanceof checks while merging, but I think we do those already. By
that it would not be public and we can hide it to the user. We would only not
validate on FilterAtomicReader's merging (split / sort indexes).
Any opinion about this?
> Add checksums to Lucene segment files
> -------------------------------------
>
> Key: LUCENE-2446
> URL: https://issues.apache.org/jira/browse/LUCENE-2446
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Lance Norskog
> Labels: checksum
> Attachments: LUCENE-2446.patch
>
>
> It would be useful for the different files in a Lucene index to include
> checksums. This would make it easy to spot corruption while copying index
> files around; the various cloud efforts assume many more data-copying
> operations than older single-index implementations.
> This feature might be much easier to implement if all index files are created
> in a sequential fashion. This issue therefore depends on [LUCENE-2373].
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
