lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-3138) IW.addIndexes should fail fast if an index is too old/new
Date Tue, 24 May 2011 15:10:47 GMT

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

Shai Erera updated LUCENE-3138:
-------------------------------

    Fix Version/s: 3.2

bq. It also applies to 3.x? Ie if you try to add a 4.x index in a 3.x world you should get
too-new-exc?

You're right :). Added 3.2 as fix version too.

> IW.addIndexes should fail fast if an index is too old/new
> ---------------------------------------------------------
>
>                 Key: LUCENE-3138
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3138
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: core/index
>            Reporter: Shai Erera
>            Priority: Minor
>             Fix For: 3.2, 4.0
>
>
> Today IW.addIndexes (both Dir and IR versions) do not check the format of the incoming
indexes. Therefore it could add a too old/new index and the app will discover that only later,
maybe during commit() or segment merges. We should check that up front and fail fast.
> This issue is relevant only to 4.0 at the moment, which will not support 2.x indexes
anymore.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message