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/06/19 23:21:11 UTC
svn commit: r822417 - in /websites: production/lucene/content/
production/lucene/content/core/ production/lucene/content/solr/
staging/lucene/trunk/content/ staging/lucene/trunk/content/core/
staging/lucene/trunk/content/solr/
Author: buildbot
Date: Tue Jun 19 21:21:11 2012
New Revision: 822417
Log:
Dynamic 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
websites/staging/lucene/trunk/content/core/index.html
websites/staging/lucene/trunk/content/index.html
websites/staging/lucene/trunk/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 Jun 19 21:21:11 2012
@@ -306,6 +306,12 @@
<div class="status-item">
<div class="section-content">
+ <a class="svn" href="http://svn.apache.org/viewvc?revision=1351839;view=revision">r1351839</a>
+ <a href="https://issues.apache.org/jira/browse/SOLR-3548">SOLR-3548</a>: Fixed a bug in the cachability of queries using the {!join} parser or the strdist() function, as well... (<a href="http://lucene.apache.org/">lucene</a>) —
+ <a href="http://people.apache.org/committer-index.html#hossman">hossman</a>
+ </div>
+
+ <div class="section-content">
<a class="svn" href="http://svn.apache.org/viewvc?revision=1351829;view=revision">r1351829</a>
don't use Memory/SimpleText postings format when indexing too many tokens from random data (<a href="http://lucene.apache.org/">lucene</a>) —
<a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
@@ -332,12 +338,6 @@
<a href="https://issues.apache.org/jira/browse/LUCENE-4061">LUCENE-4061</a>: fix another concurrency issue with DirTaxoWriter (<a href="http://lucene.apache.org/">lucene</a>) —
<a href="http://people.apache.org/committer-index.html#shaie">shaie</a>
</div>
-
- <div class="section-content">
- <a class="svn" href="http://svn.apache.org/viewvc?revision=1351661;view=revision">r1351661</a>
- suppress MemoryPostingsFormat for this test, to prevent false OOME (<a href="http://lucene.apache.org/">lucene</a>) —
- <a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
- </div>
</div></div>
Modified: websites/production/lucene/content/index.html
==============================================================================
(empty)
Modified: websites/production/lucene/content/solr/index.html
==============================================================================
--- websites/production/lucene/content/solr/index.html (original)
+++ websites/production/lucene/content/solr/index.html Tue Jun 19 21:21:11 2012
@@ -400,6 +400,12 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
+ <a class="svn" href="http://svn.apache.org/viewvc?revision=1351839;view=revision">r1351839</a>
+ <a href="https://issues.apache.org/jira/browse/SOLR-3548">SOLR-3548</a>: Fixed a bug in the cachability of queries using the {!join} parser or the strdist() function, as well... (<a href="http://lucene.apache.org/">lucene</a>) —
+ <a href="http://people.apache.org/committer-index.html#hossman">hossman</a>
+ </div>
+
+ <div class="section-content">
<a class="svn" href="http://svn.apache.org/viewvc?revision=1351829;view=revision">r1351829</a>
don't use Memory/SimpleText postings format when indexing too many tokens from random data (<a href="http://lucene.apache.org/">lucene</a>) —
<a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
@@ -427,12 +433,6 @@ numeric fields or query relevancy scores
<a href="http://people.apache.org/committer-index.html#shaie">shaie</a>
</div>
- <div class="section-content">
- <a class="svn" href="http://svn.apache.org/viewvc?revision=1351661;view=revision">r1351661</a>
- suppress MemoryPostingsFormat for this test, to prevent false OOME (<a href="http://lucene.apache.org/">lucene</a>) —
- <a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
- </div>
-
</div>
</div>
@@ -442,15 +442,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="http://twitter.com/torilll/statuses/215174693215408132">@</a>Why use <a href="http://twitter.com/search?q=%23Solr?">#Solr?</a>
+ <a href="http://twitter.com/shirleman/statuses/215189337246138368">@</a>That is why DataStax Enterprise rocks; <a href="http://twitter.com/search?q=%23cassandra">#cassandra</a> <a href="http://twitter.com/search?q=%23hadoop">#hadoop</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23bigdata">#bigdata</a> <a href="http://twitter.com/data_hipster">@data_hipster</a> Waiting for ETL is the new 'Waiting for Godot'
</div>
<div class="section-content">
- <a href="http://twitter.com/otisg/statuses/215119355971780610">@</a>How SolrCloud behaves in Split Brain situations: <a href="http://t.co/VSGhDl6W">http://t.co/VSGhDl6W</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23solrcloud">#solrcloud</a>
+ <a href="http://twitter.com/torilll/statuses/215174693215408132">@</a>Why use <a href="http://twitter.com/search?q=%23Solr?">#Solr?</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/nosh_p/statuses/215103481562931201">@</a>RT <a href="http://twitter.com/rick446">@rick446</a>: Allura, SourceForge's platform, has been submitted to the ASF for incubation <a href="http://twitter.com/search?q=%23python">#python</a> <a href="http://twitter.com/search?q=%23mongodb">#mongodb</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://t.co/l1kRq5AM">http://t.co/l1kRq5AM</a>
+ <a href="http://twitter.com/otisg/statuses/215119355971780610">@</a>How SolrCloud behaves in Split Brain situations: <a href="http://t.co/VSGhDl6W">http://t.co/VSGhDl6W</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23solrcloud">#solrcloud</a>
</div>
</div>
Modified: websites/staging/lucene/trunk/content/core/index.html
==============================================================================
--- websites/staging/lucene/trunk/content/core/index.html (original)
+++ websites/staging/lucene/trunk/content/core/index.html Tue Jun 19 21:21:11 2012
@@ -306,6 +306,12 @@
<div class="status-item">
<div class="section-content">
+ <a class="svn" href="http://svn.apache.org/viewvc?revision=1351839;view=revision">r1351839</a>
+ <a href="https://issues.apache.org/jira/browse/SOLR-3548">SOLR-3548</a>: Fixed a bug in the cachability of queries using the {!join} parser or the strdist() function, as well... (<a href="http://lucene.apache.org/">lucene</a>) —
+ <a href="http://people.apache.org/committer-index.html#hossman">hossman</a>
+ </div>
+
+ <div class="section-content">
<a class="svn" href="http://svn.apache.org/viewvc?revision=1351829;view=revision">r1351829</a>
don't use Memory/SimpleText postings format when indexing too many tokens from random data (<a href="http://lucene.apache.org/">lucene</a>) —
<a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
@@ -332,12 +338,6 @@
<a href="https://issues.apache.org/jira/browse/LUCENE-4061">LUCENE-4061</a>: fix another concurrency issue with DirTaxoWriter (<a href="http://lucene.apache.org/">lucene</a>) —
<a href="http://people.apache.org/committer-index.html#shaie">shaie</a>
</div>
-
- <div class="section-content">
- <a class="svn" href="http://svn.apache.org/viewvc?revision=1351661;view=revision">r1351661</a>
- suppress MemoryPostingsFormat for this test, to prevent false OOME (<a href="http://lucene.apache.org/">lucene</a>) —
- <a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
- </div>
</div></div>
Modified: websites/staging/lucene/trunk/content/index.html
==============================================================================
(empty)
Modified: websites/staging/lucene/trunk/content/solr/index.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/index.html (original)
+++ websites/staging/lucene/trunk/content/solr/index.html Tue Jun 19 21:21:11 2012
@@ -400,6 +400,12 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
+ <a class="svn" href="http://svn.apache.org/viewvc?revision=1351839;view=revision">r1351839</a>
+ <a href="https://issues.apache.org/jira/browse/SOLR-3548">SOLR-3548</a>: Fixed a bug in the cachability of queries using the {!join} parser or the strdist() function, as well... (<a href="http://lucene.apache.org/">lucene</a>) —
+ <a href="http://people.apache.org/committer-index.html#hossman">hossman</a>
+ </div>
+
+ <div class="section-content">
<a class="svn" href="http://svn.apache.org/viewvc?revision=1351829;view=revision">r1351829</a>
don't use Memory/SimpleText postings format when indexing too many tokens from random data (<a href="http://lucene.apache.org/">lucene</a>) —
<a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
@@ -427,12 +433,6 @@ numeric fields or query relevancy scores
<a href="http://people.apache.org/committer-index.html#shaie">shaie</a>
</div>
- <div class="section-content">
- <a class="svn" href="http://svn.apache.org/viewvc?revision=1351661;view=revision">r1351661</a>
- suppress MemoryPostingsFormat for this test, to prevent false OOME (<a href="http://lucene.apache.org/">lucene</a>) —
- <a href="http://people.apache.org/committer-index.html#mikemccand">mikemccand</a>
- </div>
-
</div>
</div>
@@ -442,15 +442,15 @@ numeric fields or query relevancy scores
<div class="status-item">
<div class="section-content">
- <a href="http://twitter.com/torilll/statuses/215174693215408132">@</a>Why use <a href="http://twitter.com/search?q=%23Solr?">#Solr?</a>
+ <a href="http://twitter.com/shirleman/statuses/215189337246138368">@</a>That is why DataStax Enterprise rocks; <a href="http://twitter.com/search?q=%23cassandra">#cassandra</a> <a href="http://twitter.com/search?q=%23hadoop">#hadoop</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23bigdata">#bigdata</a> <a href="http://twitter.com/data_hipster">@data_hipster</a> Waiting for ETL is the new 'Waiting for Godot'
</div>
<div class="section-content">
- <a href="http://twitter.com/otisg/statuses/215119355971780610">@</a>How SolrCloud behaves in Split Brain situations: <a href="http://t.co/VSGhDl6W">http://t.co/VSGhDl6W</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23solrcloud">#solrcloud</a>
+ <a href="http://twitter.com/torilll/statuses/215174693215408132">@</a>Why use <a href="http://twitter.com/search?q=%23Solr?">#Solr?</a>
</div>
<div class="section-content">
- <a href="http://twitter.com/nosh_p/statuses/215103481562931201">@</a>RT <a href="http://twitter.com/rick446">@rick446</a>: Allura, SourceForge's platform, has been submitted to the ASF for incubation <a href="http://twitter.com/search?q=%23python">#python</a> <a href="http://twitter.com/search?q=%23mongodb">#mongodb</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://t.co/l1kRq5AM">http://t.co/l1kRq5AM</a>
+ <a href="http://twitter.com/otisg/statuses/215119355971780610">@</a>How SolrCloud behaves in Split Brain situations: <a href="http://t.co/VSGhDl6W">http://t.co/VSGhDl6W</a> <a href="http://twitter.com/search?q=%23solr">#solr</a> <a href="http://twitter.com/search?q=%23solrcloud">#solrcloud</a>
</div>
</div>