lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r805429 - in /websites/production/lucene/content: core/index.html index.html solr/index.html
Date Mon, 20 Feb 2012 02:15:46 GMT
Author: buildbot
Date: Mon Feb 20 02:15:45 2012
New Revision: 805429

Log:
Production update by buildbot for lucene

Modified:
    websites/production/lucene/content/core/index.html
    websites/production/lucene/content/index.html
    websites/production/lucene/content/solr/index.html

Modified: websites/production/lucene/content/core/index.html
==============================================================================
--- websites/production/lucene/content/core/index.html (original)
+++ websites/production/lucene/content/core/index.html Mon Feb 20 02:15:45 2012
@@ -116,7 +116,7 @@
   
 <ul>
   <li><a href="index.html">Core</a></li>
-  <li><a href="features.html">Features</a></li>
+  <li><a href="corenews.html">News</a></li>
   <li><a href="downloads.html">Download</a></li>
   <li><a href="documentation.html">Documentation</a></li>
   <li><a href="quickstart.html">Tutorials</a></li>
@@ -207,252 +207,34 @@
       <div><p>Apache Lucene(TM) is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.</p>
 <p>Apache Lucene is an open source project available for free download. Please use the links on the right to access Lucene.</p></div>
       
-<div><h1 id="lucene_core_news">Lucene Core News</h1>
-<h2 id="27_november_2011_-_lucene_core_350">27 November 2011 - Lucene Core 3.5.0</h2>
-<p>The Lucene PMC is pleased to announce the availability
-of Apache Lucene 3.5.0.</p>
-<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>Highlights of the Lucene release include:</p>
-<ul>
-<li>
-<p>Added a very substantial (3-5X) RAM reduction required to hold the
-terms index on opening an IndexReader. (<a href="https://issues.apache.org/jira/browse/LUCENE-2205">LUCENE-2205</a>)</p>
-</li>
-<li>
-<p>Added IndexSearcher.searchAfter which returns results after a
-specified ScoreDoc (e.g. last document on the previous page) to
-support deep paging use cases.
-(<a href="https://issues.apache.org/jira/browse/LUCENE-2215">LUCENE-2215</a>)</p>
-</li>
-<li>
-<p>Added SearcherManager to manage sharing and reopening IndexSearchers
-across multiple search threads. Underlying IndexReader instances are
-safely closed if not referenced anymore.
-(<a href="https://issues.apache.org/jira/browse/LUCENE-3445">LUCENE-3445</a>,
-<a href="https://issues.apache.org/jira/browse/LUCENE-3558">LUCENE-3558</a>)</p>
-</li>
-<li>
-<p>Added SearcherLifetimeManager which safely provides a consistent
-view of the index across multiple requests (e.g. paging/drilldown).
-(<a href="https://issues.apache.org/jira/browse/LUCENE-3558">LUCENE-3558</a>,
-<a href="https://issues.apache.org/jira/browse/LUCENE-3486">LUCENE-3486</a>)</p>
-</li>
-<li>
-<p>Renamed IndexWriter.optimize to forceMerge to discourage use of
-this method since it is horribly costly and rarely justified anymore.
-(<a href="https://issues.apache.org/jira/browse/LUCENE-3454">LUCENE-3454</a>)</p>
-</li>
-<li>
-<p>Added NGramPhraseQuery that speeds up phrase queries 30-50% when
- n-gram analysis is used. (<a href="https://issues.apache.org/jira/browse/LUCENE-3426">LUCENE-3426</a>)</p>
-</li>
-<li>
-<p>Added a new reopen API (IndexReader.openIfChanged) that returns
-null instead of the old reader if there are no changes in the index.
-(<a href="https://issues.apache.org/jira/browse/LUCENE-3464">LUCENE-3464</a>)</p>
-</li>
-<li>
-<p>Improvements to vector highlighting: support for more queries
-such as wildcards and boundary analysis for generated snippets.
-(<a href="https://issues.apache.org/jira/browse/LUCENE-1824">LUCENE-1824</a>,
-<a href="https://issues.apache.org/jira/browse/LUCENE-1889">LUCENE-1889</a>)</p>
-</li>
-<li>
-<p>IndexSearcher and IndexReader now perform additional checks to
-throw AlreadyClosedExceptions if searches are performed on a
-closed IndexReader. Performing searches on already closed reader can
-cause JVM crashes when invalid memory mapped files are referenced.</p>
-</li>
-<li>
-<p>Several bugfixes, including a bug where closing an NRT reader
-after the writer was closed was incorrectly invoking the
-DeletionPolicy. See CHANGES.txt entries for full details.</p>
-</li>
-</ul>
-<h2 id="26_october_2011_-_java_7u1_fixes_index_corruption_and_crash_bugs_in_apache_lucene_core_and_apache_solrtitle">26 October 2011 - Java 7u1 fixes index corruption and crash bugs in Apache Lucene Core and Apache Solr</title></h2>
-<p>Oracle released <a href="http://www.oracle.com/technetwork/java/javase/7u1-relnotes-507962.html">Java 7u1</a> on October 19.
-  According to the release notes and tests done by the Lucene committers, all bugs reported on July 28 are fixed in this release,
-  so code using Porter stemmer no longer crashes with <code  class="inline">SIGSEGV</code>. We were not able to experience any index corruption anymore,
-  so it is safe to use Java 7u1 with Lucene Core and Solr.
-  On the same day, Oracle released <a href="http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html">Java 6u29</a>
-  fixing the same problems occurring with Java 6, if the JVM switches <code  class="inline">-XX:+AggressiveOpts</code>
-  or <code  class="inline">-XX:+OptimizeStringConcat</code> were used. Of course, you should <strong>not</strong> use experimental JVM options like
-  <code  class="inline">-XX:+AggressiveOpts</code> in production environments! We recommend everybody to upgrade to this latest version 6u29.
-  In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
-  version shipped with Java 7 changed and tokenization behaves differently
-  (e.g. lowercasing). For more information, read <code  class="inline">JRE_VERSION_MIGRATION.txt</code>
-  in your distribution package!</p>
-<h2 id="14_september_2011_-_lucene_core_340title">14 September 2011 - Lucene Core 3.4.0</title></h2>
-<p>The Lucene PMC is pleased to announce the availability
- of Apache Lucene 3.4.0.</p>
-<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>If you are already using Apache Lucene 3.1, 3.2 or 3.3, we strongly recommend you upgrade to 3.4.0 because of the index corruption bug on OS or computer crash or power loss (<a href="https://issues.apache.org/jira/browse/LUCENE-3418">LUCENE-3418</a>), now fixed in 3.4.0.</p>
-<p>Highlights of the Lucene release include:</p>
-<ul>
-<li>
-<p>Fixed a major bug (<a href="https://issues.apache.org/jira/browse/LUCENE-3418">LUCENE-3418</a>) whereby a Lucene index could
-easily become corrupted if the OS or computer crashed or lost
-power.</p>
-</li>
-<li>
-<p>Added a new faceting module (<code  class="inline">contrib/facet</code>) for computing facet
-counts (both hierarchical and non-hierarchical) at search
-time (<a href="https://issues.apache.org/jira/browse/LUCENE-3079">LUCENE-3079</a>).</p>
-</li>
-<li>
-<p>Added a new join module (<code  class="inline">contrib/join</code>), enabling indexing and
-searching of nested (parent/child) documents using
-<code  class="inline">BlockJoinQuery</code>/<code  class="inline">Collector</code> (<a href="https://issues.apache.org/jira/browse/LUCENE-3171">LUCENE-3171</a>).</p>
-</li>
-<li>
-<p>It is now possible to index documents with term frequencies
-included but without positions (<a href="https://issues.apache.org/jira/browse/LUCENE-2048">LUCENE-2048</a>); previously
-<code  class="inline">omitTermFreqAndPositions</code> always omitted both.</p>
-</li>
-<li>
-<p>The modular <code  class="inline">QueryParser</code> (<code  class="inline">contrib/queryparser</code>) can now create
-<code  class="inline">NumericRangeQuery</code>.</p>
-</li>
-<li>
-<p>Added SynonymFilter, in <code  class="inline">contrib/analyzers</code>, to apply multi-word
-synonyms during indexing or querying, including parsers to read
-the wordnet and solr synonym formats (<a href="https://issues.apache.org/jira/browse/LUCENE-3233">LUCENE-3233</a>).</p>
-</li>
-<li>
-<p>You can now control how documents that don't have a value on the
-sort field should sort (<a href="https://issues.apache.org/jira/browse/LUCENE-3390">LUCENE-3390</a>), using <code  class="inline">SortField.setMissingValue</code>.</p>
-</li>
-<li>
-<p>Fixed a case where term vectors could be silently deleted from the
-index after <code  class="inline">addIndexes</code> (<a href="https://issues.apache.org/jira/browse/LUCENE-3402">LUCENE-3402</a>).</p>
-</li>
-</ul>
-<h2 id="28_july_2011_-_warning_index_corruption_and_crashes_in_apache_lucene_core__apache_solr_with_java_7">28 July 2011 - WARNING: Index corruption and crashes in Apache Lucene Core / Apache Solr with Java 7</h2>
-<p>Oracle released <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java 7</a> today.
-Unfortunately it contains hotspot compiler optimizations, which miscompile some loops.
-This can affect code of several Apache projects. Sometimes JVMs only crash, but in several cases,
-results calculated can be incorrect, leading to bugs in applications
-(see Hotspot bugs <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134">7070134</a>,
-<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7044738">7044738</a>,
-<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7068051">7068051</a>).
-<strong>Apache Lucene Core</strong> and <strong>Apache Solr</strong> are two Apache projects,
-which are affected by these bugs, namely all versions released until today.
-Solr users with the default configuration will have
-Java crashing with <code  class="inline">SIGSEGV</code> as soon as they start to index documents, as one
-affected part is the well-known Porter stemmer
-(see <a href="https://issues.apache.org/jira/browse/LUCENE-3335">LUCENE-3335</a>).
-Other loops in Lucene may be miscompiled, too, leading to index corruption
-(especially on Lucene trunk with pulsing codec; other loops may be
-affected, too - <a href="https://issues.apache.org/jira/browse/LUCENE-3346">LUCENE-3346</a>).
-These problems were detected only 5 days before the official Java 7 release,
-so Oracle had no time to fix those bugs, affecting also many more applications.
-In response to our questions, they proposed to include the fixes into service
-release u2 (eventually into service release u1, see
-<a href="http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2011-July/005971.html">this mail</a>).
-<strong>This means you cannot use Apache Lucene/Solr with Java 7 releases before Update 2!</strong>
-If you do, please don't open bug reports, it is not the committers' fault!
-At least disable loop optimizations using the <code  class="inline">-XX:-UseLoopPredicate</code> JVM option
-to not risk index corruptions.
-<em>Please note:</em> Also Java 6 users are affected, if they use one of those
-JVM options, which are <strong>not</strong> enabled by default: <code  class="inline">-XX:+OptimizeStringConcat</code>
-or <code  class="inline">-XX:+AggressiveOpts</code>.
-It is strongly recommended not to use any hotspot optimization switches in any Java
-version without extensive testing!
-In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
-version shipped with Java 7 changed and tokenization behaves differently
-(e.g. lowercasing). For more information, read <code  class="inline">JRE_VERSION_MIGRATION.txt</code>
-in your distribution package!</p>
-<h2 id="1_july_2011_-_lucene_core_33">1 July 2011 - Lucene Core 3.3</h2>
-<p>The Lucene PMC is pleased to announce the availability
-of Apache Lucene 3.3.</p>
-<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a>
-Highlights of the Lucene release include:</p>
-<ul>
-<li>The spellchecker module now includes suggest/auto-complete functionality,
-       with three implementations: Jaspell, Ternary Trie, and Finite State.</li>
-<li>Support for merging results from multiple shards, for both "normal"
-       search results (TopDocs.merge) as well as grouped results using the
-       grouping module (SearchGroup.merge, TopGroups.merge).</li>
-<li>An optimized implementation of KStem, a less aggressive stemmer
-       for English</li>
-<li>Single-pass grouping implementation based on block document indexing.</li>
-<li>Improvements to MMapDirectory (now also the default implementation
-       returned by FSDirectory.open on 64-bit Linux).</li>
-<li>NRTManager simplifies handling near-real-time search with multiple
-       search threads, allowing the application to control which indexing
-       changes must be visible to which search requests.</li>
-<li>TwoPhaseCommitTool facilitates performing a multi-resource
-       two-phased commit, including IndexWriter.</li>
-<li>The default merge policy, TieredMergePolicy, has a new method
-       (set/getReclaimDeletesWeight) to control how aggressively it
-       targets segments with deletions, and is now more aggressive than
-       before by default.</li>
-<li>PKIndexSplitter tool splits an index by a mid-point term.</li>
+<div><h1 id="features">Features</h1>
+<p>Lucene offers powerful features through a simple API:</p>
+<h2 id="scalable_high-performance_indexing">Scalable, High-Performance Indexing</h2>
+<ul>
+<li>over 95GB/hour on modern hardware<br/></li>
+<li>small RAM requirements -- only 1MB heap</li>
+<li>incremental indexing as fast as batch indexing</li>
+<li>index size roughly 20-30% the size of text indexed</li>
 </ul>
-<h2 id="4_june_2011_-_lucene_core_32">4 June 2011 - Lucene Core 3.2</h2>
-<p>The Lucene PMC is pleased to announce the availability of Apache Lucene 3.2.</p>
-<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a>
-Highlights of the Lucene release include:</p>
+<h2 id="powerful_accurate_and_efficient_search_algorithms">Powerful, Accurate and Efficient Search Algorithms</h2>
 <ul>
-<li>A new grouping module, under lucene/contrib/grouping, enables
-       search results to be grouped by a single-valued indexed field</li>
-<li>A new IndexUpgrader tool fully converts an old index to the
-       current format.</li>
-<li>A new Directory implementation, NRTCachingDirectory, caches small
-       segments in RAM, to reduce the I/O load for applications with fast
-       NRT reopen rates.</li>
-<li>A new Collector implementation, CachingCollector, is able to
-       gather search hits (document IDs and optionally also scores) and
-       then replay them.  This is useful for Collectors that require two
-       or more passes to produce results.</li>
-<li>Index a document block using IndexWriter's new addDocuments or
-       updateDocuments methods.  These experimental APIs ensure that the
-       block of documents will forever remain contiguous in the index,
-       enabling interesting future features like grouping and joins.</li>
-<li>A new default merge policy, TieredMergePolicy, which is more
-       efficient due to being able to merge non-contiguous segments.
-       See <a href="http://s.apache.org/merging">http://s.apache.org/merging</a> for details.</li>
-<li>NumericField is now returned correctly when you load a stored
-       document (previously you received a normal Field back, with the
-       numeric value converted string).</li>
-<li>Deleted terms are now applied during flushing to the newly flushed
-       segment, which is more efficient than having to later initialize a
-       reader for that segment.</li>
+<li>ranked searching -- best results returned first</li>
+<li>many powerful query types: phrase queries, wildcard queries, proximity
+    queries, range queries and more</li>
+<li>fielded searching (e.g., title, author, contents)</li>
+<li>date-range searching</li>
+<li>sorting by any field</li>
+<li>multiple-index searching with merged results</li>
+<li>allows simultaneous update and searching</li>
 </ul>
-<h2 id="31_march_2011_-_lucene_core_31">31 March 2011 - Lucene Core 3.1</h2>
-<p>The Lucene PMC is pleased to announce the availability of Apache Lucene 3.1.</p>
-<p>Lucene can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/java/">http://www.apache.org/dyn/closer.cgi/lucene/java/</a> and Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a>
-Highlights of the Lucene release include:</p>
+<h2 id="cross-platform_solution">Cross-Platform Solution</h2>
 <ul>
-<li>Numerous performance improvements: faster exact PhraseQuery; merging
-favors segments with deletions; primary key lookup is faster;
-IndexWriter.addIndexes(Directory[]) uses file copy instead of
-merging; various Directory performance improvements; compound file
-is dynamically turned off for large segments; fully deleted segments
-are dropped on commit; faster snowball analyzers (in contrib);
-ConcurrentMergeScheduler is more careful about setting priority of
-merge threads.</li>
-<li>ReusableAnalyzerBase makes it easier to reuse TokenStreams
-correctly.</li>
-<li>Improved Analysis capabilities: Improved Unicode support, including
-Unicode 4, more friendly term handling (CharTermAttribute), easier
-object reuse and better support for protected words in lossy token
-filters (e.g. stemmers).</li>
-<li>ConstantScoreQuery now allows directly wrapping a Query.</li>
-<li>IndexWriter is now configured with a new separate builder API,
-IndexWriterConfig.  You can now control IndexWriter's previously
-fixed internal thread limit by calling setMaxThreadStates.</li>
-<li>IndexWriter.getReader is replaced by IndexReader.open(IndexWriter).
-In addition you can now specify whether deletes should be resolved
-when you open an NRT reader.</li>
-<li>MultiSearcher is deprecated; ParallelMultiSearcher has been
-absorbed directly into IndexSearcher.</li>
-<li>On 64bit Windows and Solaris JVMs, MMapDirectory is now the
-default implementation (returned by FSDirectory.open).
-MMapDirectory also enables unmapping if the JVM supports it.</li>
-<li>New TotalHitCountCollector just counts total number of hits.</li>
-<li>ReaderFinishedListener API enables external caches to evict entries
-once a segment is finished.</li>
+<li>Available as Open Source software under the
+    <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License</a>
+    which lets you use Lucene in both commercial and Open Source programs</li>
+<li>100%-pure Java</li>
+<li>Implementations <a href="http://wiki.apache.org/lucene-java/LuceneImplementations">in other
+    programming languages available</a> that are index-compatible</li>
 </ul></div>
 
 
@@ -514,6 +296,12 @@ once a segment is finished.</li>
       <div class="status-item">
       
       <div class="section-content">
+        <a class="svn" href="http://svn.apache.org/viewvc?revision=1291115;view=revision">r1291115</a>
+        <a href="https://issues.apache.org/jira/browse/SOLR-3142">SOLR-3142</a>: don't auto-optimize in dataimports (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
+        <a href="http://people.apache.org/committer-index.html#rmuir">rmuir</a>
+      </div>
+    
+      <div class="section-content">
         <a class="svn" href="http://svn.apache.org/viewvc?revision=1291097;view=revision">r1291097</a>
         Remove volatile from IR.closed variable (its only used in already synchronized close() method) (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
         <a href="http://people.apache.org/committer-index.html#uschindler">uschindler</a>
@@ -536,18 +324,17 @@ once a segment is finished.</li>
         <a href="https://issues.apache.org/jira/browse/LUCENE-3714">LUCENE-3714</a>: add weighted FST suggester impl (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
         <a href="http://people.apache.org/committer-index.html#rmuir">rmuir</a>
       </div>
-    
-      <div class="section-content">
-        <a class="svn" href="http://svn.apache.org/viewvc?revision=1291003;view=revision">r1291003</a>
-        <a href="https://issues.apache.org/jira/browse/SOLR-3126">SOLR-3126</a>: test changes to handle deletes surviving restart (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
-        <a href="http://people.apache.org/committer-index.html#yonik">yonik</a>
-      </div>
     </div></div>
     
     
     <div id="jira">
       <h1>Latest JIRA</h1>
       <div class="status-item">
+      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3804">[LUCENE-3804] Swap Features and News on the website.</a><br/>
+       <div class="section-content">
+        <p>I think we can do even better, but that is a nice, easy incremental improvement.</p>
+       </div>
+    
       <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3803">[LUCENE-3803] Using a searcher with an executor service does not work from within a Callable called by that same executor service</a><br/>
        <div class="section-content">
         <p>The test case I&apos;m about to attach creates an executor service uses invokeAll to run things from it. The &apos;things&apos;...</p>
@@ -571,38 +358,32 @@ fails because the inner reader is closed
 <ul class="alternate" type="square">
 	<li>dynamic...</li></ul>
        </div>
-    
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3801">[LUCENE-3801] Generify FST shortestPaths() to take a comparator</a><br/>
-       <div class="section-content">
-        <p>Not sure we should do this, it costs 5-10% performance for WFSTSuggester.<br/>
-But maybe we can optimize something here, or...</p>
-       </div>
     </div></div>
     
     
     <div id="dev-mail">
       <h1>Latest Dev</h1>
       <div class="status-item">
-      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c144116534.1276.1329697234363.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c988961348.1373.1329701314321.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
         <div class="section-content">
-        [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211616#comment-13211616">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211616#comment-13211616</a>
-] <br />&nbsp;<br />Yonik Seeley commented on SOLR-3141:
-------------------------------------<br />&nbsp;<br />A slight improvement in name does not come anywhere...
+        [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211626#comment-13211626">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211626#comment-13211626</a>
+] <br />&nbsp;<br />Robert Muir commented on SOLR-3141:
+-----------------------------------<br />&nbsp;<br />{quote}
+A slight improvement in name does not come...
         </div>
       
-      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c951795337.1243.1329696636539.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c623503952.1366.1329700834282.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (LUCENE-3803) Using a searcher with an executor service does not work from within a Callable called by that same executor service</a></h4>
         <div class="section-content">
-        [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211611#comment-13211611">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211611#comment-13211611</a>
-] <br />&nbsp;<br />Uwe Schindler commented on SOLR-3141:
--------------------------------------<br />&nbsp;<br />bq. I doubt it. An dhow did they find...
+        [ <a href="https://issues.apache.org/jira/browse/LUCENE-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211624#comment-13211624">https://issues.apache.org/jira/browse/LUCENE-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211624#comment-13211624</a>
+] <br />&nbsp;<br />Robert Muir commented on LUCENE-3803:
+-------------------------------------<br />&nbsp;<br />This is not really related to your problem (somewhat)...
         </div>
       
-      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c614733919.1230.1329696154551.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c2011272015.1364.1329700042509.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Assigned] (SOLR-3080) We should consider removing shard info from Zk when you explicitly unload a SolrCore.</a></h4>
         <div class="section-content">
-        [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211609#comment-13211609">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211609#comment-13211609</a>
-] <br />&nbsp;<br />Robert Muir commented on SOLR-3141:
------------------------------------<br />&nbsp;<br />{quote}
-twice that many visit the download page... but...
+        [ <a href="https://issues.apache.org/jira/browse/SOLR-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel">https://issues.apache.org/jira/browse/SOLR-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a>
+]<br />&nbsp;<br />Mark Miller reassigned SOLR-3080:
+---------------------------------<br />&nbsp;<br />    Assignee: Sami Siren  (was: Mark Miller)<br />&nbsp;<br />All yours Sami....
         </div>
       </div>
     </div>
@@ -611,24 +392,23 @@ twice that many visit the download page.
     <div id="core-user-mail">
       <h1>Latest Core User</h1>
       <div class="status-item">
-      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3cCALhtWkfdDBzbJ2gqqNXP2Ks-U6y-5Pmx2B29F3FmTrzVCvjT-Q@mail.gmail.com%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
+      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3c000b01ccef6c$1371bff0$3a553fd0$@thetaphi.de%3e">RE: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
         <div class="section-content">
-        Conveniently, all the 'wrong-result' problems disappeared when I
-followed your advice about counting hits.<br />&nbsp;<br />On Sun, Feb 19, 2012...
+        See my response. The problem is not in Lucene; its in general a problem of fixed thread pools
+that execute...
         </div>
       
-      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3c4F414393.1030506@gmail.com%3e">Implement a custom similarity</a></h4>
+      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3cCALhtWkei0jqx1gQ_1KUWxF8J5zbDy4Y7uTLc=mTVa_k+3jrz=A@mail.gmail.com%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
         <div class="section-content">
-        Hello,
-I am really new to Lucene, last week through this list i was really 
-successfull into finding a solution...
+        See <a href="https://issues.apache.org/jira/browse/LUCENE-3803">https://issues.apache.org/jira/browse/LUCENE-3803</a> for an example
+of the hang. I think this nets out to pilot error, but maybe Javadoc
+could...
         </div>
       
-      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3c8333493708831977755@unknownmsgid%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
+      <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3cCALhtWkfdDBzbJ2gqqNXP2Ks-U6y-5Pmx2B29F3FmTrzVCvjT-Q@mail.gmail.com%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
         <div class="section-content">
-        and there was a dumb typo.<br />&nbsp;<br />1 thread: hang
-2 threads: hang
-3 or more: no hang<br />&nbsp;<br />On...
+        Conveniently, all the 'wrong-result' problems disappeared when I
+followed your advice about counting hits.<br />&nbsp;<br />On Sun, Feb 19, 2012...
         </div>
       </div>
     </div>

Modified: websites/production/lucene/content/index.html
==============================================================================
--- websites/production/lucene/content/index.html (original)
+++ websites/production/lucene/content/index.html Mon Feb 20 02:15:45 2012
@@ -631,21 +631,21 @@ as well as new analysis capabilities.</l
         <div id="dev-mail">
           <h1>Latest Dev</h1>
           <div class="status-item">
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c144116534.1276.1329697234363.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c988961348.1373.1329701314321.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
           
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c951795337.1243.1329696636539.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c623503952.1366.1329700834282.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (LUCENE-3803) Using a searcher with an executor service does not work from within a Callable called by that same executor service</a></h4>
           
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c614733919.1230.1329696154551.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c2011272015.1364.1329700042509.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Assigned] (SOLR-3080) We should consider removing shard info from Zk when you explicitly unload a SolrCore.</a></h4>
           </div>
         </div>
         <div id="core-user-mail">
           <h1>Latest Core User</h1>
           <div class="status-item">
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3cCALhtWkfdDBzbJ2gqqNXP2Ks-U6y-5Pmx2B29F3FmTrzVCvjT-Q@mail.gmail.com%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3c000b01ccef6c$1371bff0$3a553fd0$@thetaphi.de%3e">RE: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
           
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3c4F414393.1030506@gmail.com%3e">Implement a custom similarity</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3cCALhtWkei0jqx1gQ_1KUWxF8J5zbDy4Y7uTLc=mTVa_k+3jrz=A@mail.gmail.com%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
           
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3c8333493708831977755@unknownmsgid%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-java-user/201202.mbox/%3cCALhtWkfdDBzbJ2gqqNXP2Ks-U6y-5Pmx2B29F3FmTrzVCvjT-Q@mail.gmail.com%3e">Re: Hanging with fixed thread pool in the IndexSearcher multithread code</a></h4>
           </div>
         </div>
         <div id="solr-user-mail">

Modified: websites/production/lucene/content/solr/index.html
==============================================================================
--- websites/production/lucene/content/solr/index.html (original)
+++ websites/production/lucene/content/solr/index.html Mon Feb 20 02:15:45 2012
@@ -117,7 +117,7 @@
       
   <ul>
   <li><a href="index.html">Solr</a></li>
-  <li><a href="features.html">Features</a></li>
+  <li><a href="solrnews.html">News</a></li>
   <li><a href="wiki.html">Wiki</a></li>
   <li><a href="downloads.html">Download</a></li>
   <li><a href="tutorial.html">Tutorial</a></li>
@@ -231,207 +231,117 @@
 <p>See the complete feature list for more details.</p>
 <p>For more information about Solr, please see the Solr wiki.</p></div>
       
-<div><h1 id="solr_news">Solr News</h1>
-<h2 id="27_november_2011_-_solr_350_available">27 November 2011 - Solr 3.5.0 Available</h2>
-<p>The Lucene PMC is pleased to announce the availability
-of Apache Solr 3.5.0.</p>
-<p>Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>Highlights of the Solr release include:</p>
-<ul>
-<li>
-<p>Bug fixes and improvements from Apache Lucene 3.5.0, including a
-    very substantial (3-5X) RAM reduction required to hold the terms
-    index on opening an <code  class="inline">IndexReader</code>.
-    (<a href="https://issues.apache.org/jira/browse/LUCENE-2205">LUCENE-2205</a>)</p>
-</li>
-<li>
-<p>Added support for distributed result grouping.
-    (<a href="https://issues.apache.org/jira/browse/SOLR-2066">SOLR-2066</a>,
-    <a href="https://issues.apache.org/jira/browse/SOLR-2776">SOLR-2776</a>)</p>
-</li>
-<li>
-<p>Added support for Hunspell stemmer <code  class="inline">TokenFilter</code> supporting
-    stemming for 99 languages.
-    (<a href="https://issues.apache.org/jira/browse/SOLR-2769">SOLR-2769</a>)</p>
-</li>
-<li>
-<p>A new contrib module "langid" adds language identification
-    capabilities as an Update Processor, using Tika's
-    <code  class="inline">LanguageIdentifier</code> or Cybozu language-detection library
-    (<a href="https://issues.apache.org/jira/browse/SOLR-1979">SOLR-1979</a>)</p>
-</li>
-<li>
-<p>Numeric types including Trie and date types now support
-    <code  class="inline">sortMissingFirst</code>/<code  class="inline">Last</code>.
-    (<a href="https://issues.apache.org/jira/browse/SOLR-2881">SOLR-2881</a>)</p>
-</li>
-<li>
-<p>Added <code  class="inline">hl.q</code> parameter. It is optional and if it is specified,
-    it overrides <code  class="inline">q</code> parameter in <code  class="inline">Highlighter</code>.
-    (<a href="https://issues.apache.org/jira/browse/SOLR-1926">SOLR-1926</a>)</p>
-</li>
-<li>
-<p>Several minor bugfixes like date parsing for years from 0001-1000, ignored
-    configurations when using <code  class="inline">QueryAnalyzer</code> with
-    <code  class="inline">SpellCheckComponent</code> and many more.
-    See CHANGES.txt entries for full details.</p>
-</li>
-</ul>
-<h2 id="26_october_2011_-_java_7u1_fixes_index_corruption_and_crash_bugs_in_apache_lucene_core_and_apache_solrtitle">26 October 2011 - Java 7u1 fixes index corruption and crash bugs in Apache Lucene Core and Apache Solr</title></h2>
-<p>Oracle released <a href="http://www.oracle.com/technetwork/java/javase/7u1-relnotes-507962.html">Java 7u1</a> on October 19.
-  According to the release notes and tests done by the Lucene committers, all bugs reported on July 28 are fixed in this release,
-  so code using Porter stemmer no longer crashes with <code  class="inline">SIGSEGV</code>. We were not able to experience any index corruption anymore,
-  so it is safe to use Java 7u1 with Lucene Core and Solr.
-  On the same day, Oracle released <a href="http://www.oracle.com/technetwork/java/javase/6u29-relnotes-507960.html">Java 6u29</a>
-  fixing the same problems occurring with Java 6, if the JVM switches <code  class="inline">-XX:+AggressiveOpts</code>
-  or <code  class="inline">-XX:+OptimizeStringConcat</code> were used. Of course, you should <strong>not</strong> use experimental JVM options like
-  <code  class="inline">-XX:+AggressiveOpts</code> in production environments! We recommend everybody to upgrade to this latest version 6u29.
-  In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
-  version shipped with Java 7 changed and tokenization behaves differently
-  (e.g. lowercasing). For more information, read <code  class="inline">JRE_VERSION_MIGRATION.txt</code>
-  in your distribution package!</p>
-<h2 id="14_september_2011_-_lucene_core_340_and_solr_340_availabletitle">14 September 2011 - Lucene Core 3.4.0 and Solr 3.4.0 Available</title></h2>
-<p>The Lucene PMC is pleased to announce the availability
- of Apache Solr 3.4.0.</p>
-<p>Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>Highlights of the Solr release include:</p>
-<ul>
-<li>
-<p>SolrJ client can now parse grouped and range facets results
-(<a href="https://issues.apache.org/jira/browse/SOLR-2523">SOLR-2523</a>).</p>
-</li>
-<li>
-<p>A new <code  class="inline">XsltUpdateRequestHandler</code> allows posting XML that's
-transformed by a provided XSLT into a valid Solr document
-(<a href="https://issues.apache.org/jira/browse/SOLR-2630">SOLR-2630</a>).</p>
-</li>
-<li>
-<p>Post-group faceting option (<code  class="inline">group.truncate</code>) can now compute
-facet counts for only the highest ranking documents per-group.
-(<a href="https://issues.apache.org/jira/browse/SOLR-2665">SOLR-2665</a>).</p>
-</li>
-<li>
-<p>Add <code  class="inline">commitWithin</code> update request parameter to all update handlers
-that were previously missing it.  This tells Solr to commit the
-change within the specified amount of time (<a href="https://issues.apache.org/jira/browse/SOLR-2540">SOLR-2540</a>).</p>
-</li>
-<li>
-<p>You can now specify <code  class="inline">NIOFSDirectory</code> (<a href="https://issues.apache.org/jira/browse/SOLR-2670">SOLR-2670</a>).</p>
-</li>
-<li>
-<p>New parameter <code  class="inline">hl.phraseLimit</code> speeds up <code  class="inline">FastVectorHighlighter</code>
-(<a href="https://issues.apache.org/jira/browse/LUCENE-3234">LUCENE-3234</a>).</p>
-</li>
-<li>
-<p>The query cache and filter cache can now be disabled per request.
-See <a href="http://wiki.apache.org/solr/CommonQueryParameters#Caching_of_filters">this wiki page</a>
-(<a href="https://issues.apache.org/jira/browse/SOLR-2429">SOLR-2429</a>).</p>
-</li>
-<li>
-<p>Improved memory usage, build time, and performance of
-<code  class="inline">SynonymFilterFactory</code> (<a href="https://issues.apache.org/jira/browse/LUCENE-3233">LUCENE-3233</a>).</p>
-</li>
-<li>
-<p>Added <code  class="inline">omitPositions</code> to the schema, so you can omit position
-information while still indexing term frequencies (<a href="https://issues.apache.org/jira/browse/LUCENE-2048">LUCENE-2048</a>).</p>
-</li>
-<li>
-<p>Various fixes for multi-threaded <code  class="inline">DataImportHandler</code>.</p>
-</li>
-</ul>
-<h2 id="28_july_2011_-_warning_index_corruption_and_crashes_in_apache_lucene_core__apache_solr_with_java_7">28 July 2011 - WARNING: Index corruption and crashes in Apache Lucene Core / Apache Solr with Java 7</h2>
-<p>Oracle released <a href="http://www.oracle.com/technetwork/java/javase/downloads/index.html">Java 7</a> today.
-Unfortunately it contains hotspot compiler optimizations, which miscompile some loops.
-This can affect code of several Apache projects. Sometimes JVMs only crash, but in several cases,
-results calculated can be incorrect, leading to bugs in applications
-(see Hotspot bugs <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134">7070134</a>,
-<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7044738">7044738</a>,
-<a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7068051">7068051</a>).
-<strong>Apache Lucene Core</strong> and <strong>Apache Solr</strong> are two Apache projects,
-which are affected by these bugs, namely all versions released until today.
-Solr users with the default configuration will have
-Java crashing with <code  class="inline">SIGSEGV</code> as soon as they start to index documents, as one
-affected part is the well-known Porter stemmer
-(see <a href="https://issues.apache.org/jira/browse/LUCENE-3335">LUCENE-3335</a>).
-Other loops in Lucene may be miscompiled, too, leading to index corruption
-(especially on Lucene trunk with pulsing codec; other loops may be
-affected, too - <a href="https://issues.apache.org/jira/browse/LUCENE-3346">LUCENE-3346</a>).
-These problems were detected only 5 days before the official Java 7 release,
-so Oracle had no time to fix those bugs, affecting also many more applications.
-In response to our questions, they proposed to include the fixes into service
-release u2 (eventually into service release u1, see
-<a href="http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2011-July/005971.html">this mail</a>).
-<strong>This means you cannot use Apache Lucene/Solr with Java 7 releases before Update 2!</strong>
-If you do, please don't open bug reports, it is not the committers' fault!
-At least disable loop optimizations using the <code  class="inline">-XX:-UseLoopPredicate</code> JVM option
-to not risk index corruptions.
-<em>Please note:</em> Also Java 6 users are affected, if they use one of those
-JVM options, which are <strong>not</strong> enabled by default: <code  class="inline">-XX:+OptimizeStringConcat</code>
-or <code  class="inline">-XX:+AggressiveOpts</code>.
-It is strongly recommended not to use any hotspot optimization switches in any Java
-version without extensive testing!
-In case you upgrade to Java 7, remember that you may have to reindex, as the unicode
-version shipped with Java 7 changed and tokenization behaves differently
-(e.g. lowercasing). For more information, read <code  class="inline">JRE_VERSION_MIGRATION.txt</code>
-in your distribution package!</p>
-<h2 id="1_july_2011_-_solr_33_available">1 July 2011 - Solr 3.3 Available</h2>
-<p>The Lucene PMC is pleased to announce the availability
-of Apache Solr 3.3.</p>
-<p>Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>Highlights of the Solr release include:</p>
-<ul>
-<li>Grouping / Field Collapsing</li>
-<li>A new, automaton-based suggest/autocomplete implementation offering an
-       order of magnitude smaller RAM consumption.</li>
-<li>KStemFilterFactory, an optimized implementation of a less aggressive
-       stemmer for English.</li>
-<li>Solr defaults to a new, more efficient merge policy (TieredMergePolicy).
-       See <a href="http://s.apache.org/merging">http://s.apache.org/merging</a> for more information.</li>
-<li>Important bugfixes, including extremely high RAM usage in spellchecking.</li>
-<li>Bugfixes and improvements from Apache Lucene 3.3</li>
-</ul>
-<h2 id="4_june_2011_-_lucene_core_32_and_solr_32_available">4 June 2011 - Lucene Core 3.2 and Solr 3.2 Available</h2>
-<p>The Lucene PMC is pleased to announce the availability of Apache Solr 3.2.</p>
-<p>Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>Highlights of the Solr release include:</p>
-<ul>
-<li>Ability to specify overwrite and commitWithin as request parameters when
-       using the JSON update format.</li>
-<li>TermQParserPlugin, useful when generating filter queries from terms
-       returned from field faceting or the terms component.</li>
-<li>DebugComponent now supports using a NamedList to model Explanation objects
-       in its responses instead of Explanation.toString.</li>
-<li>Improvements to the UIMA and Carrot2 integrations.</li>
-<li>Highlighting performance improvements.</li>
-<li>A test-framework jar for easy testing of Solr extensions.</li>
-<li>Bugfixes and improvements from Apache Lucene 3.2.</li>
-</ul>
-<h2 id="31_march_2011_-_solr_31_available">31 March 2011 - Solr 3.1 Available</h2>
-<p>The Lucene PMC is pleased to announce the availability of Apache Solr 3.1.
-The version number for Solr 3.1 was chosen to reflect the merge of
-development with Lucene, which is currently also on 3.1.  Going
-forward, we expect the Solr version to be the same as the Lucene
-version.  Solr 3.1 contains Lucene 3.1 and is the release after Solr 1.4.1.</p>
-<p>Solr can be downloaded from <a href="http://www.apache.org/dyn/closer.cgi/lucene/solr/">http://www.apache.org/dyn/closer.cgi/lucene/solr/</a></p>
-<p>Highlights of the Solr release include:</p>
-<ul>
-<li>Numeric range facets (similar to date faceting).</li>
-<li>New spatial search, including spatial filtering, boosting and sorting capabilities.</li>
-<li>Example Velocity driven search UI at http://localhost:8983/solr/browse</li>
-<li>A new termvector-based highlighter</li>
-<li>Extend dismax (edismax) query parser which addresses some
-missing features in the dismax query parser along with some
-extensions.</li>
-<li>Several more components now support distributed mode:
-TermsComponent, SpellCheckComponent.</li>
-<li>A new Auto Suggest component.</li>
-<li>Ability to sort by functions.</li>
-<li>JSON document indexing.</li>
-<li>CSV response format.</li>
-<li>Apache UIMA integration for metadata extraction.</li>
-<li>Leverages Lucene 3.1 and it's inherent optimizations and bug fixes
-as well as new analysis capabilities.</li>
-<li>Numerous improvements, bug fixes, and optimizations.</li>
+<div><p>Title: Solr Features</p>
+<p>Solr is a standalone enterprise search server with a REST-like API. You put documents in it (called "indexing") via XML, JSON or binary over HTTP. You query it via HTTP GET and receive XML, JSON, or binary results.</p>
+<ul>
+<li>Advanced Full-Text Search Capabilities</li>
+<li>Optimized for High Volume Web Traffic</li>
+<li>Standards Based Open Interfaces - XML,JSON and HTTP</li>
+<li>Comprehensive HTML Administration Interfaces</li>
+<li>Server statistics exposed over JMX for monitoring</li>
+<li>Scalability - Efficient Replication to other Solr Search Servers</li>
+<li>Flexible and Adaptable with XML configuration</li>
+<li>Extensible Plugin Architecture</li>
+</ul>
+<h2 id="solr_uses_the_lucene_search_library_and_extends_it">Solr Uses the Lucene Search Library and Extends it!</h2>
+<ul>
+<li>A Real Data Schema, with Numeric Types, Dynamic Fields, Unique Keys</li>
+<li>Powerful Extensions to the Lucene Query Language</li>
+<li>Faceted Search and Filtering</li>
+<li>Geospatial Search</li>
+<li>Advanced, Configurable Text Analysis</li>
+<li>Highly Configurable and User Extensible Caching</li>
+<li>Performance Optimizations</li>
+<li>External Configuration via XML</li>
+<li>An Administration Interface</li>
+<li>Monitorable Logging</li>
+<li>Fast Incremental Updates and Index Replication</li>
+<li>Highly Scalable Distributed search with sharded index across multiple hosts</li>
+<li>JSON, XML, CSV/delimited-text, and binary update formats</li>
+<li>Easy ways to pull in data from databases and XML files from local disk and HTTP sources</li>
+<li>Rich Document Parsing and Indexing (PDF, Word, HTML, etc) using Apache Tika</li>
+<li>Apache UIMA integration for configurable metadata extraction</li>
+<li>Multiple search indices</li>
+</ul>
+<h2 id="detailed_features">Detailed Features</h2>
+<h3 id="schema">Schema</h3>
+<ul>
+<li>Defines the field types and fields of documents</li>
+<li>Can drive more intelligent processing</li>
+<li>Declarative Lucene Analyzer specification</li>
+<li>Dynamic Fields enables on-the-fly addition of new fields</li>
+<li>CopyField functionality allows indexing a single field multiple ways, or combining multiple fields into a single searchable field</li>
+<li>Explicit types eliminates the need for guessing types of fields</li>
+<li>External file-based configuration of stopword lists, synonym lists, and protected word lists</li>
+<li>Many additional text analysis components including word splitting, regex and sounds-like filters</li>
+</ul>
+<h3 id="query">Query</h3>
+<ul>
+<li>HTTP interface with configurable response formats (XML/XSLT, JSON, Python, Ruby, PHP, Velocity, binary)</li>
+<li>Sort by any number of fields, and by complex functions of numeric fields</li>
+<li>Advanced DisMax query parser for high relevancy results from user-entered queries</li>
+<li>Highlighted context snippets</li>
+<li>Faceted Searching based on unique field values, explicit queries, date ranges, and numeric ranges</li>
+<li>Multi-Select Faceting by tagging and selectively excluding filters</li>
+<li>Spelling suggestions for user queries</li>
+<li>More Like This suggestions for given document</li>
+<li>Function Query - influence the score by user specified complex functions of
+numeric fields or query relevancy scores.</li>
+<li>Range filter over Function Query results</li>
+<li>Date Math - specify dates relative to "NOW" in queries and updates</li>
+<li>Dynamic search results clustering using Carrot2</li>
+<li>Numeric field statistics such as min, max, average, standard deviation</li>
+<li>Combine queries derived from different syntaxes</li>
+<li>Auto-suggest functionality for completing user queries</li>
+<li>Allow configuration of top results for a query, overriding normal scoring and sorting</li>
+<li>Performance Optimizations</li>
+</ul>
+<h3 id="core">Core</h3>
+<ul>
+<li>Dynamically create and delete document collections without restarting</li>
+<li>Pluggable query handlers and extensible XML data format</li>
+<li>Pluggable user functions for Function Query</li>
+<li>Customizable component based request handler with distributed search support</li>
+<li>Document uniqueness enforcement based on unique key field</li>
+<li>Duplicate document detection, including fuzzy near duplicates</li>
+<li>Custom index processing chains, allowing document manipulation before indexing</li>
+<li>User configurable commands triggered on index changes</li>
+<li>Ability to control where docs with the sort field missing will be placed</li>
+<li>"Luke" request handler for corpus information</li>
+</ul>
+<h3 id="caching">Caching</h3>
+<ul>
+<li>Configurable Query Result, Filter, and Document cache instances</li>
+<li>Pluggable Cache implementations, including a lock free, high concurrency implementation</li>
+<li>Cache warming in background</li>
+<li>When a new searcher is opened, configurable searches are run against
+  it in order to warm it up to avoid
+  slow first hits.  During warming, the current searcher handles live requests.</li>
+<li>Autowarming in background</li>
+<li>The most recently accessed items in the caches of the current
+  searcher are re-populated in the new searcher, enabling high cache hit
+  rates across index/searcher changes.</li>
+<li>Fast/small filter implementation</li>
+<li>User level caching with autowarming support</li>
+</ul>
+<h3 id="replication">Replication</h3>
+<ul>
+<li>Efficient distribution of index parts that have changed</li>
+<li>Pull strategy allows for easy addition of searchers</li>
+<li>Configurable distribution interval allows tradeoff between timeliness and cache utilization</li>
+<li>Replication and automatic reloading of configuration files</li>
+</ul>
+<h3 id="admin_interface">Admin Interface</h3>
+<ul>
+<li>Comprehensive statistics on cache utilization, updates, and queries</li>
+<li>Interactive schema browser that includes index statistics</li>
+<li>Replication monitoring</li>
+<li>Full logging control</li>
+<li>Text analysis debugger, showing result of every stage in an analyzer</li>
+<li>Web Query Interface w/ debugging output</li>
+<li>Parsed query output</li>
+<li>Lucene explain() document score detailing</li>
+<li>explain score for documents outside of the requested range to debug why a given document wasn't ranked higher.</li>
 </ul></div>
 
 
@@ -482,6 +392,12 @@ as well as new analysis capabilities.</l
         <div class="status-item">
           
           <div class="section-content">
+            <a class="svn" href="http://svn.apache.org/viewvc?revision=1291115;view=revision">r1291115</a>
+            <a href="https://issues.apache.org/jira/browse/SOLR-3142">SOLR-3142</a>: don't auto-optimize in dataimports (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
+            <a href="http://people.apache.org/committer-index.html#rmuir">rmuir</a>
+          </div>
+          
+          <div class="section-content">
             <a class="svn" href="http://svn.apache.org/viewvc?revision=1291097;view=revision">r1291097</a>
             Remove volatile from IR.closed variable (its only used in already synchronized close() method) (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
             <a href="http://people.apache.org/committer-index.html#uschindler">uschindler</a>
@@ -505,12 +421,6 @@ as well as new analysis capabilities.</l
             <a href="http://people.apache.org/committer-index.html#rmuir">rmuir</a>
           </div>
           
-          <div class="section-content">
-            <a class="svn" href="http://svn.apache.org/viewvc?revision=1291003;view=revision">r1291003</a>
-            <a href="https://issues.apache.org/jira/browse/SOLR-3126">SOLR-3126</a>: test changes to handle deletes surviving restart (<a href="http://lucene.apache.org/">lucene</a>) &mdash;
-            <a href="http://people.apache.org/committer-index.html#yonik">yonik</a>
-          </div>
-          
         </div>
         
       </div>
@@ -519,9 +429,11 @@ as well as new analysis capabilities.</l
 
         
         <div class="status-item">
-          <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-3080">[SOLR-3080] We should consider removing shard info from Zk when you explicitly unload a SolrCore.</a><br/>
+          <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-3142">[SOLR-3142] remove O(n^2) slow slow indexing defaults in DataImportHandler</a><br/>
           <div class="section-content">
-                         
+                         <p>By default, dataimporthandler optimizes the entire index when it commits.</p>
+
+<p>This is bad for performance, because it means by default...</p>
           </div>
           
           <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-3141">[SOLR-3141] Deprecate OPTIMIZE command in Solr</a><br/>
@@ -531,16 +443,14 @@ as well as new analysis capabilities.</l
 <p>Now that optimize() is rarely necessary anymore, and renamed...</p>
           </div>
           
-          <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-2898">[SOLR-2898] Support grouped faceting</a><br/>
+          <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-3080">[SOLR-3080] We should consider removing shard info from Zk when you explicitly unload a SolrCore.</a><br/>
           <div class="section-content">
-                         <p>Support grouped faceting. As described in <a href="https://issues.apache.org/jira/browse/LUCENE-3097" title="Post grouping faceting"><del>LUCENE-3097</del></a> (matrix counts).</p>
+                         
           </div>
           
-          <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-3142">[SOLR-3142] remove O(n^2) slow slow indexing defaults in DataImportHandler</a><br/>
+          <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-2898">[SOLR-2898] Support grouped faceting</a><br/>
           <div class="section-content">
-                         <p>By default, dataimporthandler optimizes the entire index when it commits.</p>
-
-<p>This is bad for performance, because it means by default...</p>
+                         <p>Support grouped faceting. As described in <a href="https://issues.apache.org/jira/browse/LUCENE-3097" title="Post grouping faceting"><del>LUCENE-3097</del></a> (matrix counts).</p>
           </div>
           
           <a class="bug" href="https://issues.apache.org/jira/browse/SOLR-3143">[SOLR-3143] Supply a phrase-oriented QueryConverter for Suggesters</a><br/>
@@ -557,26 +467,26 @@ it tries to parse out the &apos;meat&apo
 
         
         <div class="status-item">
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c144116534.1276.1329697234363.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c988961348.1373.1329701314321.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
           <div class="section-content">
-          [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211616#comment-13211616">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211616#comment-13211616</a>
-] <br />&nbsp;<br />Yonik Seeley commented on SOLR-3141:
-------------------------------------<br />&nbsp;<br />A slight improvement in name does not come anywhere...
+          [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211626#comment-13211626">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211626#comment-13211626</a>
+] <br />&nbsp;<br />Robert Muir commented on SOLR-3141:
+-----------------------------------<br />&nbsp;<br />{quote}
+A slight improvement in name does not come...
             </div>
           
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c951795337.1243.1329696636539.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c623503952.1366.1329700834282.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (LUCENE-3803) Using a searcher with an executor service does not work from within a Callable called by that same executor service</a></h4>
           <div class="section-content">
-          [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211611#comment-13211611">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211611#comment-13211611</a>
-] <br />&nbsp;<br />Uwe Schindler commented on SOLR-3141:
--------------------------------------<br />&nbsp;<br />bq. I doubt it. An dhow did they find...
+          [ <a href="https://issues.apache.org/jira/browse/LUCENE-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211624#comment-13211624">https://issues.apache.org/jira/browse/LUCENE-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211624#comment-13211624</a>
+] <br />&nbsp;<br />Robert Muir commented on LUCENE-3803:
+-------------------------------------<br />&nbsp;<br />This is not really related to your problem (somewhat)...
             </div>
           
-          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c614733919.1230.1329696154551.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Commented] (SOLR-3141) Deprecate OPTIMIZE command in Solr</a></h4>
+          <h4><a href="http://mail-archives.apache.org/mod_mbox/lucene-dev/201202.mbox/%3c2011272015.1364.1329700042509.JavaMail.tomcat@hel.zones.apache.org%3e">[jira] [Assigned] (SOLR-3080) We should consider removing shard info from Zk when you explicitly unload a SolrCore.</a></h4>
           <div class="section-content">
-          [ <a href="https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211609#comment-13211609">https://issues.apache.org/jira/browse/SOLR-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211609#comment-13211609</a>
-] <br />&nbsp;<br />Robert Muir commented on SOLR-3141:
------------------------------------<br />&nbsp;<br />{quote}
-twice that many visit the download page... but...
+          [ <a href="https://issues.apache.org/jira/browse/SOLR-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel">https://issues.apache.org/jira/browse/SOLR-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel</a>
+]<br />&nbsp;<br />Mark Miller reassigned SOLR-3080:
+---------------------------------<br />&nbsp;<br />    Assignee: Sami Siren  (was: Mark Miller)<br />&nbsp;<br />All yours Sami....
             </div>
           
         </div>



Mime
View raw message