lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (LUCENE-1920) Make MultiReader.isOptimized() return a useful result
Date Fri, 18 Sep 2009 16:42:16 GMT


Yonik Seeley commented on LUCENE-1920:

I agree with the patch - MulitReader is not used by Lucene natively, so it's always instantiated
by a user with multiple sub-readers, that are normally complete indexes on their own.  If
they are all optimized, then the top-level should be optimized.

It's minor though, because the user could also check the optimization status of the sub-readers

As for instantiatedIndex, that's a different issue - I don't know why it thinks it needs an
optimized index (no deletions? single segment? both?) but it should check a different way.

> Make MultiReader.isOptimized() return a useful result
> -----------------------------------------------------
>                 Key: LUCENE-1920
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Bernd Fondermann
>            Priority: Minor
>         Attachments: MultiReader_isOptimized.patch
> The MultiReader statically returns FALSE on any isOptimized() call.
> This makes it unusable as the source index for an InstantiatedIndex, which checks initially
if the source index is optimized and aborts if not.
> The attached patch iterates all sub readers and returns TRUE if all of them are optimized.

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