lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Smith (JIRA)" <>
Subject [jira] Updated: (LUCENE-1625) openReaderPassed not populated in CheckIndex.Status.SegmentInfoStatus
Date Wed, 17 Jun 2009 18:50:07 GMT


Tim Smith updated LUCENE-1625:

    Attachment: CheckIndex.patch

Attached patch for exposing all collected stats
(created with svn diff > CheckIndex.patch (please correct me if this is not the right way
(this is my first patch)))

This patch breaks out the testing of field norms, terms, stored fields, and term vectors into
their own methods
it also creates a status object for each one of these tests to make the results transparent

this status object exposes:
* stats previously only available from infoStream
* exception thrown if test fails (null if test was successful)

each SegmentInfoStatus will have these status objects attached

This patch allows that if one of the above tests fails, it will attempt to keep testing (to
find all failures)
any failure will still result in the overall segment being rejected

> openReaderPassed not populated in CheckIndex.Status.SegmentInfoStatus
> ---------------------------------------------------------------------
>                 Key: LUCENE-1625
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.4
>            Reporter: Tim Smith
>         Attachments: CheckIndex.patch
> When using CheckIndex programatically, the openReaderPassed flag on the SegmentInfoStatus
is never populated (so it always comes back false)
> looking at the code, its clear that openReaderPassed is defined, but never used
> furthermore, it appears that not all information that is propagated to the "InfoStream"
is available via SegmentIinfoStatus
> All of the following information should be able to be gather from public properties on
the SegmentInfoStatus:
> test: open reader.........OK
> test: fields, norms.......OK [2 fields]
> test: terms, freq, prox...OK [101 terms; 133 terms/docs pairs; 133 tokens]
> test: stored fields.......OK [100 total field count; avg 1 fields per doc]
> test: term vectors........OK [0 total vector count; avg 0 term/freq vector fields per

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message