You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2015/03/06 04:39:38 UTC
[jira] [Commented] (LUCENE-6341) add CheckIndex -fast option
[ https://issues.apache.org/jira/browse/LUCENE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349901#comment-14349901 ]
Robert Muir commented on LUCENE-6341:
-------------------------------------
For trunk, i think something like this patch is ok? The user gets a pretty solid check with the option, and its fast.
On 5.x i have concerns. For lucene 4.0-4.7 segments, which are supported there, the option is kind of trappy, maybe just a warning beside the option's usage() in 5.x branch is ok since its not set by default anyway?
> add CheckIndex -fast option
> ---------------------------
>
> Key: LUCENE-6341
> URL: https://issues.apache.org/jira/browse/LUCENE-6341
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Robert Muir
> Attachments: LUCENE-6341.patch
>
>
> CheckIndex is great for testing and when tracking down lucene bugs.
> But in cases where users just want to verify their index files are OK, it is very slow and expensive.
> I think we should add a -fast option, that only opens the reader and calls checkIntegrity(). This means all files are the correct files (identifiers match) and have the correct CRC32 checksums.
> For our 10M doc wikipedia index, this is the difference between a 2 second check and a 2 minute check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org