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 2012/02/14 11:15:10 UTC

svn commit: r804761 - in /websites/production/lucene/content: core/index.html solr/index.html

Author: buildbot
Date: Tue Feb 14 10:15:10 2012
New Revision: 804761

Log:
Production update by buildbot for lucene

Modified:
    websites/production/lucene/content/core/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 Tue Feb 14 10:15:10 2012
@@ -548,9 +548,9 @@ once a segment is finished.</li>
     <div id="jira">
       <h1>Latest JIRA</h1>
       <div class="status-item">
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3774">[LUCENE-3774] check-legal isn&apos;t doing its job</a><br/>
+      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3758">[LUCENE-3758] Allow the ComplexPhraseQueryParser to search order or un-order proximity queries.</a><br/>
        <div class="section-content">
-        <p>In trunk, the <tt>check-legal-lucene</tt> ant target is not checking any <tt>lucene/contrib/&#42;&#42;/lib/</tt> directories; the <tt>modules/**/lib/</tt> directories are not being checked; and...</p>
+        <p>The ComplexPhraseQueryParser use SpanNearQuery, but always set the "inOrder" value hardcoded to "true". This could be configurable.</p>
        </div>
     
       <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-2632">[LUCENE-2632] FilteringCodec, TeeCodec, TeeDirectory</a><br/>
@@ -561,25 +561,21 @@ once a segment is finished.</li>
 	<li>TeeCodec: there have been attempts in the past to implement parallel writing to...</li></ul>
        </div>
     
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3777">[LUCENE-3777] trapping overloaded ctors/setters in Field/NumericField/DocValuesField</a><br/>
+      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3778">[LUCENE-3778] Create a grouping convenience class</a><br/>
        <div class="section-content">
-        <p>In trunk, these apis let you easily create a field, but my concern is this:</p>
-<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java"><span class="code-keyword">public</span> NumericField(<span class="code-object">String</span> name, <span class="code-object">int...</span></pre></div></div>
+        <p>Currently the grouping module has many collector classes with a lot of different options per class. I think it would...</p>
        </div>
     
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3754">[LUCENE-3754] Store generated archive manifests in per-module output directories</a><br/>
+      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3774">[LUCENE-3774] check-legal isn&apos;t doing its job</a><br/>
        <div class="section-content">
-        <p>Currently, generated archive manifests are all stored in the same location, so each module&apos;s build overwrites the previously built module&apos;s...</p>
+        <p>In trunk, the <tt>check-legal-lucene</tt> ant target is not checking any <tt>lucene/contrib/&#42;&#42;/lib/</tt> directories; the <tt>modules/**/lib/</tt> directories are not being checked; and...</p>
        </div>
     
-      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3776">[LUCENE-3776] NRTManager shouldn&apos;t expose its private SearcherManager</a><br/>
+      <a class="bug" href="https://issues.apache.org/jira/browse/LUCENE-3777">[LUCENE-3777] trapping overloaded ctors/setters in Field/NumericField/DocValuesField</a><br/>
        <div class="section-content">
-        <p>Spinoff from <a href="https://issues.apache.org/jira/browse/LUCENE-3769" title="Simplify NRTManager"><del>LUCENE-3769</del></a>.</p>
-
-<p>To actually obtain an IndexSearcher from NRTManager, it&apos;s a 2-step process now.</p>
-
-<p>You must .getSearcherManager(), then...</p>
+        <p>In trunk, these apis let you easily create a field, but my concern is this:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java"><span class="code-keyword">public</span> NumericField(<span class="code-object">String</span> name, <span class="code-object">int...</span></pre></div></div>
        </div>
     </div></div>
     

Modified: websites/production/lucene/content/solr/index.html
==============================================================================
--- websites/production/lucene/content/solr/index.html (original)
+++ websites/production/lucene/content/solr/index.html Tue Feb 14 10:15:10 2012
@@ -590,15 +590,15 @@ define language specific tokenizers in..
         
         <div class="status-item">
           <div class="section-content">
-             <a href="http://twitter.com/dathor/statuses/169315077097398273">@</a>Bra! RT <a href="http://twitter.com/marcusosterberg">@marcusosterberg</a>: Har just lyckats indexera <a href="http://t.co/89I8jsJt">http://t.co/89I8jsJt</a> i <a href="http://twitter.com/search?q=%23Solr,">#Solr,</a> nu återstår ett sök-GUI. Onödigt? Absolut, men roligt :)
+             <a href="http://twitter.com/rbramley/statuses/169320970161623041">@</a>RT <a href="http://twitter.com/dep4b">@dep4b</a>: Identifying Anomalous Driving Patterns Using Hadoop and Cassandra <a href="http://t.co/bN0Y0Uih">http://t.co/bN0Y0Uih</a> <a href="http://twitter.com/search?q=%23solr">#solr</a>
           </div>
           
           <div class="section-content">
-             <a href="http://twitter.com/ichattopadhyaya/statuses/169283517178585088">@</a>RT <a href="http://twitter.com/sematext">@sematext</a>: Poll: What Should Index Monitoring Show?  Avg, Min, or Max # of docs?  <a href="http://t.co/aYbjqjmK">http://t.co/aYbjqjmK</a>  <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23sensei">#sensei</a>
+             <a href="http://twitter.com/dathor/statuses/169315077097398273">@</a>Bra! RT <a href="http://twitter.com/marcusosterberg">@marcusosterberg</a>: Har just lyckats indexera <a href="http://t.co/89I8jsJt">http://t.co/89I8jsJt</a> i <a href="http://twitter.com/search?q=%23Solr,">#Solr,</a> nu återstår ett sök-GUI. Onödigt? Absolut, men roligt :)
           </div>
           
           <div class="section-content">
-             <a href="http://twitter.com/_abhij33t/statuses/169263502047981570">@</a>RT <a href="http://twitter.com/sematext">@sematext</a>: Poll: What Should Index Monitoring Show?  Avg, Min, or Max # of docs?  <a href="http://t.co/aYbjqjmK">http://t.co/aYbjqjmK</a>  <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23sensei">#sensei</a>
+             <a href="http://twitter.com/ichattopadhyaya/statuses/169283517178585088">@</a>RT <a href="http://twitter.com/sematext">@sematext</a>: Poll: What Should Index Monitoring Show?  Avg, Min, or Max # of docs?  <a href="http://t.co/aYbjqjmK">http://t.co/aYbjqjmK</a>  <a href="http://twitter.com/search?q=%23lucene">#lucene</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23elasticsearch">#elasticsearch</a> <a href="http://twitter.com/search?q=%23sensei">#sensei</a>
           </div>
           
         </div>