fix wrong version number in changes entry

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1353702 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Robert Muir 2012-06-25 19:10:04 +00:00
parent 7c26573fe3
commit 0b4cae1b5e
1 changed files with 2 additions and 2 deletions

View File

@ -20,7 +20,7 @@ Changes in backwards compatibility policy
* LUCENE-1458, LUCENE-2111, LUCENE-2354: Changes from flexible indexing: * LUCENE-1458, LUCENE-2111, LUCENE-2354: Changes from flexible indexing:
- On upgrading to 3.1, if you do not fully reindex your documents, - On upgrading to 4.0, if you do not fully reindex your documents,
Lucene will emulate the new flex API on top of the old index, Lucene will emulate the new flex API on top of the old index,
incurring some performance cost (up to ~10% slowdown, typically). incurring some performance cost (up to ~10% slowdown, typically).
To prevent this slowdown, use oal.index.IndexUpgrader To prevent this slowdown, use oal.index.IndexUpgrader
@ -29,7 +29,7 @@ Changes in backwards compatibility policy
Mixed flex/pre-flex indexes are perfectly fine -- the two Mixed flex/pre-flex indexes are perfectly fine -- the two
emulation layers (flex API on pre-flex index, and pre-flex API on emulation layers (flex API on pre-flex index, and pre-flex API on
flex index) will remap the access as required. So on upgrading to flex index) will remap the access as required. So on upgrading to
3.1 you can start indexing new documents into an existing index. 4.0 you can start indexing new documents into an existing index.
To get optimal performance, use oal.index.IndexUpgrader To get optimal performance, use oal.index.IndexUpgrader
to upgrade your indexes to latest file format (LUCENE-3082). to upgrade your indexes to latest file format (LUCENE-3082).