[
https://issues.apache.org/jira/browse/LUCENE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983617#action_12983617
]
Shai Erera commented on LUCENE-2720:
------------------------------------
>From the comments I thought what's left to do is to take care of IndexWriter
>throwing IFTOE when it's opened, but I don't see the min/max versions recorded
>anywhere. I expected to find them in SegmentInfo(s), but they're not. So did I
>miss it, or what's left to do here is the whole nine yards?
> IndexWriter should throw IndexFormatTooOldExc on open, not later during
> optimize/getReader/close
> ------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2720
> URL: https://issues.apache.org/jira/browse/LUCENE-2720
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Reporter: Michael McCandless
> Fix For: 3.1, 4.0
>
>
> Spinoff of LUCENE-2618 and also related to the original issue LUCENE-2523...
> If you open IW on a too-old index, you don't find out until much later that
> the index is too old.
> This is because IW does not go and open segment readers on all segments. It
> only does so when it's time to apply deletes, do merges, open an NRT reader,
> etc.
> This is a serious bug because you can in fact succeed in committing with the
> new major version of Lucene against your too-old index, which is catastrophic
> because suddenly the old Lucene version will no longer open the index, and so
> your index becomes unusable.
--
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: [email protected]
For additional commands, e-mail: [email protected]
