Yonik Seeley wrote: > Perhaps add something to the effect that autoCommit=false was a new > 2.3 feature, so it's only those who actually started using it who were > at risk? >
autoCommit=false was already introduced in 2.2.0, so also people who are upgrading from 2.2.0 might be at risk. But I can still mention that autoCommit is a quite new feature and that by default autoCommit=true is used. Attached an updated version of the draft. -Michael DRAFT: Release 2.3.1 of Lucene Java is now available! This release contains fixes for serious bugs in 2.3.0 that could cause index corruptions in autoCommit=false mode. The autoCommit option was added to IndexWriter with release 2.2.0. If not explicitly set to false, the IndexWriter runs in autoCommit=true mode. 2.3.1 does not contain any new features, API or file format changes, which makes it fully compatible to 2.3.0. We would like to encourage everyone who currently uses Lucene Java 2.3.0 to upgrade to 2.3.1 to prevent possible index corruptions! The detailed change log is at: http://svn.apache.org/repos/asf/lucene/java/tags/lucene_2_3_1/CHANGES.txt Binary and source distributions are available at http://www.apache.org/dyn/closer.cgi/lucene/java/ Lucene artifacts are also available in the Maven2 repository at http://repo1.maven.org/maven2/org/apache/lucene/ -Michael (on behalf of the Lucene team) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
