[
https://issues.apache.org/jira/browse/LUCENE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2720:
-------------------------------
Attachment: LUCENE-2720-trunk.patch
Modified patch against trunk:
* Added FieldsReader.checkCodeVersion - throws TooOldEx if format is unsupported
* Added ctor to IndexFormatTooOldException which takes a String, so that we can
properly express it's a "2.x" index
* DefaultSegmentInfosReader handles si.getVersion().equals("2.x") by throwing
TooOldEx
After it gets the "green light", I'll produce a 3.1 index and check it in trunk
for TestBackCompat.
> 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
>
> Attachments: LUCENE-2720-3x.patch, LUCENE-2720-trunk.patch,
> LUCENE-2720-trunk.patch
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
