[jira] [Reopened] (LUCENE-6341) add CheckIndex -fast option

["Robert Muir (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir reopened LUCENE-6341:
---------------------------------

I think I know of a good solution for backporting.

My problem is here at the end: 

{code}
    if (result.clean) {
      msg(infoStream, "No problems were detected with this index.\n");
    }
{code}

I think if the -fast option is used, and we find segments older than 5.0 we can emit a warning right here. If we find any older than 4.8 it could be a much stronger warning. In either case it just recommends to do a full checkindex to be sure.

> 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
>             Fix For: Trunk
>
>         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