You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by us...@apache.org on 2011/06/12 17:35:40 UTC
svn commit: r1134937 - /lucene/dev/trunk/lucene/CHANGES.txt
Author: uschindler
Date: Sun Jun 12 15:35:40 2011
New Revision: 1134937
URL: http://svn.apache.org/viewvc?rev=1134937&view=rev
Log:
Correct and improve some changes entries.
Modified:
lucene/dev/trunk/lucene/CHANGES.txt
Modified: lucene/dev/trunk/lucene/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/CHANGES.txt?rev=1134937&r1=1134936&r2=1134937&view=diff
==============================================================================
--- lucene/dev/trunk/lucene/CHANGES.txt (original)
+++ lucene/dev/trunk/lucene/CHANGES.txt Sun Jun 12 15:35:40 2011
@@ -12,15 +12,15 @@ Changes in backwards compatibility polic
- On upgrading to 3.1, if you do not fully reindex your documents,
Lucene will emulate the new flex API on top of the old index,
incurring some performance cost (up to ~10% slowdown, typically).
- Likewise, if you use the deprecated pre-flex APIs on a newly
- created flex index, this emulation will also incur some
- performance loss.
+ To prevent this slowdown, use oal.index.IndexUpgrader
+ to upgrade your indexes to latest file format (LUCENE-3082).
Mixed flex/pre-flex indexes are perfectly fine -- the two
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
3.1 you can start indexing new documents into an existing index.
- But for best performance you should fully reindex.
+ To get optimal performance, use oal.index.IndexUpgrader
+ to upgrade your indexes to latest file format (LUCENE-3082).
- The postings APIs (TermEnum, TermDocsEnum, TermPositionsEnum)
have been removed in favor of the new flexible