lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1045705 - in /websites/staging/lucene/trunk/content: ./ index.html mainnews.html
Date Wed, 29 May 2019 21:41:33 GMT
Author: buildbot
Date: Wed May 29 21:41:33 2019
New Revision: 1045705

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 Wed May 29 21:41:33 2019
@@ -1 +1 @@
-1860290
+1860374

Modified: websites/staging/lucene/trunk/content/index.html
==============================================================================
--- websites/staging/lucene/trunk/content/index.html (original)
+++ websites/staging/lucene/trunk/content/index.html Wed May 29 21:41:33 2019
@@ -256,6 +256,15 @@ and Solr can be downloaded from <a href=
 <li>REINDEXCOLLECTION command for re-indexing of existing collections</li>
 <li>Collection RENAME command and support using aliases in most collection admin commands</li>
 <li>Read-only mode for SolrCloud collections</li>
+<li>Handling of incorrect or absent values was improved for many request parameters.
In such cases the response is 400 http code (Bad Request), instead of 500 (Internal Server
Error) as it was before.</li>
+<li>
+<p>Breaching timeAllowed limit correctly responded as 200 http code (Ok) with partialResults=true,
instead of 500 (Internal Server Error) as it was before in SolrCloud. Note, it was fixed for
essential request parameters, if you still evidence 500 caused by timeAllowed, please submit
an issue with log excerpt attached.</p>
+</li>
+<li>
+<p>In-place updates work for collections created with route.field.</p>
+</li>
+<li>Asynchronous Collection API calls do not return completion status prematurely when
more than one replica reside per note.</li>
+<li>Range Facets and Terms Component performance has been optimized for certain cases.</li>
 </ul>
 <h2 id="5-april-2019-apache-lucene-666-and-apache-solr-666-available">5 April 2019
- Apache Lucene 6.6.6 and Apache Solr 6.6.6 Available<a class="headerlink" href="#5-april-2019-apache-lucene-666-and-apache-solr-666-available"
title="Permanent link">&para;</a></h2>
 <p>The Lucene PMC is pleased to announce the release of Apache Lucene 6.6.6 and Apache
Solr 6.6.6</p>

Modified: websites/staging/lucene/trunk/content/mainnews.html
==============================================================================
--- websites/staging/lucene/trunk/content/mainnews.html (original)
+++ websites/staging/lucene/trunk/content/mainnews.html Wed May 29 21:41:33 2019
@@ -236,6 +236,15 @@ and Solr can be downloaded from <a href=
 <li>REINDEXCOLLECTION command for re-indexing of existing collections</li>
 <li>Collection RENAME command and support using aliases in most collection admin commands</li>
 <li>Read-only mode for SolrCloud collections</li>
+<li>Handling of incorrect or absent values was improved for many request parameters.
In such cases the response is 400 http code (Bad Request), instead of 500 (Internal Server
Error) as it was before.</li>
+<li>
+<p>Breaching timeAllowed limit correctly responded as 200 http code (Ok) with partialResults=true,
instead of 500 (Internal Server Error) as it was before in SolrCloud. Note, it was fixed for
essential request parameters, if you still evidence 500 caused by timeAllowed, please submit
an issue with log excerpt attached.</p>
+</li>
+<li>
+<p>In-place updates work for collections created with route.field.</p>
+</li>
+<li>Asynchronous Collection API calls do not return completion status prematurely when
more than one replica reside per note.</li>
+<li>Range Facets and Terms Component performance has been optimized for certain cases.</li>
 </ul>
 <h2 id="5-april-2019-apache-lucene-666-and-apache-solr-666-available">5 April 2019
- Apache Lucene 6.6.6 and Apache Solr 6.6.6 Available<a class="headerlink" href="#5-april-2019-apache-lucene-666-and-apache-solr-666-available"
title="Permanent link">&para;</a></h2>
 <p>The Lucene PMC is pleased to announce the release of Apache Lucene 6.6.6 and Apache
Solr 6.6.6</p>



Mime
View raw message