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

Uwe Schindler edited comment on LUCENE-2446 at 3/31/14 12:44 PM:
-----------------------------------------------------------------

Although its currently only doing file integrity checks, we may extend this 
later! Maybe remove more parts of CheckIndex class and move it to Codec level?

Another idea: Move {{validate()/checkIntegrity()}} up to IndexReader, so it 
would also work on DirectoryReaders? This would help with cleaning up stuff 
from CheckIndex.


was (Author: thetaphi):
Although its currently only doing file integrity checks, we may extend this 
later! Maybe remove more parts of CheckIndex class and move it to Codec level?

Another idea: Move it up to IndexReader, so it would also work on 
DirectoryReaders? This would help with cleaning up stuff from CheckIndex.

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to