You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ct...@apache.org on 2020/07/15 16:52:39 UTC
svn commit: r1063067 [21/28] - in
/websites/production/lucene/content/solr/guide/8_6: ./ meta-docs/
Modified: websites/production/lucene/content/solr/guide/8_6/solr-upgrade-notes.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/solr-upgrade-notes.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/solr-upgrade-notes.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Solr Upgrade Notes | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Solr Upgrade Notes | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="solr-upgrade-notes">
+<body class="" id="solr-upgrade-notes">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1678,11 +1673,12 @@ file found in your Solr package. That fi
that may effect your existing implementation.</p>
<p>Detailed steps for upgrading a Solr cluster are in the section <a href="upgrading-a-solr-cluster.html#upgrading-a-solr-cluster">Upgrading a Solr Cluster</a>.</p></section>
<section class="sect1"><h2 id="upgrading-to-8-x-releases">Upgrading to 8.x Releases</h2><p>If you are upgrading from 7.x, see the section <a href="#upgrading-from-7-x-releases">Upgrading from 7.x Releases</a> below.</p>
-<section class="sect2"><h3 id="solr-8-6">Solr 8.6</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote86">8.6 Release Notes</a>
+<section class="sect2"><h3 id="solr-8-6">Solr 8.6</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote86" target="_blank" rel="noopener">8.6 Release Notes</a>
for an overview of the main new features of Solr 8.6.</p>
<p>When upgrading to 8.6.x users should be aware of the following major changes from 8.5.</p>
<p><strong>Support for Block-Max WAND</strong></p>
<p>Lucene added support for Block-Max WAND in 8.0, and 8.6 makes this available for Solr also.</p>
+<p>This can provide significant performance enhancements by not calculating the score for results which are not likely to appear in the top set of results.</p>
<p>It is enabled when using a new query parameter <code>minExactCount</code>.
This parameter tells Solr to accurately count the number of hits accurately until at least this value.
Once this value is reached, Solr can skip over documents that don’t have a score high enough to be in the top set of documents, which has the potential for greatly speeding up searches.</p>
@@ -1691,25 +1687,39 @@ It is guaranteed that the hit count is a
<p>A new boolean attribute <code>numFoundExact</code> is included in all responses to indicate if the hit count in the response is expected to be exact or not.</p>
<p>More information about this new feature is available in the section <a href="common-query-parameters.html#minexactcount-parameter">minExactCount Parameter</a>.</p>
<p><strong>Autoscaling</strong></p>
-<div class="ulist"><ul><li><p>Solr now includes a default autoscaling policy.
-This policy can be overridden with your custom rules or by specifying an empty policy to replace the default.</p><p>For details of the default policy, see the section <a href="solrcloud-autoscaling-overview.html#cluster-policy">Cluster Policy</a>.</p></li><li>The <a href="solrcloud-autoscaling-trigger-actions.html#compute-plan-action">ComputePlan action</a> now supports a collection selector to identify collections based on collection properties to determine which collections should be operated on.</li></ul></div>
+<div class="ulist"><ul><li><p><p>Solr now includes a default autoscaling policy.
+This policy can be overridden with your custom rules or by specifying an empty policy to replace the default.</p><p>For details of the default policy, see the section <a href="solrcloud-autoscaling-overview.html#cluster-policy">Cluster Policy</a>.</p></p></li><li><p>The <a href="solrcloud-autoscaling-trigger-actions.html#compute-plan-action">ComputePlan action</a> now supports a collection selector to identify collections based on collection properties to determine which collections should be operated on.</p></li></ul></div>
<p><strong>Security</strong></p>
-<div class="ulist"><ul><li>A new authorization plugin <code>ExternalRoleRuleBasedAuthorizationPlugin</code> is now available.
-This plugin allows an authentication plugin (such as JWT) to supply a user’s roles instead of maintaining a user-to-role mapping inside Solr.</li><li>When authentication is enabled, the Admin UI Dashboard (main screen) now includes a panel that shows the authentication and authorization plugins in use, the logged in username, and the roles assigned to this user.
-A new link will also appear in the left-hand navigation to allow a user to log out.</li></ul></div>
+<div class="ulist"><ul><li><p><p>Prior to Solr 8.6 Solr APIs which take a file system location, such as core creation, backup, restore, and others, did not validate the path and Solr would allow any absolute or relative path.
+Starting in 8.6 only paths that are relative to <code>SOLR_HOME</code>, <code>SOLR_DATA_HOME</code> and <code>coreRootDir</code> are allowed by default.</p><p>If you need to create a core or store a backup outside the default paths, you will need to tell Solr which paths to allow.
+A new element in <code>solr.xml</code> called <code>allowPaths</code> takes a comma-separated list of allowed paths.</p>
+<p>When using the <code>solr.xml</code> file that ships with 8.6, you can configure the list of paths to allow through the system property <code>solr.allowPaths</code>.
+Please see <code>bin/solr.in.sh</code> or <code>bin\solr.in.cmd</code> for example usage.
+Using the value <code>*</code> will allow any path as in earlier versions.</p>
+<p>For more on this, see the section <a href="format-of-solr-xml.html#the-solr-element">Solr.xml Parameters</a>.</p>
+<p>Windows SMB shares on the UNC format, such as <code>\\myhost\myshare\mypath</code> are now always disallowed.
+Please use drive letter mounts instead, i.e., <code>S:\mypath</code>.</p></p></li><li><p>A new authorization plugin <code>ExternalRoleRuleBasedAuthorizationPlugin</code> is now available.
+This plugin allows an authentication plugin (such as JWT) to supply a user’s roles instead of maintaining a user-to-role mapping inside Solr.</p></li><li><p>When authentication is enabled, the Admin UI Dashboard (main screen) now includes a panel that shows the authentication and authorization plugins in use, the logged in username, and the roles assigned to this user.
+A new link will also appear in the left-hand navigation to allow a user to log out.</p></li></ul></div>
<p><strong>Streaming Expressions</strong></p>
-<div class="ulist"><ul><li><p>The <code>/export</code> handler now supports streaming expressions to allow limiting the output of the export to only matching documents.</p><p>For more information about how to use this, see the section <a href="exporting-result-sets.html#specifying-the-local-streaming-expression">Specifying the Local Streaming Expression</a>.</p></li><li>The <code>stats</code>, <code>facet</code>, and <code>timeseries</code> expressions now support percentiles and standard deviation aggregations.</li></ul></div>
+<div class="ulist"><ul><li><p><p>The <code>/export</code> handler now supports streaming expressions to allow limiting the output of the export to only matching documents.</p><p>For more information about how to use this, see the section <a href="exporting-result-sets.html#specifying-the-local-streaming-expression">Specifying the Local Streaming Expression</a>.</p></p></li><li><p>The <code>stats</code>, <code>facet</code>, and <code>timeseries</code> expressions now support percentiles and standard deviation aggregations.</p></li></ul></div>
<p><strong>Highlighting</strong></p>
<p>For the Unified Highlighter: The setting <code>hl.fragsizeIsMinimum</code> now defaults to <code>false</code> because <code>true</code> was found to be a significant performance regression when highlighting lots of text.
This will yield longer highlights on average compared to Solr 8.5 but relatively unchanged compared to previous releases.
Furthermore, if your application highlights lots of text, you may want to experiment with lowering <code>hl.fragAlignRatio</code> to trade ideal fragment alignment for better performance.</p>
-<p><strong>Restricting file paths</strong></p>
-<p>Several Solr APIs allow specifying a file system location. This includes core creation, backup, restore and others. Prior to Solr 8.6 these parameters were not validated, and Solr would allow any absolute or relative path. From 8.6 we by default allow only paths that are relative to <code>SOLR_HOME</code>, <code>SOLR_DATA_HOME</code> and <code>coreRootDir</code>. If you need to create a core or store a backup outside these pre-allowed paths, you now need to tell Solr about what paths to allow.</p>
-<p>Solr can be configured with a comma separated list of paths to allow in <code>solr.xml</code> using the new <code>allowPaths</code> element, see <a href="format-of-solr-xml.html#the-solr-element">Solr.xml Parameters</a>. When using the <code>solr.xml</code> file shipping with 8.6, you can configure the list of paths to allow through the system property <code>solr.allowPaths</code>. Please see <code>bin/solr.in.sh</code> or <code>bin\solr.in.cmd</code> for example usage. Using the value <code>*</code> will allow any path as in erlier versions.</p>
-<p>Windows SMB shares on the UNC format, such as <code>\\myhost\myshare\mypath</code> are now always disallowed. Please use drive letter mounts instead, i.e. <code>S:\mypath</code>.</p>
<p><strong>Deprecations</strong></p>
-<div class="ulist"><ul><li>Cross Data Center Replication (CDCR), in its current form, is deprecated and is scheduled to be removed in 9.0. Please refer to SOLR-14022.</li><li>Data Import Handler is deprecated and is scheduled to be removed in 9.0. A community supported version of this may be available as an external package to be used with the package management system. For more details, please refer to SOLR-14066.</li><li>HDFS support in Solr is deprecated and is scheduled to be removed in 9.0. A community supported version of this may be available as an external package to be used with the package management system. For more details, please refer to SOLR-14021.</li></ul></div></section>
-<section class="sect2"><h3 id="solr-8-5">Solr 8.5</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote85">8.5 Release Notes</a>
+<p>A primary focus of the community is improving Solr’s stability and supportability.
+With the addition of the package manager system in 8.4, we now have the ability to move some features into plugins maintained by third-parties with the expertise to properly develop and support them.
+Our goal is to make running Solr easier and less prone to outages and other headaches.
+In this spirit, the following features have been deprecated and are slated to be removed in Solr 9.0.</p>
+<div class="ulist"><ul><li><p>Cross Data Center Replication (CDCR), in its current form, is deprecated and is scheduled to be removed in 9.0.
+This feature is unlikely to be replaced by an identical plugin.
+However, the community is working on figuring out a replacement feature for disaster recovery and failover.</p></li><li><p>The Data Import Handler (DIH) is deprecated and is scheduled to be removed in 9.0.
+Work to replace DIH with a community-supported plugin is underway and may be available soon.</p></li><li><p>Support to store indexes and backups in HDFS is deprecated and is scheduled to be removed in 9.0.
+A community-supported version of this may be available as a plugin in the future.
+For more details, please see <a href="https://issues.apache.org/jira/browse/SOLR-14021" target="_blank" rel="noopener">SOLR-14021</a>.</p></li></ul></div>
+<p>Users interested in maintaining a feature as a plugin are encouraged to join the <a href="https://lucene.apache.org/solr/community.html#mailing-lists-irc" target="_blank" rel="noopener">developer mailing list</a> to find out more about how to help.</p></section>
+<section class="sect2"><h3 id="solr-8-5">Solr 8.5</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote85" target="_blank" rel="noopener">8.5 Release Notes</a>
for an overview of the main new features of Solr 8.5.</p>
<p>When upgrading to 8.5.x users should be aware of the following major changes from 8.4.</p>
<p><em>Note: an index incompatibility warning was retroactively added below to 8.4 for users choosing a non-default postings format (e.g., "FST50").</em></p>
@@ -1719,13 +1729,13 @@ operations, to communicate operation res
<p>This change wonât require you to change any client-side code you should see no differences on the client side.
However, it does require some care when upgrading an existing SolrCloud cluster depending on your upgrade strategy.</p>
<p>If you are upgrading Solr with an atomic restart strategy:</p>
-<div class="ulist"><ul><li>If you donât use async or REQUESTSTATUS operations, you should be able to restart and not see any issues.</li><li>If you do use Collection API operations:<ol class="arabic"><li>Pause Collection API operations.</li><li>Cleanup queues (See the section <a href="collections-api.html#deletestatus">DELETESTATUS</a> for examples)
-if you use async operations.</li><li>Upgrade and restart the nodes.</li><li>Resume all normal operations.</li></ol></li></ul></div>
+<div class="ulist"><ul><li><p>If you donât use async or REQUESTSTATUS operations, you should be able to restart and not see any issues.</p></li><li><p>If you do use Collection API operations:<ol class="arabic"><li>Pause Collection API operations.</li><li>Cleanup queues (See the section <a href="collections-api.html#deletestatus">DELETESTATUS</a> for examples)
+if you use async operations.</li><li>Upgrade and restart the nodes.</li><li>Resume all normal operations.</li></ol></p></li></ul></div>
<p>If you are upgrading Solr with a rolling restart strategy:</p>
-<div class="ulist"><ul><li>If you donât use Collection API operations, you should be able to do a rolling restart and not see
-any issues.</li><li>If you do use Collection API operations, but you can pause their use during the restart the easiest
+<div class="ulist"><ul><li><p>If you donât use Collection API operations, you should be able to do a rolling restart and not see
+any issues.</p></li><li><p>If you do use Collection API operations, but you can pause their use during the restart the easiest
way is to:<ol class="arabic"><li>Pause Collection API operations.</li><li>Upgrade and restart all nodes.</li><li>Cleanup queues (See the section <a href="collections-api.html#deletestatus">DELETESTATUS</a> for examples)
-if you use async operations.</li><li>Resume all normal operations.</li></ol></li></ul></div>
+if you use async operations.</li><li>Resume all normal operations.</li></ol></p></li></ul></div>
<p>If you use Collection API operations and canât pause them during the upgrade:</p>
<div class="olist arabic"><ol class="arabic"><li>Start 8.5 nodes with the system property: <code>-Dsolr.useUnsafeOverseerResponse=deserialization</code>. Ensure the
Overseer node is upgraded last.</li><li>Once all nodes are in 8.5 and once you donât need to read old status anymore, restart again removing the
@@ -1748,7 +1758,7 @@ More information about this is available
<p><strong>Indexing Log Files</strong></p>
<p>Solr now includes a command line tool, <code>bin/postlogs</code> which will index Solr’s log files into a collection.
This provides an easy way to use Solr or visualization tools (such as Zeppelin) to troubleshoot problems with the system.</p>
-<p>This tool is not yet officially documented in the Reference Guide, but draft documentation is available in a branch and can be accessed <a href="https://github.com/apache/lucene-solr/blob/visual-guide/solr/solr-ref-guide/src/logs.adoc">via GitHub</a>.</p>
+<p>This tool is not yet officially documented in the Reference Guide, but draft documentation is available in a branch and can be accessed <a href="https://github.com/apache/lucene-solr/blob/visual-guide/solr/solr-ref-guide/src/logs.adoc" target="_blank" rel="noopener">via GitHub</a>.</p>
<p><strong>Highlighting</strong></p>
<p>Solr’s Unified Highlighter now has two parameters to help control passage sizing, <code>hl.fragAlignRatio</code> and <code>hl.fragsizeIsMinimum</code>.
See the section <a href="highlighting.html#the-unified-highlighter">The Unified Highlighter</a> for details about these new parameters.
@@ -1758,7 +1768,7 @@ See the 8.6 upgrade notes for advise you
<p><strong>Shared Library System Parameter</strong></p>
<p>Solr’s <code>solr.xml</code> file has long had support for a <code>sharedLib</code> parameter, which allows you to define a common location for .jar files that may need to be in the path for all cores.</p>
<p>This property can now be defined in <code>solr.in.sh</code> or <code>solr.in.cmd</code> as a system property (<code>-Dsolr.sharedLib=/path/to/lib</code>) added to <code>SOLR_OPTS</code> (see <code>solr.in.sh</code> or <code>solr.in.cmd</code> for details).</p></section>
-<section class="sect2"><h3 id="solr-8-4">Solr 8.4</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote84">8.4 Release Notes</a>
+<section class="sect2"><h3 id="solr-8-4">Solr 8.4</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote84" target="_blank" rel="noopener">8.4 Release Notes</a>
for an overview of the main new features of Solr 8.4.</p>
<p>When upgrading to 8.4.x users should be aware of the following major changes from 8.3.</p>
<p><strong>Reminder:</strong> If you set the <code>postingsFormat</code> or <code>docValuesFormat</code> in the schema in order to use a non-default option, you risk preventing yourself from upgrading your Lucene/Solr software at future versions.
@@ -1780,24 +1790,24 @@ For details, please see the section <a h
functionality is now deprecated and will likely be removed in 9.0.</p>
<p><strong>Security</strong></p>
<p>The follow mix of changes were all made with the intention of making Solr more secure out of the box.</p>
-<div class="ulist"><ul><li>The <code>solrconfig.xml</code> file in Solr’s <code>_default</code> configset has been trimmed of
-the following previously pre-configured items:<ul><li>All <code><lib …​/></code> directives. This means that Solr Cell (aka Tika), Learning
+<div class="ulist"><ul><li><p>The <code>solrconfig.xml</code> file in Solr’s <code>_default</code> configset has been trimmed of
+the following previously pre-configured items:<ul><li><p>All <code><lib …​/></code> directives. This means that Solr Cell (aka Tika), Learning
to Rank, Clustering (with Carrot2), language identification, and Velocity (for
-the <code>/browse</code> sample search interface) are no longer enabled out of the box.</li><li>The <code>/browse</code>, <code>/tvrh</code>, and <code>/update/extract</code> request handlers.</li><li>The Term Vector Component.</li><li><p>The XSLT and Velocity response writers.</p><p>All of these items can be added to your Solr implementation by manually editing
+the <code>/browse</code> sample search interface) are no longer enabled out of the box.</p></li><li><p>The <code>/browse</code>, <code>/tvrh</code>, and <code>/update/extract</code> request handlers.</p></li><li><p>The Term Vector Component.</p></li><li><p><p>The XSLT and Velocity response writers.</p><p>All of these items can be added to your Solr implementation by manually editing
<code>solrconfig.xml</code> to add them back in, or use the <a href="config-api.html#config-api">Config API</a>.</p>
-<p>The <code>sample_techproducts_configs</code> and the examples found in <code>./example</code> are unchanged.</p></li></ul></li><li><p>Configsets that have been uploaded with an unsecured Configset API (i.e., when authentication is not enabled) are considered "Untrusted Configsets".</p><p>In order to bolster Solr’s out-of-the-box security, these untrusted configsets
+<p>The <code>sample_techproducts_configs</code> and the examples found in <code>./example</code> are unchanged.</p></p></li></ul></p></li><li><p><p>Configsets that have been uploaded with an unsecured Configset API (i.e., when authentication is not enabled) are considered "Untrusted Configsets".</p><p>In order to bolster Solr’s out-of-the-box security, these untrusted configsets
are no longer allowed to use the <code><lib …​/></code> directive to implement contribs
or custom Jars.</p>
<p>When upgrading to 8.4, if you are using untrusted configsets that contain <code><lib ../></code>
directives, their corresponding collections will not load (they will cease to
work). You have a few options in this case:</p>
-<ul><li>You can secure your Solr instance with <a href="authentication-and-authorization-plugins.html#authentication-and-authorization-plugins">authentication</a>
+<ul><li><p>You can secure your Solr instance with <a href="authentication-and-authorization-plugins.html#authentication-and-authorization-plugins">authentication</a>
and re-upload the configset (using the <code>bin/solr zk upconfig …​</code>
-<a href="solr-control-script-reference.html#solr-control-script-reference">Solr CLI</a> command);</li><li>You can put your custom Jars in Solr’s classpath instead of <code>lib</code> directories;</li><li><p>You can try the new package management system to manage your custom Jars.</p><p>See the section <a href="configsets-api.html#configsets-upload">Upload a Configset</a>
- for more details about trusted vs. untrusted configsets.</p></li></ul></li><li><p>Our default Jetty configuration has been updated to now set a
+<a href="solr-control-script-reference.html#solr-control-script-reference">Solr CLI</a> command);</p></li><li><p>You can put your custom Jars in Solr’s classpath instead of <code>lib</code> directories;</p></li><li><p><p>You can try the new package management system to manage your custom Jars.</p><p>See the section <a href="configsets-api.html#configsets-upload">Upload a Configset</a>
+ for more details about trusted vs. untrusted configsets.</p></p></li></ul></p></li><li><p><p>Our default Jetty configuration has been updated to now set a
Content-Security-Policy (CSP) by default. See <code>./server/etc/jetty.xml</code> for
details about how it is configured.</p><p>As a result of this change, any custom HTML served by Solr’s HTTP server that contains inline Javascript will no longer execute in modern browsers. The options for you are:</p>
-<ul><li>Change your JavaScript code to not run inline any longer;</li><li>Edit <code>jetty.xml</code> to remove CSP (creating weaker security protection);</li><li>Remove/alter the headers with a reverse proxy.</li></ul></li><li>Solr’s Blob Store and runtime libs functionality are now deprecated and are planned to be removed from Solr in version 9.0. It has been replaced with the new package management system.</li><li>The Velocity response writer is also now deprecated and is planned to be removed from Solr in version 9.0.</li></ul></div>
+<ul><li><p>Change your JavaScript code to not run inline any longer;</p></li><li><p>Edit <code>jetty.xml</code> to remove CSP (creating weaker security protection);</p></li><li><p>Remove/alter the headers with a reverse proxy.</p></li></ul></p></li><li><p>Solr’s Blob Store and runtime libs functionality are now deprecated and are planned to be removed from Solr in version 9.0. It has been replaced with the new package management system.</p></li><li><p>The Velocity response writer is also now deprecated and is planned to be removed from Solr in version 9.0.</p></li></ul></div>
<p><strong>Using Collapse with Group Disallowed</strong></p>
<p>Using the <a href="collapse-and-expand-results.html#collapse-and-expand-results">CollapsingQueryParser</a>
with <a href="result-grouping.html#result-grouping">Result Grouping</a> has never been
@@ -1805,21 +1815,21 @@ supported as it causes inconsistent beha
We have now explicitly disallowed this combination to prevent these errors.
If you are using these together, you will need to modify your queries.</p>
<p><strong>SolrJ</strong></p>
-<div class="ulist"><ul><li><p>SolrJ now supports the <code>shards.preference</code> parameter for single-shard
+<div class="ulist"><ul><li><p><p>SolrJ now supports the <code>shards.preference</code> parameter for single-shard
scenarios to ensure multi-shard and single-shard request routing works in the same way.</p><p>See <a href="using-solrj.html#cloud-request-routing">Cloud Request Routing</a> and
-<a href="distributed-requests.html#shards-preference-parameter">shards.preference Parameter</a> for details.</p></li><li><p><code>QueryResponse.getExplainMap()</code> type has changed from <code>Map<String, String></code> to <code>Map<String, Object></code> in order to support structured explanations.</p><p>This change is expected to be mostly back-compatible. Compiled third-party
+<a href="distributed-requests.html#shards-preference-parameter">shards.preference Parameter</a> for details.</p></p></li><li><p><p><code>QueryResponse.getExplainMap()</code> type has changed from <code>Map<String, String></code> to <code>Map<String, Object></code> in order to support structured explanations.</p><p>This change is expected to be mostly back-compatible. Compiled third-party
components will work the same due to type erasure, but source code changes may
-be required.</p></li><li>Replica routing code has been moved to SolrJ, making those classes available
-to clients if necessary.</li></ul></div>
+be required.</p></p></li><li><p>Replica routing code has been moved to SolrJ, making those classes available
+to clients if necessary.</p></li></ul></div>
<p><strong>Streaming Expressions</strong></p>
-<div class="ulist"><ul><li>A new DBSCAN clustering streaming evaluator has been added.</li><li>The <code>precision</code> stream evaluator can now operate on matrices.</li><li>The <code>random</code> streaming expression can now create the x-axis.</li></ul></div>
+<div class="ulist"><ul><li><p>A new DBSCAN clustering streaming evaluator has been added.</p></li><li><p>The <code>precision</code> stream evaluator can now operate on matrices.</p></li><li><p>The <code>random</code> streaming expression can now create the x-axis.</p></li></ul></div>
<p><strong>JSON Facets</strong></p>
-<div class="ulist"><ul><li>Two new aggregations have been added: <code>missing</code> and <code>countvals</code>.</li><li>Several aggregations now support multi-valued fields: <code>min</code>, <code>max</code>, <code>avg</code>, <code>sum</code>, <code>sumsq</code>, <code>stddev</code>, <code>variance</code>, and <code>percentile</code>.</li></ul></div>
+<div class="ulist"><ul><li><p>Two new aggregations have been added: <code>missing</code> and <code>countvals</code>.</p></li><li><p>Several aggregations now support multi-valued fields: <code>min</code>, <code>max</code>, <code>avg</code>, <code>sum</code>, <code>sumsq</code>, <code>stddev</code>, <code>variance</code>, and <code>percentile</code>.</p></li></ul></div>
<p><strong>Caches</strong></p>
-<div class="ulist"><ul><li><p>After the addition of <code>CaffeineCache</code> in 8.3, legacy SolrCache
+<div class="ulist"><ul><li><p><p>After the addition of <code>CaffeineCache</code> in 8.3, legacy SolrCache
implementations are deprecated and likely to be removed in 9.0.</p><p>Users are encouraged to transition their cache configurations to use
-<code>org.apache.solr.search.CaffeineCache</code> as soon as feasible.</p></li></ul></div></section>
-<section class="sect2"><h3 id="solr-8-3">Solr 8.3</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote83">8.3 Release Notes</a> for an overview of the main new features of Solr 8.3.</p>
+<code>org.apache.solr.search.CaffeineCache</code> as soon as feasible.</p></p></li></ul></div></section>
+<section class="sect2"><h3 id="solr-8-3">Solr 8.3</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote83" target="_blank" rel="noopener">8.3 Release Notes</a> for an overview of the main new features of Solr 8.3.</p>
<p>When upgrading to 8.3.x users should be aware of the following major changes from 8.2.</p>
<p><strong>JWT Authentication</strong></p>
<p>JWT Authentication now supports multiple identity providers.
@@ -1828,12 +1838,12 @@ Implementations using <code>jwkUrl</code
should plan to transition their configurations to use <code>jwksUrl</code> instead as
soon as feasible.</p>
<p><strong>Caches</strong></p>
-<div class="ulist"><ul><li><p>Solr has a new cache implementation, <code>CaffeineCache</code>, which is now recommended over other caches. This cache is expected to generally provide most users lower memory footprint, higher hit ratio, and better multi-threaded performance.</p><p>Since caching has a direct impact on the performance of your Solr
+<div class="ulist"><ul><li><p><p>Solr has a new cache implementation, <code>CaffeineCache</code>, which is now recommended over other caches. This cache is expected to generally provide most users lower memory footprint, higher hit ratio, and better multi-threaded performance.</p><p>Since caching has a direct impact on the performance of your Solr
implementation, before switching to any new cache implementation in
production, take care to test for your environment and traffic patterns so
- you fully understand the ramifications of the change.</p></li><li>A new parameter, <code>maxIdleTime</code>, allows automatic eviction of cache items that have not been used in the defined amount of time. This allows the cache to release some memory and should aid those who want or need to fine-tune their caches.</li></ul></div>
+ you fully understand the ramifications of the change.</p></p></li><li><p>A new parameter, <code>maxIdleTime</code>, allows automatic eviction of cache items that have not been used in the defined amount of time. This allows the cache to release some memory and should aid those who want or need to fine-tune their caches.</p></li></ul></div>
<p>See the section <a href="query-settings-in-solrconfig.html#query-settings-in-solrconfig">Query Settings in SolrConfig</a> for more details about these and other cache options and parameters.</p></section>
-<section class="sect2"><h3 id="solr-8-2">Solr 8.2</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote82">8.2 Release Notes</a> for an overview of the main new features of Solr 8.2.</p>
+<section class="sect2"><h3 id="solr-8-2">Solr 8.2</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote82" target="_blank" rel="noopener">8.2 Release Notes</a> for an overview of the main new features of Solr 8.2.</p>
<p>When upgrading to 8.2.x, users should be aware of the following major changes from v8.1.</p>
<p><strong>ZooKeeper 3.5.5</strong></p>
<p>Solr 8.2 updates the version of ZooKeeper included with Solr to v3.5.5.</p>
@@ -1855,33 +1865,33 @@ Until 8.3, <a href="https://issues.apach
</table>
</div>
<p><strong>Routed Aliases</strong></p>
-<div class="ulist"><ul><li><p>Routed aliases now use collection properties to identify collections that belong to the alias; prior to 8.2, these aliases used core properties.</p><p>This is backward-compatible and aliases created with prior versions will
+<div class="ulist"><ul><li><p><p>Routed aliases now use collection properties to identify collections that belong to the alias; prior to 8.2, these aliases used core properties.</p><p>This is backward-compatible and aliases created with prior versions will
continue to work. However, new collections will no longer add the
<code>routedAliasName</code> property to the <code>core.properties</code> file so any external code
- depending on this location will need to be updated.</p></li></ul></div>
-<div class="ulist"><ul><li>Time-routed aliases now include a <code>TRA</code> infix in the collection name, in the pattern <code><alias>_TRA_<timestamp></code>.<br>
-Collections created with older versions will continue to work.</li></ul></div>
+ depending on this location will need to be updated.</p></p></li></ul></div>
+<div class="ulist"><ul><li><p>Time-routed aliases now include a <code>TRA</code> infix in the collection name, in the pattern <code><alias>_TRA_<timestamp></code>.<br>
+Collections created with older versions will continue to work.</p></li></ul></div>
<p><strong>Distributed Tracing Support</strong></p>
<p>This release adds support for tracing requests in Solr. Please review the section <a href="solr-tracing.html#solr-tracing">Distributed Solr Tracing</a> for details on how to configure this feature.</p></section>
-<section class="sect2"><h3 id="solr-8-1">Solr 8.1</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote810">8.1 Release Notes</a> for an overview of the main new features of Solr 8.1.</p>
+<section class="sect2"><h3 id="solr-8-1">Solr 8.1</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/SOLR/ReleaseNote810" target="_blank" rel="noopener">8.1 Release Notes</a> for an overview of the main new features of Solr 8.1.</p>
<p>When upgrading to 8.1.x, users should be aware of the following major changes from v8.0.</p>
<p><strong>Global maxBooleanClauses Parameter</strong></p>
-<div class="ulist"><ul><li><p>The behavior of the <code>maxBooleanClauses</code> parameter has changed to reduce the risk of exponential query expansion when dealing with pathological query strings.</p><p>A default upper limit of 1024 clauses is now enforced at the node level. This was the default prior to 7.0, and it can be overridden with a new global parameter in <code>solr.xml</code>. This limit will be enforced for all queries whether explicitly defined by the user (or client), or created by Solr and Lucene internals.</p>
+<div class="ulist"><ul><li><p><p>The behavior of the <code>maxBooleanClauses</code> parameter has changed to reduce the risk of exponential query expansion when dealing with pathological query strings.</p><p>A default upper limit of 1024 clauses is now enforced at the node level. This was the default prior to 7.0, and it can be overridden with a new global parameter in <code>solr.xml</code>. This limit will be enforced for all queries whether explicitly defined by the user (or client), or created by Solr and Lucene internals.</p>
<p>An identical parameter is available in <code>solrconfig.xml</code> for limiting the size of queries explicitly defined by the user (or client), but this per-collection limit will still be restricted by the global limit set in <code>solr.xml</code>.</p>
<p>If your use case demands that you a lot of OR or AND clauses in your queries, upon upgrade to 8.1 you may need to adjust the global <code>maxBooleanClauses</code> parameter since between 7.0 and 8.1 the limit was effectively unbounded.</p>
-<p>For more information about the new parameter, see the section <a href="format-of-solr-xml.html#global-maxbooleanclauses">Format of solr.xml: maxBooleanClauses</a>.</p></li></ul></div>
+<p>For more information about the new parameter, see the section <a href="format-of-solr-xml.html#global-maxbooleanclauses">Format of solr.xml: maxBooleanClauses</a>.</p></p></li></ul></div>
<p><strong>Security</strong></p>
-<div class="ulist"><ul><li>JSON Web Tokens (JWT) are now supported for authentication. These allow Solr to assert a user is already authenticated via an external identity provider, such as an OpenID Connect-enabled IdP. For more information, see the section <a href="jwt-authentication-plugin.html#jwt-authentication-plugin">JWT Authentication Plugin</a>.</li><li>A new security plugin for audit logging has been added. A default class <code>SolrLogAuditLoggerPlugin</code> is available and configurable in <code>security.json</code>. The base class is also extendable for adding custom audit plugins if needed. See the section <a href="audit-logging.html#audit-logging">Audit Logging</a> for more information.</li></ul></div>
+<div class="ulist"><ul><li><p>JSON Web Tokens (JWT) are now supported for authentication. These allow Solr to assert a user is already authenticated via an external identity provider, such as an OpenID Connect-enabled IdP. For more information, see the section <a href="jwt-authentication-plugin.html#jwt-authentication-plugin">JWT Authentication Plugin</a>.</p></li><li><p>A new security plugin for audit logging has been added. A default class <code>SolrLogAuditLoggerPlugin</code> is available and configurable in <code>security.json</code>. The base class is also extendable for adding custom audit plugins if needed. See the section <a href="audit-logging.html#audit-logging">Audit Logging</a> for more information.</p></li></ul></div>
<p><strong>Collections API</strong></p>
-<div class="ulist"><ul><li>The output of the REQUESTSTATUS command in the Collections API will now include internal asynchronous requests (if any) in the "success" or "failed" keys.</li><li>The CREATE command will now return the appropriate status code (4xx, 5xx, etc.) when the command has failed. Previously, it always returned <code>0</code>, even in failure.</li><li>The MODIFYCOLLECTION command now accepts an attribute to set a collection as read-only. This can be used to block a collection from receiving any updates while still allowing queries to be served. See the section <a href="collection-management.html#modifycollection">MODIFYCOLLECTION</a> for details on how to use it.</li><li>A new command RENAME allows renaming a collection by setting up a one-to-one alias using the new name. For more information, see the section <a href="collection-management.html#rename">RENAME</a>.</li><li>A new command REINDEXCOLLECTION allows indexing existing stored fields from a source collection
into a new collection. For more information, please see the section <a href="collection-management.html#reindexcollection">REINDEXCOLLECTION</a>.</li></ul></div>
+<div class="ulist"><ul><li><p>The output of the REQUESTSTATUS command in the Collections API will now include internal asynchronous requests (if any) in the "success" or "failed" keys.</p></li><li><p>The CREATE command will now return the appropriate status code (4xx, 5xx, etc.) when the command has failed. Previously, it always returned <code>0</code>, even in failure.</p></li><li><p>The MODIFYCOLLECTION command now accepts an attribute to set a collection as read-only. This can be used to block a collection from receiving any updates while still allowing queries to be served. See the section <a href="collection-management.html#modifycollection">MODIFYCOLLECTION</a> for details on how to use it.</p></li><li><p>A new command RENAME allows renaming a collection by setting up a one-to-one alias using the new name. For more information, see the section <a href="collection-management.html#rename">RENAME</a>.</p></li><li><p>A new command REINDEXCOLLECTION allows indexing existing stored
fields from a source collection into a new collection. For more information, please see the section <a href="collection-management.html#reindexcollection">REINDEXCOLLECTION</a>.</p></li></ul></div>
<p><strong>Logging</strong></p>
-<div class="ulist"><ul><li><p>The default Log4j2 logging mode has been changed from synchronous to asynchronous. This will improve logging throughput and reduce system contention at the cost of a <em>slight</em> chance that some logging messages may be missed in the event of abnormal Solr termination.</p><p>If even this slight risk is unacceptable, the Log4j configuration file found in <code>server/resources/log4j2.xml</code> has the synchronous logging configuration in a commented section and can be edited to re-enable synchronous logging.</p></li></ul></div>
+<div class="ulist"><ul><li><p><p>The default Log4j2 logging mode has been changed from synchronous to asynchronous. This will improve logging throughput and reduce system contention at the cost of a <em>slight</em> chance that some logging messages may be missed in the event of abnormal Solr termination.</p><p>If even this slight risk is unacceptable, the Log4j configuration file found in <code>server/resources/log4j2.xml</code> has the synchronous logging configuration in a commented section and can be edited to re-enable synchronous logging.</p></p></li></ul></div>
<p><strong>Metrics</strong></p>
-<div class="ulist"><ul><li>The SolrGangliaReporter has been removed from Solr. The metrics library used by Solr, Dropwizard Metrics, was updated to version 4, and Ganglia support was removed from it due to a dependency on the LGPL license.</li></ul></div>
+<div class="ulist"><ul><li><p>The SolrGangliaReporter has been removed from Solr. The metrics library used by Solr, Dropwizard Metrics, was updated to version 4, and Ganglia support was removed from it due to a dependency on the LGPL license.</p></li></ul></div>
<p><strong>Browse UI (Velocity)</strong></p>
-<div class="ulist"><ul><li>Velocity and Velocity Tools were both upgraded as part of this release. Velocity upgraded from 1.7 to 2.0. Please see <a class="bare" href="https://velocity.apache.org/engine/2.0/upgrading.html">https://velocity.apache.org/engine/2.0/upgrading.html</a> about upgrading. Velocity Tools upgraded from 2.0 to 3.0. For more details, please see <a class="bare" href="https://velocity.apache.org/tools/3.0/upgrading.html">https://velocity.apache.org/tools/3.0/upgrading.html</a> for details about the upgrade.</li></ul></div>
+<div class="ulist"><ul><li><p>Velocity and Velocity Tools were both upgraded as part of this release. Velocity upgraded from 1.7 to 2.0. Please see <a class="bare" href="https://velocity.apache.org/engine/2.0/upgrading.html">https://velocity.apache.org/engine/2.0/upgrading.html</a> about upgrading. Velocity Tools upgraded from 2.0 to 3.0. For more details, please see <a class="bare" href="https://velocity.apache.org/tools/3.0/upgrading.html">https://velocity.apache.org/tools/3.0/upgrading.html</a> for details about the upgrade.</p></li></ul></div>
<p><strong>Default Garbage Collector (GC)</strong></p>
-<div class="ulist"><ul><li>Solr’s default GC has been changed from CMS to G1. If you prefer to use CMS or any other GC method, you can modify the <code>GC_TUNE</code> section of <code>solr.in.sh</code> (*nix) or <code>solr.in.cmd</code> (Windows).</li></ul></div></section></section>
+<div class="ulist"><ul><li><p>Solr’s default GC has been changed from CMS to G1. If you prefer to use CMS or any other GC method, you can modify the <code>GC_TUNE</code> section of <code>solr.in.sh</code> (*nix) or <code>solr.in.cmd</code> (Windows).</p></li></ul></div></section></section>
<section class="sect1"><h2 id="upgrading-from-7-x-releases">Upgrading from 7.x Releases</h2><p>The upgrade from 7.x to Solr 8.0 introduces several major changes that you should be aware of before upgrading.
These changes are described in the section <a href="major-changes-in-solr-8.html#major-changes-in-solr-8">Major Changes in Solr 8</a>. It’s strongly recommended that you do a thorough review of that section before starting your upgrade.</p>
<div class="admonitionblock note">
@@ -1928,7 +1938,7 @@ If you run in SolrCloud mode, you must b
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>
Modified: websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-api.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-api.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-api.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Autoscaling API | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Autoscaling API | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="solrcloud-autoscaling-api">
+<body class="" id="solrcloud-autoscaling-api">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1930,7 +1925,7 @@
</span><span style="color: #000080">"WARNING"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"This response format is experimental. It is likely to change in the future."</span><span style="background-color: #f8f8f8">}</span></code></pre></code></pre></div>
<p>The suggested <code>operation</code> is an API call that can be invoked to remedy the current violation.</p>
<p>The types of suggestions available are</p>
-<div class="ulist"><ul><li><code>violation</code>: Fixes a violation to one or more policy rules</li><li><code>repair</code>: Add missing replicas</li><li><code>improvement</code>: move replicas around so that the load is more evenly balanced according to the autoscaling preferences</li></ul></div>
+<div class="ulist"><ul><li><p><code>violation</code>: Fixes a violation to one or more policy rules</p></li><li><p><code>repair</code>: Add missing replicas</p></li><li><p><code>improvement</code>: move replicas around so that the load is more evenly balanced according to the autoscaling preferences</p></li></ul></div>
<p>By default, the suggestions API returns all of the above, in that order. However it is possible to fetch only certain types by adding a request parameter <code>type</code>. e.g: <code>type=violation&type=repair</code></p>
<section class="sect2"><h3 id="inline-policy-configuration-2">Inline Policy Configuration</h3><p>If there is no autoscaling policy configured or if you wish to use a configuration other than the default, it is possible to send the autoscaling policy JSON as an inline payload as follows:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code>curl -X POST -H <span style="color: #d14">'Content-type:application/json'</span> -d <span style="color: #d14">'{
@@ -2256,7 +2251,7 @@ A changed value can be unset by using a
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>
Modified: websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-auto-add-replicas.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-auto-add-replicas.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-auto-add-replicas.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>SolrCloud Autoscaling Automatically Adding Replicas | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>SolrCloud Autoscaling Automatically Adding Replicas | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="solrcloud-autoscaling-auto-add-replicas">
+<body class="" id="solrcloud-autoscaling-auto-add-replicas">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1727,7 +1722,7 @@ If this cluster property is missing or s
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>
Modified: websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-fault-tolerance.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-fault-tolerance.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-fault-tolerance.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>SolrCloud Autoscaling Fault Tolerance | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>SolrCloud Autoscaling Fault Tolerance | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="solrcloud-autoscaling-fault-tolerance">
+<body class="" id="solrcloud-autoscaling-fault-tolerance">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1718,7 +1713,7 @@ normally. Queued events that fail proces
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>
Modified: websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-listeners.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-listeners.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-listeners.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>SolrCloud Autoscaling Listeners | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>SolrCloud Autoscaling Listeners | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="solrcloud-autoscaling-listeners">
+<body class="" id="solrcloud-autoscaling-listeners">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1675,8 +1670,8 @@ particular type of event occurs or when
events generated by that specific trigger. Several (or none) named listeners can be registered for a trigger,
and they will be notified in the order in which they were defined.</p>
<p>Listener configuration can specify what processing stages are of interest, and when an event enters this processing stage the listener will be notified. Currently the following stages are recognized:</p>
-<div class="ulist"><ul><li>STARTED - when an event has been generated by a trigger and its processing is starting.</li><li>ABORTED - when event was being processed while the source trigger closed.</li><li>BEFORE_ACTION - when a <code>TriggerAction</code> is about to be invoked. Action name and the current <code>ActionContext</code> are passed to the listener.</li><li>AFTER_ACTION - after a <code>TriggerAction</code> has been successfully invoked. Action name, <code>ActionContext</code> and the list of action
-names invoked so far are passed to the listener.</li><li>FAILED - when event processing failed (or when a <code>TriggerAction</code> failed)</li><li>SUCCEEDED - when event processing completes successfully</li></ul></div>
+<div class="ulist"><ul><li><p>STARTED - when an event has been generated by a trigger and its processing is starting.</p></li><li><p>ABORTED - when event was being processed while the source trigger closed.</p></li><li><p>BEFORE_ACTION - when a <code>TriggerAction</code> is about to be invoked. Action name and the current <code>ActionContext</code> are passed to the listener.</p></li><li><p>AFTER_ACTION - after a <code>TriggerAction</code> has been successfully invoked. Action name, <code>ActionContext</code> and the list of action
+names invoked so far are passed to the listener.</p></li><li><p>FAILED - when event processing failed (or when a <code>TriggerAction</code> failed)</p></li><li><p>SUCCEEDED - when event processing completes successfully</p></li></ul></div>
<p>Listener configuration can also specify what particular actions are of interest, both before and/or after they are invoked.</p></section>
<section class="sect1"><h2 id="listener-configuration">Listener Configuration</h2><p>Currently the following listener configuration properties are supported:</p>
<div class="dlist"><dl><dt><code>name</code></dt><dd>(string, required) A unique listener configuration name.</dd><dt><code>trigger</code></dt><dd>(string, required) The name of an existing trigger configuration.</dd><dt><code>class</code></dt><dd>(string, required) A listener implementation class name.</dd><dt><code>stage</code></dt><dd>(list of strings, optional, ignored case) A list of processing stages that
@@ -1739,12 +1734,12 @@ WARN message with the details of the eve
</table>
</div></dd><dt><code>enabled</code></dt><dd>(boolean, optional) Enables the listener when true. Default value is true.</dd></dl></div>
<p>Documents created by this listener have several predefined fields:</p>
-<div class="ulist"><ul><li><code>id</code> - time-based random id</li><li><code>type</code> - always set to <code>autoscaling_event</code></li><li><code>source_s</code> - always set to <code>SystemLogListener</code></li><li><code>timestamp</code> - current time when document was created</li><li><code>stage_s</code> - current stage of event processing</li><li><code>action_s</code> - current action name, if available</li><li><code>message_t</code> - optional additional message</li><li><code>error.message_t</code> - message from Throwable, if available</li><li><code>error.details_t</code> - stacktrace from Throwable, if available</li><li><code>before.actions_ss</code> - list of action names to be invoked so far</li><li><code>after.actions_ss</code> - list of action names that have been successfully invoked so far</li><li><code>event_str</code> - JSON representation of all event properties</li><li><code>context_str</code> - JSON representation of all <code>ActionContext</code> propertie
s, if available</li></ul></div>
+<div class="ulist"><ul><li><p><code>id</code> - time-based random id</p></li><li><p><code>type</code> - always set to <code>autoscaling_event</code></p></li><li><p><code>source_s</code> - always set to <code>SystemLogListener</code></p></li><li><p><code>timestamp</code> - current time when document was created</p></li><li><p><code>stage_s</code> - current stage of event processing</p></li><li><p><code>action_s</code> - current action name, if available</p></li><li><p><code>message_t</code> - optional additional message</p></li><li><p><code>error.message_t</code> - message from Throwable, if available</p></li><li><p><code>error.details_t</code> - stacktrace from Throwable, if available</p></li><li><p><code>before.actions_ss</code> - list of action names to be invoked so far</p></li><li><p><code>after.actions_ss</code> - list of action names that have been successfully invoked so far</p></li><li><p><code>event_str</code> - JSON representation of all event properties</p></li><li><p><co
de>context_str</code> - JSON representation of all <code>ActionContext</code> properties, if available</p></li></ul></div>
<p>The following fields are created using the information from trigger event:</p>
-<div class="ulist"><ul><li><code>event.id_s</code> - event id</li><li><code>event.type_s</code> - event type</li><li><code>event.source_s</code> - event source (trigger name)</li><li><code>event.time_l</code> - Unix time when the event was created (may significantly differ from the time when it was actually
-processed)</li><li><code>event.property.*</code> - additional fields that represent other arbitrary event properties. These fields use either
+<div class="ulist"><ul><li><p><code>event.id_s</code> - event id</p></li><li><p><code>event.type_s</code> - event type</p></li><li><p><code>event.source_s</code> - event source (trigger name)</p></li><li><p><code>event.time_l</code> - Unix time when the event was created (may significantly differ from the time when it was actually
+processed)</p></li><li><p><code>event.property.*</code> - additional fields that represent other arbitrary event properties. These fields use either
<code>_s</code> or <code>_ss</code> suffix depending on whether the property value is a collection (values inside collection are treated as
-strings, there’s no recursive flattening)</li></ul></div>
+strings, there’s no recursive flattening)</p></li></ul></div>
<p>The following configuration is used for the automatically created listener (in this case for a
trigger named <code>foo</code>):</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-json" data-lang="json"><pre class="highlight"><code><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb">
@@ -1760,7 +1755,7 @@ if the value is absent.</p>
<p>Supported configuration properties:</p>
<div class="dlist"><dl><dt><code>url</code></dt><dd>(string, required) A URL template.</dd><dt><code>payload</code></dt><dd>(string, optional) A payload template. If absent, a JSON map of all properties listed above will be used.</dd><dt><code>contentType</code></dt><dd>(string, optional) A payload content type. If absent then <code>application/json</code> will be used.</dd><dt><code>header.*</code></dt><dd>(string, optional) A header template(s). The name of the property without "header." prefix defines the literal header name.</dd><dt><code>timeout</code></dt><dd>(int, optional) Connection and socket timeout in milliseconds. Default is <code>60000</code> milliseconds (60 seconds).</dd><dt><code>followRedirects</code></dt><dd>(boolean, optional) Allows following redirects. Default is <code>false</code>.</dd></dl></div>
<p>The following properties are available in context and can be referenced from templates:</p>
-<div class="ulist"><ul><li><code>config.*</code> - listener configuration properties</li><li><code>event.*</code> - current event properties</li><li><code>stage</code> - current stage of event processing</li><li><code>actionName</code> - optional current action name</li><li><code>context.*</code> - optional ActionContext properties</li><li><code>error</code> - optional error string (from Throwable.toString())</li><li><code>message</code> - optional message</li></ul></div>
+<div class="ulist"><ul><li><p><code>config.*</code> - listener configuration properties</p></li><li><p><code>event.*</code> - current event properties</p></li><li><p><code>stage</code> - current stage of event processing</p></li><li><p><code>actionName</code> - optional current action name</p></li><li><p><code>context.*</code> - optional ActionContext properties</p></li><li><p><code>error</code> - optional error string (from Throwable.toString())</p></li><li><p><code>message</code> - optional message</p></li></ul></div>
<figure class="listingblock"><figcaption>Example HttpTriggerListener</figcaption>
<pre class="rouge highlight"><code class="language-json" data-lang="json"><pre class="highlight"><code><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb">
</span><span style="color: #000080">"name"</span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="color: #d14">"foo"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb">
@@ -1807,7 +1802,7 @@ and with a custom header that indicates
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>
Modified: websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-overview.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-overview.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/solrcloud-autoscaling-overview.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Overview of SolrCloud Autoscaling | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Overview of SolrCloud Autoscaling | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="solrcloud-autoscaling-overview">
+<body class="" id="solrcloud-autoscaling-overview">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1668,7 +1663,7 @@
<p>A simple example is automatically adding a replica for a SolrCloud collection when a node containing an existing replica goes down.</p>
<p>The goal of autoscaling in SolrCloud is to make cluster management easier, more automatic, and more intelligent. It aims to provide good defaults such that the cluster remains balanced and stable in the face of various events such as a node joining the cluster or leaving the cluster. This is achieved by satisfying a set of rules and sorting preferences that help Solr select the target of cluster management operations.</p>
<p>There are three distinct problems that this feature solves:</p>
-<div class="ulist"><ul><li>When to run cluster management tasks? For example, we might want to add a replica when an existing replica is no longer alive.</li><li>Which cluster management task to run? For example, do we add a new replica or should we move an existing one to a new node?</li><li>How do we run the cluster management tasks so the cluster remains balanced and stable?</li></ul></div>
+<div class="ulist"><ul><li><p>When to run cluster management tasks? For example, we might want to add a replica when an existing replica is no longer alive.</p></li><li><p>Which cluster management task to run? For example, do we add a new replica or should we move an existing one to a new node?</p></li><li><p>How do we run the cluster management tasks so the cluster remains balanced and stable?</p></li></ul></div>
<p>Before we get into the details of how each of these problems are solved, let’s take a quick look at the easiest way to setup autoscaling for your cluster.</p></section>
<section class="sect1"><h2 id="quick-start-automatically-adding-replicas">Quick Start: Automatically Adding Replicas</h2><p>Say that we want to create a collection which always requires us to have three replicas available for each shard all the time. We can set the <code>replicationFactor=3</code> while creating the collection, but what happens if a node containing one or more of the replicas either crashed or was shutdown for maintenance? In such a case, we’d like to create additional replicas to replace the ones that are no longer available to preserve the original number of replicas.</p>
<p>We have an easy way to enable this behavior without needing to understand the autoscaling features in depth. We can create a collection with such behavior by adding an additional parameter <code>autoAddReplicas=true</code> with the CREATE command of the Collection API. For example:</p>
@@ -1690,7 +1685,7 @@
</span><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"cores"</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="color: #d14">"#EQUAL"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"node"</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="color: #d14">"#ANY"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"strict"</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="color: #000000;font-weight: bold">false</span><span style="background-color: #f8f8f8">}</span><span style="color: #bbbbbb">
</span><span style="background-color: #f8f8f8">]</span></code></pre></code></pre></div>
<p>These rules mean that:</p>
-<div class="ulist"><ul><li>Each shard should not have more than one replica on the same node, if possible (strict: false).</li><li>Each collection’s replicas should be equally distributed among nodes.</li><li>All cores should be equally distributed among nodes.</li></ul></div>
+<div class="ulist"><ul><li><p>Each shard should not have more than one replica on the same node, if possible (strict: false).</p></li><li><p>Each collection’s replicas should be equally distributed among nodes.</p></li><li><p>All cores should be equally distributed among nodes.</p></li></ul></div>
<div class="admonitionblock note">
<table>
<tr>
@@ -1744,7 +1739,7 @@ admin request, like this: <code>{set-clu
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>