You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by bu...@apache.org on 2015/02/20 19:41:25 UTC
svn commit: r940881 - in /websites/staging/lucene/trunk/content: ./
index.html mainnews.html
Author: buildbot
Date: Fri Feb 20 18:41:24 2015
New Revision: 940881
Log:
Staging update by buildbot for lucene
Modified:
websites/staging/lucene/trunk/content/ (props changed)
websites/staging/lucene/trunk/content/index.html
websites/staging/lucene/trunk/content/mainnews.html
Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Feb 20 18:41:24 2015
@@ -1 +1 @@
-1661186
+1661188
Modified: websites/staging/lucene/trunk/content/index.html
==============================================================================
--- websites/staging/lucene/trunk/content/index.html (original)
+++ websites/staging/lucene/trunk/content/index.html Fri Feb 20 18:41:24 2015
@@ -213,20 +213,24 @@ and Solr can be downloaded from <a href=
<a href="/solr/5_0_0/changes/Changes.html">Solr CHANGES.txt</a> files included
with the release for a full list of details.</p>
<h3 id="highlights-of-the-lucene-release-include">Highlights of the Lucene release include:</h3>
-<p>Stronger index safety
-* All file access now uses Javaâs NIO.2 APIs which give Lucene stronger index safety in terms of better error handling and safer commits.</p>
+<p>Stronger index safety</p>
<ul>
<li>
+<p>All file access now uses Javaâs NIO.2 APIs which give Lucene stronger index safety in terms of better error handling and safer commits.</p>
+</li>
+<li>
<p>Every Lucene segment now stores a unique id per-segment and per-commit to aid in accurate replication of index files.</p>
</li>
<li>
<p>During merging, IndexWriter now always checks the incoming segments for corruption before merging. This can mean, on upgrading to 5.0.0, that merging may uncover long-standing latent corruption in an older 4.x index.</p>
</li>
</ul>
-<p>Reduced heap usage
-* Lucene now supports random-writable and advance-able sparse bitsets (RoaringDocIdSet and SparseFixedBitSet), so the heap required is in proportion to how many bits are set, not how many total documents exist in the index.</p>
+<p>Reduced heap usage</p>
<ul>
<li>
+<p>Lucene now supports random-writable and advance-able sparse bitsets (RoaringDocIdSet and SparseFixedBitSet), so the heap required is in proportion to how many bits are set, not how many total documents exist in the index.</p>
+</li>
+<li>
<p>Heap usage during IndexWriter merging is also much lower with the new Lucene50Codec, since doc values and norms for the segments being merged are no longer fully loaded into heap for all fields; now they are loaded for the one field currently being merged, and then dropped.</p>
</li>
<li>
@@ -236,10 +240,12 @@ with the release for a full list of deta
<p>5.0 has a new API to print a tree structure showing a recursive breakdown of which parts are using how much heap.</p>
</li>
</ul>
-<p>Other features
-* FieldCache is gone (moved to a dedicated UninvertingReader in the misc module). This means when you intend to sort on a field, you should index that field using doc values, which is much faster and less heap consuming than FieldCache.</p>
+<p>Other features</p>
<ul>
<li>
+<p>FieldCache is gone (moved to a dedicated UninvertingReader in the misc module). This means when you intend to sort on a field, you should index that field using doc values, which is much faster and less heap consuming than FieldCache.</p>
+</li>
+<li>
<p>Tokenizers and Analyzers no longer require Reader on init.</p>
</li>
<li>
@@ -293,9 +299,15 @@ with the release for a full list of deta
<li>
<p>Distributed IDF is now supported and can be enabled via the config. Currently, there are four supported implementations for the same:</p>
</li>
-<li>LocalStatsCache: Local document stats.</li>
-<li>ExactStatsCache: One time use aggregation</li>
-<li>ExactSharedStatsCache: Stats shared across requests</li>
+<li>
+<p>LocalStatsCache: Local document stats.</p>
+</li>
+<li>
+<p>ExactStatsCache: One time use aggregation</p>
+</li>
+<li>
+<p>ExactSharedStatsCache: Stats shared across requests</p>
+</li>
<li>
<p>LRUStatsCache: Stats shared in an LRU cache across requests</p>
</li>
Modified: websites/staging/lucene/trunk/content/mainnews.html
==============================================================================
--- websites/staging/lucene/trunk/content/mainnews.html (original)
+++ websites/staging/lucene/trunk/content/mainnews.html Fri Feb 20 18:41:24 2015
@@ -203,20 +203,24 @@ and Solr can be downloaded from <a href=
<a href="/solr/5_0_0/changes/Changes.html">Solr CHANGES.txt</a> files included
with the release for a full list of details.</p>
<h3 id="highlights-of-the-lucene-release-include">Highlights of the Lucene release include:</h3>
-<p>Stronger index safety
-* All file access now uses Javaâs NIO.2 APIs which give Lucene stronger index safety in terms of better error handling and safer commits.</p>
+<p>Stronger index safety</p>
<ul>
<li>
+<p>All file access now uses Javaâs NIO.2 APIs which give Lucene stronger index safety in terms of better error handling and safer commits.</p>
+</li>
+<li>
<p>Every Lucene segment now stores a unique id per-segment and per-commit to aid in accurate replication of index files.</p>
</li>
<li>
<p>During merging, IndexWriter now always checks the incoming segments for corruption before merging. This can mean, on upgrading to 5.0.0, that merging may uncover long-standing latent corruption in an older 4.x index.</p>
</li>
</ul>
-<p>Reduced heap usage
-* Lucene now supports random-writable and advance-able sparse bitsets (RoaringDocIdSet and SparseFixedBitSet), so the heap required is in proportion to how many bits are set, not how many total documents exist in the index.</p>
+<p>Reduced heap usage</p>
<ul>
<li>
+<p>Lucene now supports random-writable and advance-able sparse bitsets (RoaringDocIdSet and SparseFixedBitSet), so the heap required is in proportion to how many bits are set, not how many total documents exist in the index.</p>
+</li>
+<li>
<p>Heap usage during IndexWriter merging is also much lower with the new Lucene50Codec, since doc values and norms for the segments being merged are no longer fully loaded into heap for all fields; now they are loaded for the one field currently being merged, and then dropped.</p>
</li>
<li>
@@ -226,10 +230,12 @@ with the release for a full list of deta
<p>5.0 has a new API to print a tree structure showing a recursive breakdown of which parts are using how much heap.</p>
</li>
</ul>
-<p>Other features
-* FieldCache is gone (moved to a dedicated UninvertingReader in the misc module). This means when you intend to sort on a field, you should index that field using doc values, which is much faster and less heap consuming than FieldCache.</p>
+<p>Other features</p>
<ul>
<li>
+<p>FieldCache is gone (moved to a dedicated UninvertingReader in the misc module). This means when you intend to sort on a field, you should index that field using doc values, which is much faster and less heap consuming than FieldCache.</p>
+</li>
+<li>
<p>Tokenizers and Analyzers no longer require Reader on init.</p>
</li>
<li>
@@ -283,9 +289,15 @@ with the release for a full list of deta
<li>
<p>Distributed IDF is now supported and can be enabled via the config. Currently, there are four supported implementations for the same:</p>
</li>
-<li>LocalStatsCache: Local document stats.</li>
-<li>ExactStatsCache: One time use aggregation</li>
-<li>ExactSharedStatsCache: Stats shared across requests</li>
+<li>
+<p>LocalStatsCache: Local document stats.</p>
+</li>
+<li>
+<p>ExactStatsCache: One time use aggregation</p>
+</li>
+<li>
+<p>ExactSharedStatsCache: Stats shared across requests</p>
+</li>
<li>
<p>LRUStatsCache: Stats shared in an LRU cache across requests</p>
</li>