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 [13/28] - in
/websites/production/lucene/content/solr/guide/8_6: ./ meta-docs/
Modified: websites/production/lucene/content/solr/guide/8_6/major-changes-in-solr-8.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/major-changes-in-solr-8.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/major-changes-in-solr-8.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Major Changes in Solr 8 | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Major Changes in Solr 8 | 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="major-changes-in-solr-8">
+<body class="" id="major-changes-in-solr-8">
<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-->
@@ -1719,62 +1714,62 @@ with HTTP/2 and async capabilities based
<code>HttpSolrClient</code> and <code>ConcurrentUpdateSolrClient</code> for sending most internal requests (sent by
<code>UpdateShardHandler</code> and <code>HttpShardHandler</code>).</p>
<p>However this causes the following changes in configuration and authentication setup:</p>
-<div class="ulist"><ul><li>The <code>updateShardHandler</code> parameter <code>maxConnections</code> is no longer used and has been removed.</li><li>The <code>HttpShardHandler</code> parameter <code>maxConnections</code> parameter is no longer being used and has been removed.</li><li>Custom <a href="https://lucene.apache.org/solr/8_6_0//solr-core/org/apache/solr/security/AuthenticationPlugin.html"><code>AuthenticationPlugin</code></a>
+<div class="ulist"><ul><li><p>The <code>updateShardHandler</code> parameter <code>maxConnections</code> is no longer used and has been removed.</p></li><li><p>The <code>HttpShardHandler</code> parameter <code>maxConnections</code> parameter is no longer being used and has been removed.</p></li><li><p>Custom <a href="https://lucene.apache.org/solr/8_6_0//solr-core/org/apache/solr/security/AuthenticationPlugin.html"><code>AuthenticationPlugin</code></a>
implementations must provide their own setup for <code>Http2SolrClient</code> through implementing
<a href="https://lucene.apache.org/solr/8_6_0//solr-core/org/apache/solr/security/HttpClientBuilderPlugin.html"><code>HttpClientBuilderPlugin.setup</code></a>, or
-internal requests will not be able to be authenticated.</li></ul></div></section>
+internal requests will not be able to be authenticated.</p></li></ul></div></section>
<section class="sect3"><h4 id="metrics-changes-for-http2">Metrics Changes for HTTP/2</h4><p>The <code>Http2SolrClient</code> does not support exposing connection-related metrics. For this reason, the following metrics
are no longer available:</p>
-<div class="ulist"><ul><li>Metrics from <code>QUERY.httpShardHandler</code>:<ul><li><code>availableConnections</code></li><li><code>leasedConnections</code></li><li><code>maxConnections</code></li><li><code>pendingConnections</code></li></ul></li><li>Metrics from <code>UPDATE.updateShardHandler</code><ul><li><code>availableConnections</code></li><li><code>leasedConnections</code></li><li><code>maxConnections</code></li><li><code>pendingConnections</code></li></ul></li></ul></div></section></section>
+<div class="ulist"><ul><li><p>Metrics from <code>QUERY.httpShardHandler</code>:<ul><li><p><code>availableConnections</code></p></li><li><p><code>leasedConnections</code></p></li><li><p><code>maxConnections</code></p></li><li><p><code>pendingConnections</code></p></li></ul></p></li><li><p>Metrics from <code>UPDATE.updateShardHandler</code><ul><li><p><code>availableConnections</code></p></li><li><p><code>leasedConnections</code></p></li><li><p><code>maxConnections</code></p></li><li><p><code>pendingConnections</code></p></li></ul></p></li></ul></div></section></section>
<section class="sect2"><h3 id="nested-documents">Nested Documents</h3><p>Several improvements have been made for nested document support.</p>
<p>Solr now has the ability to store information about document relationships in the index. This stored information can be used for queries.</p>
<p>The Child Document Transformer can also now return children in nested form if the relationships have been properly stored in the index.</p>
<p>There are a few important changes to highlight in the context of upgrading to Solr 8:</p>
-<div class="ulist"><ul><li><p>When JSON data is sent to Solr with nested child documents split using the <code>split</code> parameter, the child documents will now be associated to their parents by the field/label string used in the JSON instead of anonymously.</p><p>Most users probably won’t notice the distinction since the label is lost unless special fields are in the schema. This choice used to be toggleable with an internal/expert <code>anonChildDocs</code> parameter flag, which has been removed.</p></li><li><p>Deleting (or updating) documents by their uniqueKey is now scoped to only consider root documents, not child/nested documents.
+<div class="ulist"><ul><li><p><p>When JSON data is sent to Solr with nested child documents split using the <code>split</code> parameter, the child documents will now be associated to their parents by the field/label string used in the JSON instead of anonymously.</p><p>Most users probably won’t notice the distinction since the label is lost unless special fields are in the schema. This choice used to be toggleable with an internal/expert <code>anonChildDocs</code> parameter flag, which has been removed.</p></p></li><li><p><p>Deleting (or updating) documents by their uniqueKey is now scoped to only consider root documents, not child/nested documents.
Thus a delete-by-id won’t work on a child document (it will fail silently), and an attempt to update a child document
by providing a new document with the same ID would add a new document (which will probably be erroneous).</p><p>Both these actions were and still are problematic. In-place-updates are safe though.
If you want to delete certain child documents and if you know they don’t themselves have nested children
-then you must do so with a delete-by-query technique.</p></li><li>Solr has a new field in the <code>_default</code> configset, called <code>_nest_path_</code>. This field stores the path of the document
-in the hierarchy for non-root documents.</li></ul></div>
+then you must do so with a delete-by-query technique.</p></p></li><li><p>Solr has a new field in the <code>_default</code> configset, called <code>_nest_path_</code>. This field stores the path of the document
+in the hierarchy for non-root documents.</p></li></ul></div>
<p>See the sections <a href="indexing-nested-documents.html#indexing-nested-documents">Indexing Nested Documents</a> and
<a href="searching-nested-documents.html#searching-nested-documents">Searching Nested Documents</a> for more information
and configuration details.</p></section></section>
<section class="sect1"><h2 id="config-changes-8">Configuration and Default Parameter Changes</h2><section class="sect2"><h3 id="schema-changes-in-8-0">Schema Changes in 8.0</h3><p>The following changes impact how fields behave.</p>
<p><strong>Default Scoring (SimilarityFactory)</strong></p>
-<div class="ulist"><ul><li><p>If you explicitly use <code>BM25SimilarityFactory</code> in your schema, the absolute scoring will be lower since Lucene changed the calculation of BM25 to remove a multiplication factor (for technical details, see <a href="https://issues.apache.org/jira/browse/LUCENE-8563">LUCENE-8563</a> or <a href="https://issues.apache.org/jira/browse/SOLR-13025">SOLR-13025</a>). Ordering of documents will not change in the normal case. Use <code>LegacyBM25SimilarityFactory</code> if you need to force the old 6.x/7.x scoring.</p><p>Note that if you have not specified any similarityFactory in the schema, or use the default
+<div class="ulist"><ul><li><p><p>If you explicitly use <code>BM25SimilarityFactory</code> in your schema, the absolute scoring will be lower since Lucene changed the calculation of BM25 to remove a multiplication factor (for technical details, see <a href="https://issues.apache.org/jira/browse/LUCENE-8563">LUCENE-8563</a> or <a href="https://issues.apache.org/jira/browse/SOLR-13025">SOLR-13025</a>). Ordering of documents will not change in the normal case. Use <code>LegacyBM25SimilarityFactory</code> if you need to force the old 6.x/7.x scoring.</p><p>Note that if you have not specified any similarityFactory in the schema, or use the default
<code>SchemaSimilarityFactory</code>, then <code>LegacyBM25Similarity</code> is automatically selected when the value for <code>luceneMatchVersion</code> is lower than <code>8.0.0</code>.</p>
-<p>See also the section <a href="other-schema-elements.html#similarity">Similarity</a> for more information.</p></li></ul></div>
+<p>See also the section <a href="other-schema-elements.html#similarity">Similarity</a> for more information.</p></p></li></ul></div>
<p><strong>Memory Codecs Removed</strong></p>
-<div class="ulist"><ul><li><p>Memory codecs have been removed from Lucene (<code>MemoryPostings</code>, <code>MemoryDocValues</code>) and are no longer available in Solr.
+<div class="ulist"><ul><li><p><p>Memory codecs have been removed from Lucene (<code>MemoryPostings</code>, <code>MemoryDocValues</code>) and are no longer available in Solr.
If you used <code>postingsFormat="Memory"</code> or <code>docValuesFormat="Memory"</code> on any field or field type configuration then either remove that setting to use the default or experiment with one of the other options.</p><p>For more information on defining a codec, see the section <a href="codec-factory.html#codec-factory">Codec Factory</a>;
-for more information on field properties, see the section <a href="field-type-definitions-and-properties.html#field-type-definitions-and-properties">Field Type Definitions and Properties</a>.</p></li></ul></div>
+for more information on field properties, see the section <a href="field-type-definitions-and-properties.html#field-type-definitions-and-properties">Field Type Definitions and Properties</a>.</p></p></li></ul></div>
<p><strong>LowerCaseTokenizer</strong></p>
-<div class="ulist"><ul><li>The <code>LowerCaseTokenizer</code> has been deprecated and is likely to be removed in Solr 9. Users are encouraged to use the <code>LetterTokenizer</code> and the <code>LowerCaseFilter</code> instead.</li></ul></div>
+<div class="ulist"><ul><li><p>The <code>LowerCaseTokenizer</code> has been deprecated and is likely to be removed in Solr 9. Users are encouraged to use the <code>LetterTokenizer</code> and the <code>LowerCaseFilter</code> instead.</p></li></ul></div>
<p><strong>Default Configset</strong></p>
-<div class="ulist"><ul><li>The <code>_default</code> configset now includes a <code>ignored_*</code> dynamic field rule.</li></ul></div></section>
+<div class="ulist"><ul><li><p>The <code>_default</code> configset now includes a <code>ignored_*</code> dynamic field rule.</p></li></ul></div></section>
<section class="sect2"><h3 id="indexing-changes-in-8-0">Indexing Changes in 8.0</h3><p>The following changes impact how documents are indexed.</p>
<p><strong>Index-time Boosts</strong></p>
-<div class="ulist"><ul><li><p>Index-time boosts were removed from <a href="major-changes-in-solr-7.html#other-deprecations-and-removals">Lucene in version 7.0</a>, and in Solr 7.x the syntax was still allowed (although it logged a warning in the logs). The syntax was similar to:</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: #000080">"id"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"1"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"val_s"</span><span style="background-color: #f8f8f8">:{</span><span style="color: #000080">"value"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"foo"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #0
00080">"boost"</span><span style="background-color: #f8f8f8">:</span><span style="color: #009999">2.0</span><span style="background-color: #f8f8f8">}}</span></code></pre></code></pre></div>
-<p>This syntax has been removed entirely and if sent to Solr it will now produce an error. This was done in conjunction with the improvements for nested document support.</p></li></ul></div>
+<div class="ulist"><ul><li><p><p>Index-time boosts were removed from <a href="major-changes-in-solr-7.html#other-deprecations-and-removals">Lucene in version 7.0</a>, and in Solr 7.x the syntax was still allowed (although it logged a warning in the logs). The syntax was similar to:</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: #000080">"id"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"1"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"val_s"</span><span style="background-color: #f8f8f8">:{</span><span style="color: #000080">"value"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"foo"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color:
#000080">"boost"</span><span style="background-color: #f8f8f8">:</span><span style="color: #009999">2.0</span><span style="background-color: #f8f8f8">}}</span></code></pre></code></pre></div>
+<p>This syntax has been removed entirely and if sent to Solr it will now produce an error. This was done in conjunction with the improvements for nested document support.</p></p></li></ul></div>
<p><strong>ParseDateFieldUpdateProcessorFactory</strong></p>
-<div class="ulist"><ul><li><p>The date format patterns used by <code>ParseDateFieldUpdateProcessorFactory</code> (used by default in "schemaless mode") are now interpreted by Java 8’s <code>java.time.DateTimeFormatter</code> instead of Joda Time.
+<div class="ulist"><ul><li><p><p>The date format patterns used by <code>ParseDateFieldUpdateProcessorFactory</code> (used by default in "schemaless mode") are now interpreted by Java 8’s <code>java.time.DateTimeFormatter</code> instead of Joda Time.
The pattern language is very similar but not the same.
Typically, simply update the pattern by changing an uppercase 'Z' to lowercase 'z' and that’s it.</p><p>For the current recommended set of patterns in schemaless mode, see the section <a href="schemaless-mode.html#schemaless-mode">Schemaless Mode</a>, or simply examine the <code>_default</code> configset (found in <code>server/solr/configsets</code>).</p>
-<p>Also note that the default set of date patterns (formats) have expanded from previous releases to subsume those patterns previously handled by the "extract" contrib (Solr Cell / Tika).</p></li></ul></div>
+<p>Also note that the default set of date patterns (formats) have expanded from previous releases to subsume those patterns previously handled by the "extract" contrib (Solr Cell / Tika).</p></p></li></ul></div>
<p><strong>Solr Cell</strong></p>
-<div class="ulist"><ul><li>The extraction contrib (<a href="uploading-data-with-solr-cell-using-apache-tika.html#uploading-data-with-solr-cell-using-apache-tika">Solr Cell</a>) no longer does any date parsing, and thus no longer supports the <code>date.formats</code> parameter. To ensure date strings are properly parsed, use the <code>ParseDateFieldUpdateProcessorFactory</code> in your update chain. This update request processor is found by default with the "parse-date" update processor when running Solr in "<a href="schemaless-mode.html#set-the-default-updaterequestprocessorchain">schemaless mode</a>".</li></ul></div>
+<div class="ulist"><ul><li><p>The extraction contrib (<a href="uploading-data-with-solr-cell-using-apache-tika.html#uploading-data-with-solr-cell-using-apache-tika">Solr Cell</a>) no longer does any date parsing, and thus no longer supports the <code>date.formats</code> parameter. To ensure date strings are properly parsed, use the <code>ParseDateFieldUpdateProcessorFactory</code> in your update chain. This update request processor is found by default with the "parse-date" update processor when running Solr in "<a href="schemaless-mode.html#set-the-default-updaterequestprocessorchain">schemaless mode</a>".</p></li></ul></div>
<p><strong>Langid Contrib</strong></p>
-<div class="ulist"><ul><li>The <code>LanguageIdentifierUpdateProcessor</code> base class in the langid contrib (found in <code>contrib/langid</code>) changed some method signatures. If you have a custom language identifier implementation you will need to adapt your code. See the Jira issue <a href="https://issues.apache.org/jira/browse/SOLR-11774">SOLR-11774</a> for details of the changes.</li></ul></div></section>
+<div class="ulist"><ul><li><p>The <code>LanguageIdentifierUpdateProcessor</code> base class in the langid contrib (found in <code>contrib/langid</code>) changed some method signatures. If you have a custom language identifier implementation you will need to adapt your code. See the Jira issue <a href="https://issues.apache.org/jira/browse/SOLR-11774">SOLR-11774</a> for details of the changes.</p></li></ul></div></section>
<section class="sect2"><h3 id="query-changes-in-8-0">Query Changes in 8.0</h3><p>The following changes impact query behavior.</p>
<p><strong>Highlighting</strong></p>
-<div class="ulist"><ul><li>The Unified Highlighter parameter <code>hl.weightMatches</code> now defaults to <code>true</code>. See the section <a href="highlighting.html#highlighting">Highlighting</a> for more information about Highlighter parameters.</li></ul></div>
+<div class="ulist"><ul><li><p>The Unified Highlighter parameter <code>hl.weightMatches</code> now defaults to <code>true</code>. See the section <a href="highlighting.html#highlighting">Highlighting</a> for more information about Highlighter parameters.</p></li></ul></div>
<p><strong>eDisMax Query Parser</strong></p>
-<div class="ulist"><ul><li>The eDisMax query parser will now thrown an error when the <code>qf</code> parameter refers to a nonexistent field.</li></ul></div>
+<div class="ulist"><ul><li><p>The eDisMax query parser will now thrown an error when the <code>qf</code> parameter refers to a nonexistent field.</p></li></ul></div>
<p><strong>Function Query Parser</strong></p>
-<div class="ulist"><ul><li>The <a href="other-parsers.html#function-query-parser">Function Query Parser</a> now returns scores that are equal to zero (0) when a negative value is produced. This change is due to the fact that Lucene now requires scores to be positive.</li></ul></div></section>
-<section class="sect2"><h3 id="authentication-security-changes-in-8-0">Authentication & Security Changes in 8.0</h3><div class="ulist"><ul><li>Authentication plugins can now intercept internode requests on a per-request basis.</li><li>The Basic Authentication plugin now has an option <code>forwardCredentials</code> to let Basic Auth headers be forwarded on inter-node requests in case of distributed search, instead of falling back to PKI.</li><li>Metrics are now reported for authentication requests.</li></ul></div></section>
-<section class="sect2"><h3 id="ui-changes-in-8-0">UI Changes in 8.0</h3><div class="ulist"><ul><li>The Radial Graph view of a Solr cluster when running in SolrCloud mode has been removed.</li><li>The Nodes view introduced in Solr 7.5 is now the default when choosing the "Cloud" tab in the left navigation menu.</li></ul></div></section>
-<section class="sect2"><h3 id="autoscaling-changes-in-8-0">Autoscaling Changes in 8.0</h3><div class="ulist"><ul><li><p>The default replica placement strategy used in Solr has been reverted to the "legacy" policy used by Solr 7.4 and previous versions. This is due to multiple bugs in the autoscaling based replica placement strategy that was made default in Solr 7.5 which causes multiple replicas of the same shard to be placed on the same node in addition to the <code>maxShardsPerNode</code> and <code>createNodeSet</code> parameters being ignored.</p><p>Although the default has changed, autoscaling will continue to be used if a cluster policy or preference is specified or a collection level policy is in use.</p>
+<div class="ulist"><ul><li><p>The <a href="other-parsers.html#function-query-parser">Function Query Parser</a> now returns scores that are equal to zero (0) when a negative value is produced. This change is due to the fact that Lucene now requires scores to be positive.</p></li></ul></div></section>
+<section class="sect2"><h3 id="authentication-security-changes-in-8-0">Authentication & Security Changes in 8.0</h3><div class="ulist"><ul><li><p>Authentication plugins can now intercept internode requests on a per-request basis.</p></li><li><p>The Basic Authentication plugin now has an option <code>forwardCredentials</code> to let Basic Auth headers be forwarded on inter-node requests in case of distributed search, instead of falling back to PKI.</p></li><li><p>Metrics are now reported for authentication requests.</p></li></ul></div></section>
+<section class="sect2"><h3 id="ui-changes-in-8-0">UI Changes in 8.0</h3><div class="ulist"><ul><li><p>The Radial Graph view of a Solr cluster when running in SolrCloud mode has been removed.</p></li><li><p>The Nodes view introduced in Solr 7.5 is now the default when choosing the "Cloud" tab in the left navigation menu.</p></li></ul></div></section>
+<section class="sect2"><h3 id="autoscaling-changes-in-8-0">Autoscaling Changes in 8.0</h3><div class="ulist"><ul><li><p><p>The default replica placement strategy used in Solr has been reverted to the "legacy" policy used by Solr 7.4 and previous versions. This is due to multiple bugs in the autoscaling based replica placement strategy that was made default in Solr 7.5 which causes multiple replicas of the same shard to be placed on the same node in addition to the <code>maxShardsPerNode</code> and <code>createNodeSet</code> parameters being ignored.</p><p>Although the default has changed, autoscaling will continue to be used if a cluster policy or preference is specified or a collection level policy is in use.</p>
<p>The default replica placement strategy can be changed to use autoscaling again by setting a cluster property:</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> --data-binary <span style="color: #d14">'
{
@@ -1785,23 +1780,23 @@ Typically, simply update the pattern by
}
}
}
- }'</span> http://<span style="color: #008080">$SOLR_HOST</span>:<span style="color: #008080">$SOLR_PORT</span>/api/cluster</code></pre></code></pre></div></li><li><p>A new command-line option is available via <code>bin/solr autoscaling</code> to calculate autoscaling policy suggestions and diagnostic information outside of the running Solr cluster. This option can use the existing autoscaling policy, or test the impact of a new one from a file located on the server filesystem.</p><p>These options have been documented in the section <a href="solrcloud-autoscaling-policy-preferences.html#testing-autoscaling-configuration-and-suggestions">Testing Autoscaling Configuration and Suggestions</a>.</p></li></ul></div></section>
-<section class="sect2"><h3 id="dependency-updates-in-8-0">Dependency Updates in 8.0</h3><div class="ulist"><ul><li>All Hadoop dependencies have been upgraded to Hadoop 3.2.0 (from 2.7.2).</li></ul></div></section></section>
+ }'</span> http://<span style="color: #008080">$SOLR_HOST</span>:<span style="color: #008080">$SOLR_PORT</span>/api/cluster</code></pre></code></pre></div></p></li><li><p><p>A new command-line option is available via <code>bin/solr autoscaling</code> to calculate autoscaling policy suggestions and diagnostic information outside of the running Solr cluster. This option can use the existing autoscaling policy, or test the impact of a new one from a file located on the server filesystem.</p><p>These options have been documented in the section <a href="solrcloud-autoscaling-policy-preferences.html#testing-autoscaling-configuration-and-suggestions">Testing Autoscaling Configuration and Suggestions</a>.</p></p></li></ul></div></section>
+<section class="sect2"><h3 id="dependency-updates-in-8-0">Dependency Updates in 8.0</h3><div class="ulist"><ul><li><p>All Hadoop dependencies have been upgraded to Hadoop 3.2.0 (from 2.7.2).</p></li></ul></div></section></section>
<section class="sect1"><h2 id="major-changes-in-earlier-7-x-versions">Major Changes in Earlier 7.x Versions</h2><p>The following is a list of major changes released between Solr 7.1 and 7.7.</p>
<p>Please be sure to review this list so you understand what may have changed between the version of Solr you are currently running and Solr 8.0.</p>
<section class="sect2"><h3 id="solr-7-7">Solr 7.7</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote77">7.7 Release Notes</a> for an overview of the main new features in Solr 7.7.</p>
<p>When upgrading to Solr 7.7.x, users should be aware of the following major changes from v7.6:</p>
<p><strong>Admin UI</strong></p>
-<div class="ulist"><ul><li><p>The Admin UI now presents a login screen for any users with authentication enabled on their cluster.
+<div class="ulist"><ul><li><p><p>The Admin UI now presents a login screen for any users with authentication enabled on their cluster.
Clusters with <a href="basic-authentication-plugin.html#basic-authentication-plugin">Basic Authentication</a> will prompt users to enter a username and password.
-On clusters configured to use <a href="kerberos-authentication-plugin.html#kerberos-authentication-plugin">Kerberos Authentication</a>, authentication is handled transparently by the browser as before, but if authentication fails, users will be directed to configure their browser to provide an appropriate Kerberos ticket.</p><p>The login screen’s purpose is cosmetic only - Admin UI-triggered Solr requests were subject to authentication prior to 7.7 and still are today. The login screen changes only the user experience of providing this authentication.</p></li></ul></div>
+On clusters configured to use <a href="kerberos-authentication-plugin.html#kerberos-authentication-plugin">Kerberos Authentication</a>, authentication is handled transparently by the browser as before, but if authentication fails, users will be directed to configure their browser to provide an appropriate Kerberos ticket.</p><p>The login screen’s purpose is cosmetic only - Admin UI-triggered Solr requests were subject to authentication prior to 7.7 and still are today. The login screen changes only the user experience of providing this authentication.</p></p></li></ul></div>
<p><strong>Distributed Requests</strong></p>
-<div class="ulist"><ul><li><p>The <code>shards</code> parameter, used to manually select the shards and replicas that receive distributed requests, now checks nodes against a whitelist of acceptable values for security reasons.</p><p>In SolrCloud mode this whitelist is automatically configured to contain all live nodes. In standalone mode the whitelist is empty by default. Upgrading users who use the <code>shards</code> parameter in standalone mode can correct this value by setting the <code>shardsWhitelist</code> property in any <code>shardHandler</code> configurations in their <code>solrconfig.xml</code> file.</p>
-<p>For more information, see the <a href="distributed-requests.html#configuring-the-shardhandlerfactory">Distributed Request</a> documentation.</p></li></ul></div></section>
+<div class="ulist"><ul><li><p><p>The <code>shards</code> parameter, used to manually select the shards and replicas that receive distributed requests, now checks nodes against a whitelist of acceptable values for security reasons.</p><p>In SolrCloud mode this whitelist is automatically configured to contain all live nodes. In standalone mode the whitelist is empty by default. Upgrading users who use the <code>shards</code> parameter in standalone mode can correct this value by setting the <code>shardsWhitelist</code> property in any <code>shardHandler</code> configurations in their <code>solrconfig.xml</code> file.</p>
+<p>For more information, see the <a href="distributed-requests.html#configuring-the-shardhandlerfactory">Distributed Request</a> documentation.</p></p></li></ul></div></section>
<section class="sect2"><h3 id="solr-7-6">Solr 7.6</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote76">7.6 Release Notes</a> for an overview of the main new features in Solr 7.6.</p>
<p>When upgrading to Solr 7.6, users should be aware of the following major changes from v7.5:</p>
<p><strong>Collections</strong></p>
-<div class="ulist"><ul><li><p>The JSON parameter to set cluster-wide default cluster properties with the <a href="cluster-node-management.html#clusterprop">CLUSTERPROP</a> command has changed.</p><p>The old syntax nested the defaults into a property named <code>clusterDefaults</code>. The new syntax uses only <code>defaults</code>. The command to use is still <code>set-obj-property</code>.</p>
+<div class="ulist"><ul><li><p><p>The JSON parameter to set cluster-wide default cluster properties with the <a href="cluster-node-management.html#clusterprop">CLUSTERPROP</a> command has changed.</p><p>The old syntax nested the defaults into a property named <code>clusterDefaults</code>. The new syntax uses only <code>defaults</code>. The command to use is still <code>set-obj-property</code>.</p>
<p>An example of the new syntax is:</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">
</span><span style="color: #000080">"set-obj-property"</span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb">
@@ -1815,73 +1810,73 @@ On clusters configured to use <a href="k
</span><span style="background-color: #f8f8f8">}</span><span style="color: #bbbbbb">
</span><span style="background-color: #f8f8f8">}</span><span style="color: #bbbbbb">
</span><span style="background-color: #f8f8f8">}</span></code></pre></code></pre></div>
-<p>The old syntax will be supported until at least Solr 9, but users are advised to begin using the new syntax as soon as possible.</p></li><li>The parameter <code>min_rf</code> has been deprecated and no longer needs to be provided in order to see the achieved replication factor. This information will now always be returned to the client with the response.</li></ul></div>
+<p>The old syntax will be supported until at least Solr 9, but users are advised to begin using the new syntax as soon as possible.</p></p></li><li><p>The parameter <code>min_rf</code> has been deprecated and no longer needs to be provided in order to see the achieved replication factor. This information will now always be returned to the client with the response.</p></li></ul></div>
<p><strong>Autoscaling</strong></p>
-<div class="ulist"><ul><li><p>An autoscaling policy is now used as the default strategy for selecting nodes on which new replicas or replicas of new collections are created.</p><p>A default policy is now in place for all users, which will sort nodes by the number of cores and available freedisk, which means by default a node with the fewest number of cores already on it and the highest available freedisk will be selected for new core creation.</p></li><li>The change described above has two additional impacts on the <code>maxShardsPerNode</code> parameter:<ol class="arabic"><li>It removes the restriction against using <code>maxShardsPerNode</code> when an autoscaling policy is in place. This parameter can now always be set when creating a collection.</li><li><p>It removes the default setting of <code>maxShardsPerNode=1</code> when an autoscaling policy is in place. It will be set correctly (if required) regardless of whether an autoscaling policy is in place or not.</p><p>The default
value of <code>maxShardsPerNode</code> is still <code>1</code>. It can be set to <code>-1</code> if the old behavior of unlimited <code>maxShardsPerNode</code> is desired.</p></li></ol></li></ul></div>
+<div class="ulist"><ul><li><p><p>An autoscaling policy is now used as the default strategy for selecting nodes on which new replicas or replicas of new collections are created.</p><p>A default policy is now in place for all users, which will sort nodes by the number of cores and available freedisk, which means by default a node with the fewest number of cores already on it and the highest available freedisk will be selected for new core creation.</p></p></li><li><p>The change described above has two additional impacts on the <code>maxShardsPerNode</code> parameter:<ol class="arabic"><li>It removes the restriction against using <code>maxShardsPerNode</code> when an autoscaling policy is in place. This parameter can now always be set when creating a collection.</li><li><p>It removes the default setting of <code>maxShardsPerNode=1</code> when an autoscaling policy is in place. It will be set correctly (if required) regardless of whether an autoscaling policy is in place or not.</p><p>T
he default value of <code>maxShardsPerNode</code> is still <code>1</code>. It can be set to <code>-1</code> if the old behavior of unlimited <code>maxShardsPerNode</code> is desired.</p></li></ol></p></li></ul></div>
<p><strong>DirectoryFactory</strong></p>
-<div class="ulist"><ul><li><p>Lucene has introduced the <code>ByteBuffersDirectoryFactory</code> as a replacement for the <code>RAMDirectoryFactory</code>, which will be removed in Solr 9.</p><p>While most users are still encouraged to use the <code>NRTCachingDirectoryFactory</code>, which allows Lucene to select the best directory factory to use, if you have explicitly configured Solr to use the <code>RAMDirectoryFactory</code>, you are encouraged to switch to the new implementation as soon as possible before Solr 9 is released.</p>
+<div class="ulist"><ul><li><p><p>Lucene has introduced the <code>ByteBuffersDirectoryFactory</code> as a replacement for the <code>RAMDirectoryFactory</code>, which will be removed in Solr 9.</p><p>While most users are still encouraged to use the <code>NRTCachingDirectoryFactory</code>, which allows Lucene to select the best directory factory to use, if you have explicitly configured Solr to use the <code>RAMDirectoryFactory</code>, you are encouraged to switch to the new implementation as soon as possible before Solr 9 is released.</p>
<p>For more information about the new directory factory, see the Jira issue <a href="https://issues.apache.org/jira/browse/LUCENE-8438">LUCENE-8438</a>.</p>
-<p>For more information about the directory factory configuration in Solr, see the section <a href="datadir-and-directoryfactory-in-solrconfig.html#datadir-and-directoryfactory-in-solrconfig">DataDir and DirectoryFactory in SolrConfig</a>.</p></li></ul></div></section>
+<p>For more information about the directory factory configuration in Solr, see the section <a href="datadir-and-directoryfactory-in-solrconfig.html#datadir-and-directoryfactory-in-solrconfig">DataDir and DirectoryFactory in SolrConfig</a>.</p></p></li></ul></div></section>
<section class="sect2"><h3 id="solr-7-5">Solr 7.5</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote75">7.5 Release Notes</a> for an overview of the main new features in Solr 7.5.</p>
<p>When upgrading to Solr 7.5, users should be aware of the following major changes from v7.4:</p>
<p><strong>Schema Changes</strong></p>
-<div class="ulist"><ul><li>Since Solr 7.0, Solr’s schema field-guessing has created <code>_str</code> fields for all <code>_txt</code> fields, and returned those by default with queries. As of 7.5, <code>_str</code> fields will no longer be returned by default. They will still be available and can be requested with the <code>fl</code> parameter on queries. See also the section on <a href="schemaless-mode.html#enable-field-class-guessing">field guessing</a> for more information about how schema field guessing works.</li><li>The Standard Filter, which has been non-operational since at least Solr v4, has been removed.</li></ul></div>
+<div class="ulist"><ul><li><p>Since Solr 7.0, Solr’s schema field-guessing has created <code>_str</code> fields for all <code>_txt</code> fields, and returned those by default with queries. As of 7.5, <code>_str</code> fields will no longer be returned by default. They will still be available and can be requested with the <code>fl</code> parameter on queries. See also the section on <a href="schemaless-mode.html#enable-field-class-guessing">field guessing</a> for more information about how schema field guessing works.</p></li><li><p>The Standard Filter, which has been non-operational since at least Solr v4, has been removed.</p></li></ul></div>
<p><strong>Index Merge Policy</strong></p>
-<div class="ulist"><ul><li><p>When using the <a href="indexconfig-in-solrconfig.html#mergepolicyfactory"><code>TieredMergePolicy</code></a>, the default merge policy for Solr, <code>optimize</code> and <code>expungeDeletes</code> now respect the <code>maxMergedSegmentMB</code> configuration parameter, which defaults to <code>5000</code> (5GB).</p><p>If it is absolutely necessary to control the number of segments present after optimize, specify <code>maxSegments</code> as a positive integer. Setting <code>maxSegments</code> higher than <code>1</code> are honored on a "best effort" basis.</p>
-<p>The <code>TieredMergePolicy</code> will also reclaim resources from segments that exceed <code>maxMergedSegmentMB</code> more aggressively than earlier.</p></li></ul></div>
+<div class="ulist"><ul><li><p><p>When using the <a href="indexconfig-in-solrconfig.html#mergepolicyfactory"><code>TieredMergePolicy</code></a>, the default merge policy for Solr, <code>optimize</code> and <code>expungeDeletes</code> now respect the <code>maxMergedSegmentMB</code> configuration parameter, which defaults to <code>5000</code> (5GB).</p><p>If it is absolutely necessary to control the number of segments present after optimize, specify <code>maxSegments</code> as a positive integer. Setting <code>maxSegments</code> higher than <code>1</code> are honored on a "best effort" basis.</p>
+<p>The <code>TieredMergePolicy</code> will also reclaim resources from segments that exceed <code>maxMergedSegmentMB</code> more aggressively than earlier.</p></p></li></ul></div>
<p><strong>UIMA Removed</strong></p>
-<div class="ulist"><ul><li>The UIMA contrib has been removed from Solr and is no longer available.</li></ul></div>
+<div class="ulist"><ul><li><p>The UIMA contrib has been removed from Solr and is no longer available.</p></li></ul></div>
<p><strong>Logging</strong></p>
-<div class="ulist"><ul><li>Solr’s logging configuration file is now located in <code>server/resources/log4j2.xml</code> by default.</li><li>A bug for Windows users has been corrected. When using Solr’s examples (<code>bin/solr start -e</code>) log files will now be put in the correct location (<code>example/</code> instead of <code>server</code>). See also <a href="installing-solr.html#solr-examples">Solr Examples</a> and <a href="solr-control-script-reference.html#solr-control-script-reference">Solr Control Script Reference</a> for more information.</li></ul></div></section>
+<div class="ulist"><ul><li><p>Solr’s logging configuration file is now located in <code>server/resources/log4j2.xml</code> by default.</p></li><li><p>A bug for Windows users has been corrected. When using Solr’s examples (<code>bin/solr start -e</code>) log files will now be put in the correct location (<code>example/</code> instead of <code>server</code>). See also <a href="installing-solr.html#solr-examples">Solr Examples</a> and <a href="solr-control-script-reference.html#solr-control-script-reference">Solr Control Script Reference</a> for more information.</p></li></ul></div></section>
<section class="sect2"><h3 id="solr-7-4">Solr 7.4</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote74">7.4 Release Notes</a> for an overview of the main new features in Solr 7.4.</p>
<p>When upgrading to Solr 7.4, users should be aware of the following major changes from v7.3:</p>
<p><strong>Logging</strong></p>
-<div class="ulist"><ul><li>Solr now uses Log4j v2.11. The Log4j configuration is now in <code>log4j2.xml</code> rather than <code>log4j.properties</code> files. This is a server side change only and clients using SolrJ won’t need any changes. Clients can still use any logging implementation which is compatible with SLF4J. We now let Log4j handle rotation of Solr logs at startup, and <code>bin/solr</code> start scripts will no longer attempt this nor move existing console or garbage collection logs into <code>logs/archived</code> either. See <a href="configuring-logging.html#configuring-logging">Configuring Logging</a> for more details about Solr logging.</li><li>Configuring <code>slowQueryThresholdMillis</code> now logs slow requests to a separate file named <code>solr_slow_requests.log</code>. Previously they would get logged in the <code>solr.log</code> file.</li></ul></div>
+<div class="ulist"><ul><li><p>Solr now uses Log4j v2.11. The Log4j configuration is now in <code>log4j2.xml</code> rather than <code>log4j.properties</code> files. This is a server side change only and clients using SolrJ won’t need any changes. Clients can still use any logging implementation which is compatible with SLF4J. We now let Log4j handle rotation of Solr logs at startup, and <code>bin/solr</code> start scripts will no longer attempt this nor move existing console or garbage collection logs into <code>logs/archived</code> either. See <a href="configuring-logging.html#configuring-logging">Configuring Logging</a> for more details about Solr logging.</p></li><li><p>Configuring <code>slowQueryThresholdMillis</code> now logs slow requests to a separate file named <code>solr_slow_requests.log</code>. Previously they would get logged in the <code>solr.log</code> file.</p></li></ul></div>
<p><strong>Legacy Scaling (non-SolrCloud)</strong></p>
-<div class="ulist"><ul><li>In the <a href="index-replication.html#index-replication">master-slave model</a> of scaling Solr, a slave no longer commits an empty index when a completely new index is detected on master during replication. To return to the previous behavior pass <code>false</code> to <code>skipCommitOnMasterVersionZero</code> in the slave section of replication handler configuration, or pass it to the <code>fetchindex</code> command.</li></ul></div>
+<div class="ulist"><ul><li><p>In the <a href="index-replication.html#index-replication">master-slave model</a> of scaling Solr, a slave no longer commits an empty index when a completely new index is detected on master during replication. To return to the previous behavior pass <code>false</code> to <code>skipCommitOnMasterVersionZero</code> in the slave section of replication handler configuration, or pass it to the <code>fetchindex</code> command.</p></li></ul></div>
<p>If you are upgrading from a version earlier than Solr 7.3, please see previous version notes below.</p></section>
<section class="sect2"><h3 id="solr-7-3">Solr 7.3</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote73">7.3 Release Notes</a> for an overview of the main new features in Solr 7.3.</p>
<p>When upgrading to Solr 7.3, users should be aware of the following major changes from v7.2:</p>
<p><strong>Configsets</strong></p>
-<div class="ulist"><ul><li>Collections created without specifying a configset name have used a copy of the <code>_default</code> configset since Solr 7.0. Before 7.3, the copied configset was named the same as the collection name, but from 7.3 onwards it will be named with a new ".AUTOCREATED" suffix. This is to prevent overwriting custom configset names.</li></ul></div>
+<div class="ulist"><ul><li><p>Collections created without specifying a configset name have used a copy of the <code>_default</code> configset since Solr 7.0. Before 7.3, the copied configset was named the same as the collection name, but from 7.3 onwards it will be named with a new ".AUTOCREATED" suffix. This is to prevent overwriting custom configset names.</p></li></ul></div>
<p><strong>Learning to Rank</strong></p>
-<div class="ulist"><ul><li>The <code>rq</code> parameter used with Learning to Rank <code>rerank</code> query parsing no longer considers the <code>defType</code> parameter. See <a href="learning-to-rank.html#running-a-rerank-query">Running a Rerank Query</a> for more information about this parameter.</li></ul></div>
+<div class="ulist"><ul><li><p>The <code>rq</code> parameter used with Learning to Rank <code>rerank</code> query parsing no longer considers the <code>defType</code> parameter. See <a href="learning-to-rank.html#running-a-rerank-query">Running a Rerank Query</a> for more information about this parameter.</p></li></ul></div>
<p><strong>Autoscaling & AutoAddReplicas</strong></p>
-<div class="ulist"><ul><li>The behaviour of the autoscaling system will now pause all triggers from execution between the start of actions and the end of a cool down period. The triggers will resume after the cool down period expires. Previously, the cool down period was a fixed period started after actions for a trigger event completed and during this time all triggers continued to run but any events were rejected and tried later.</li><li>The throttling mechanism used to limit the rate of autoscaling events processed has been removed. This deprecates the <code>actionThrottlePeriodSeconds</code> setting in the <a href="solrcloud-autoscaling-api.html#change-autoscaling-properties"><code>set-properties</code> Autoscaling API</a> which is now non-operational. Use the <code>triggerCooldownPeriodSeconds</code> parameter instead to pause event processing.</li><li>The default value of <code>autoReplicaFailoverWaitAfterExpiration</code>, used with the AutoAddReplicas feature, has increased
to 120 seconds from the previous default of 30 seconds. This affects how soon Solr adds new replicas to replace the replicas on nodes which have either crashed or shutdown.</li></ul></div>
+<div class="ulist"><ul><li><p>The behaviour of the autoscaling system will now pause all triggers from execution between the start of actions and the end of a cool down period. The triggers will resume after the cool down period expires. Previously, the cool down period was a fixed period started after actions for a trigger event completed and during this time all triggers continued to run but any events were rejected and tried later.</p></li><li><p>The throttling mechanism used to limit the rate of autoscaling events processed has been removed. This deprecates the <code>actionThrottlePeriodSeconds</code> setting in the <a href="solrcloud-autoscaling-api.html#change-autoscaling-properties"><code>set-properties</code> Autoscaling API</a> which is now non-operational. Use the <code>triggerCooldownPeriodSeconds</code> parameter instead to pause event processing.</p></li><li><p>The default value of <code>autoReplicaFailoverWaitAfterExpiration</code>, used with the AutoAddReplicas featur
e, has increased to 120 seconds from the previous default of 30 seconds. This affects how soon Solr adds new replicas to replace the replicas on nodes which have either crashed or shutdown.</p></li></ul></div>
<p><strong>Logging</strong></p>
-<div class="ulist"><ul><li>The default Solr log file size and number of backups have been raised to 32MB and 10 respectively. See the section <a href="configuring-logging.html#configuring-logging">Configuring Logging</a> for more information about how to configure logging.</li></ul></div>
+<div class="ulist"><ul><li><p>The default Solr log file size and number of backups have been raised to 32MB and 10 respectively. See the section <a href="configuring-logging.html#configuring-logging">Configuring Logging</a> for more information about how to configure logging.</p></li></ul></div>
<p><strong>SolrCloud</strong></p>
-<div class="ulist"><ul><li><p>The old Leader-In-Recovery implementation (implemented in Solr 4.9) is now deprecated and replaced. Solr will support rolling upgrades from old 7.x versions of Solr to future 7.x releases until the last release of the 7.x major version.</p><p>This means to upgrade to Solr 8 in the future, you will need to be on Solr 7.3 or higher.</p></li><li>Replicas which are not up-to-date are no longer allowed to become leader. Use the <a href="shard-management.html#forceleader">FORCELEADER command</a> of the Collections API to allow these replicas become leader.</li></ul></div>
+<div class="ulist"><ul><li><p><p>The old Leader-In-Recovery implementation (implemented in Solr 4.9) is now deprecated and replaced. Solr will support rolling upgrades from old 7.x versions of Solr to future 7.x releases until the last release of the 7.x major version.</p><p>This means to upgrade to Solr 8 in the future, you will need to be on Solr 7.3 or higher.</p></p></li><li><p>Replicas which are not up-to-date are no longer allowed to become leader. Use the <a href="shard-management.html#forceleader">FORCELEADER command</a> of the Collections API to allow these replicas become leader.</p></li></ul></div>
<p><strong>Spatial</strong></p>
-<div class="ulist"><ul><li>If you are using the spatial JTS library with Solr, you must upgrade to 1.15.0. This new version of JTS is now dual-licensed to include a BSD style license. See the section on <a href="spatial-search.html#spatial-search">Spatial Search</a> for more information.</li></ul></div>
+<div class="ulist"><ul><li><p>If you are using the spatial JTS library with Solr, you must upgrade to 1.15.0. This new version of JTS is now dual-licensed to include a BSD style license. See the section on <a href="spatial-search.html#spatial-search">Spatial Search</a> for more information.</p></li></ul></div>
<p><strong>Highlighting</strong></p>
-<div class="ulist"><ul><li>The top-level <code><highlighting></code> element in <code>solrconfig.xml</code> is now officially deprecated in favour of the equivalent <code><searchComponent></code> syntax. This element has been out of use in default Solr installations for several releases already.</li></ul></div>
+<div class="ulist"><ul><li><p>The top-level <code><highlighting></code> element in <code>solrconfig.xml</code> is now officially deprecated in favour of the equivalent <code><searchComponent></code> syntax. This element has been out of use in default Solr installations for several releases already.</p></li></ul></div>
<p>If you are upgrading from a version earlier than Solr 7.2, please see previous version notes below.</p></section>
<section class="sect2"><h3 id="solr-7-2">Solr 7.2</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote72">7.2 Release Notes</a> for an overview of the main new features in Solr 7.2.</p>
<p>When upgrading to Solr 7.2, users should be aware of the following major changes from v7.1:</p>
<p><strong>Local Parameters</strong></p>
-<div class="ulist"><ul><li><p>Starting a query string with <a href="local-parameters-in-queries.html#local-parameters-in-queries">local parameters</a> <code>{!myparser …​}</code> is used to switch from one query parser to another, and is intended for use by Solr system developers, not end users doing searches. To reduce negative side-effects of unintended hack-ability, Solr now limits the cases when local parameters will be parsed to only contexts in which the default parser is "<a href="other-parsers.html#lucene-query-parser">lucene</a>" or "<a href="other-parsers.html#function-query-parser">func</a>".</p><p>So, if <code>defType=edismax</code> then <code>q={!myparser …​}</code> won’t work. In that example, put the desired query parser into the <code>defType</code> parameter.</p>
+<div class="ulist"><ul><li><p><p>Starting a query string with <a href="local-parameters-in-queries.html#local-parameters-in-queries">local parameters</a> <code>{!myparser …​}</code> is used to switch from one query parser to another, and is intended for use by Solr system developers, not end users doing searches. To reduce negative side-effects of unintended hack-ability, Solr now limits the cases when local parameters will be parsed to only contexts in which the default parser is "<a href="other-parsers.html#lucene-query-parser">lucene</a>" or "<a href="other-parsers.html#function-query-parser">func</a>".</p><p>So, if <code>defType=edismax</code> then <code>q={!myparser …​}</code> won’t work. In that example, put the desired query parser into the <code>defType</code> parameter.</p>
<p>Another example is if <code>deftype=edismax</code> then <code>hl.q={!myparser …​}</code> won’t work for the same reason. In this example, either put the desired query parser into the <code>hl.qparser</code> parameter or set <code>hl.qparser=lucene</code>. Most users won’t run into these cases but some will need to change.</p>
-<p>If you must have full backwards compatibility, use <code>luceneMatchVersion=7.1.0</code> or an earlier version.</p></li></ul></div>
+<p>If you must have full backwards compatibility, use <code>luceneMatchVersion=7.1.0</code> or an earlier version.</p></p></li></ul></div>
<p><strong>eDisMax Query Parser</strong></p>
-<div class="ulist"><ul><li><p>The eDisMax parser by default no longer allows subqueries that specify a Solr parser using either local parameters, or the older <code>_query_</code> magic field trick.</p><p>For example, <code>{!prefix f=myfield v=enterp}</code> or <code>_query_:"{!prefix f=myfield v=enterp}"</code> are not supported by default any longer. If you want to allow power-users to do this, set <code>uf=* <em>query</em></code> or some other value that includes <code>_query_</code>.</p>
-<p>If you need full backwards compatibility for the time being, use <code>luceneMatchVersion=7.1.0</code> or something earlier.</p></li></ul></div>
+<div class="ulist"><ul><li><p><p>The eDisMax parser by default no longer allows subqueries that specify a Solr parser using either local parameters, or the older <code>_query_</code> magic field trick.</p><p>For example, <code>{!prefix f=myfield v=enterp}</code> or <code>_query_:"{!prefix f=myfield v=enterp}"</code> are not supported by default any longer. If you want to allow power-users to do this, set <code>uf=* <em>query</em></code> or some other value that includes <code>_query_</code>.</p>
+<p>If you need full backwards compatibility for the time being, use <code>luceneMatchVersion=7.1.0</code> or something earlier.</p></p></li></ul></div>
<p>If you are upgrading from a version earlier than Solr 7.1, please see previous version notes below.</p></section>
<section class="sect2"><h3 id="solr-7-1">Solr 7.1</h3><p>See the <a href="https://cwiki.apache.org/confluence/display/solr/ReleaseNote71">7.1 Release Notes</a> for an overview of the main new features of Solr 7.1.</p>
<p>When upgrading to Solr 7.1, users should be aware of the following major changes from v7.0:</p>
<p><strong>AutoAddReplicas</strong></p>
-<div class="ulist"><ul><li><p>The feature to automatically add replicas if a replica goes down, previously available only when storing indexes in HDFS, has been ported to the autoscaling framework. Due to this, <code>autoAddReplicas</code> is now available to all users even if their indexes are on local disks.</p><p>Existing users of this feature should not have to change anything. However, they should note these changes:</p>
-<ul><li>Behavior: Changing the <code>autoAddReplicas</code> property from disabled (<code>false</code>) to enabled (<code>true</code>) using <a href="collection-management.html#modifycollection">MODIFYCOLLECTION API</a> no longer replaces down replicas for the collection immediately. Instead, replicas are only added if a node containing them went down while <code>autoAddReplicas</code> was enabled. The parameters <code>autoReplicaFailoverBadNodeExpiration</code> and <code>autoReplicaFailoverWorkLoopDelay</code> are no longer used.</li><li><p>Deprecations: Enabling/disabling autoAddReplicas cluster-wide with the API will be deprecated; use suspend/resume trigger APIs with <code>name=".auto_add_replicas"</code> instead.</p><p>More information about the changes to this feature can be found in the section <a href="solrcloud-autoscaling-auto-add-replicas.html#solrcloud-autoscaling-auto-add-replicas">SolrCloud Automatically Adding Replicas</a>.</p></li></ul></li></ul></div>
+<div class="ulist"><ul><li><p><p>The feature to automatically add replicas if a replica goes down, previously available only when storing indexes in HDFS, has been ported to the autoscaling framework. Due to this, <code>autoAddReplicas</code> is now available to all users even if their indexes are on local disks.</p><p>Existing users of this feature should not have to change anything. However, they should note these changes:</p>
+<ul><li><p>Behavior: Changing the <code>autoAddReplicas</code> property from disabled (<code>false</code>) to enabled (<code>true</code>) using <a href="collection-management.html#modifycollection">MODIFYCOLLECTION API</a> no longer replaces down replicas for the collection immediately. Instead, replicas are only added if a node containing them went down while <code>autoAddReplicas</code> was enabled. The parameters <code>autoReplicaFailoverBadNodeExpiration</code> and <code>autoReplicaFailoverWorkLoopDelay</code> are no longer used.</p></li><li><p><p>Deprecations: Enabling/disabling autoAddReplicas cluster-wide with the API will be deprecated; use suspend/resume trigger APIs with <code>name=".auto_add_replicas"</code> instead.</p><p>More information about the changes to this feature can be found in the section <a href="solrcloud-autoscaling-auto-add-replicas.html#solrcloud-autoscaling-auto-add-replicas">SolrCloud Automatically Adding Replicas</a>.</p></p></li></ul></p></li></ul></d
iv>
<p><strong>Metrics Reporters</strong></p>
-<div class="ulist"><ul><li>Shard and cluster metric reporter configuration now require a <code>class</code> attribute.<ul><li>If a reporter configures the <code>group="shard"</code> attribute then please also configure the <code>class="org.apache.solr.metrics.reporters.solr.SolrShardReporter"</code> attribute.</li><li><p>If a reporter configures the <code>group="cluster"</code> attribute then please also configure the <code>class="org.apache.solr.metrics.reporters.solr.SolrClusterReporter"</code> attribute.</p><p>See the section <a href="metrics-reporting.html#shard-and-cluster-reporters">Shard and Cluster Reporters</a> for more information.</p></li></ul></li></ul></div>
+<div class="ulist"><ul><li><p>Shard and cluster metric reporter configuration now require a <code>class</code> attribute.<ul><li><p>If a reporter configures the <code>group="shard"</code> attribute then please also configure the <code>class="org.apache.solr.metrics.reporters.solr.SolrShardReporter"</code> attribute.</p></li><li><p><p>If a reporter configures the <code>group="cluster"</code> attribute then please also configure the <code>class="org.apache.solr.metrics.reporters.solr.SolrClusterReporter"</code> attribute.</p><p>See the section <a href="metrics-reporting.html#shard-and-cluster-reporters">Shard and Cluster Reporters</a> for more information.</p></p></li></ul></p></li></ul></div>
<p><strong>Streaming Expressions</strong></p>
-<div class="ulist"><ul><li>All Stream Evaluators in <code>solrj.io.eval</code> have been refactored to have a simpler and more robust structure. This simplifies and condenses the code required to implement a new Evaluator and makes it much easier for evaluators to handle differing data types (primitives, objects, arrays, lists, and so forth).</li></ul></div>
+<div class="ulist"><ul><li><p>All Stream Evaluators in <code>solrj.io.eval</code> have been refactored to have a simpler and more robust structure. This simplifies and condenses the code required to implement a new Evaluator and makes it much easier for evaluators to handle differing data types (primitives, objects, arrays, lists, and so forth).</p></li></ul></div>
<p><strong>ReplicationHandler</strong></p>
-<div class="ulist"><ul><li>In the ReplicationHandler, the <code>master.commitReserveDuration</code> sub-element is deprecated. Instead please configure a direct <code>commitReserveDuration</code> element for use in all modes (master, slave, cloud).</li></ul></div>
+<div class="ulist"><ul><li><p>In the ReplicationHandler, the <code>master.commitReserveDuration</code> sub-element is deprecated. Instead please configure a direct <code>commitReserveDuration</code> element for use in all modes (master, slave, cloud).</p></li></ul></div>
<p><strong>RunExecutableListener</strong></p>
-<div class="ulist"><ul><li>The <code>RunExecutableListener</code> was removed for security reasons. If you want to listen to events caused by updates, commits, or optimize, write your own listener as native Java class as part of a Solr plugin.</li></ul></div>
+<div class="ulist"><ul><li><p>The <code>RunExecutableListener</code> was removed for security reasons. If you want to listen to events caused by updates, commits, or optimize, write your own listener as native Java class as part of a Solr plugin.</p></li></ul></div>
<p><strong>XML Query Parser</strong></p>
-<div class="ulist"><ul><li>In the XML query parser (<code>defType=xmlparser</code> or <code>{!xmlparser …​ }</code>) the resolving of external entities is now disallowed by default.</li></ul></div>
+<div class="ulist"><ul><li><p>In the XML query parser (<code>defType=xmlparser</code> or <code>{!xmlparser …​ }</code>) the resolving of external entities is now disallowed by default.</p></li></ul></div>
<p>If you are upgrading from a version earlier than Solr 7.0, please see <a href="major-changes-in-solr-7.html#major-changes-in-solr-7">Major Changes in Solr 7</a> before starting your upgrade.</p></section></section>
</section>
@@ -1912,7 +1907,7 @@ On clusters configured to use <a href="k
<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/making-and-restoring-backups.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/making-and-restoring-backups.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/making-and-restoring-backups.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Making and Restoring Backups | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Making and Restoring Backups | 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="making-and-restoring-backups">
+<body class="" id="making-and-restoring-backups">
<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-->
@@ -1685,7 +1680,7 @@
</tr>
</table>
</div></section>
-<section class="sect1"><h2 id="solrcloud-backups">SolrCloud Backups</h2><p>Support for backups when running SolrCloud is provided with the <a href="collections-api.html#collections-api">Collections API</a>. This allows the backups to be generated across multiple shards, and restored to the same number of shards and replicas as the original collection.</p>
+<section class="sect1"><h2 id="solrcloud-backups">SolrCloud Backups</h2><p>Support for backups when running SolrCloud is provided with the <a href="collection-management.html#collection-management">Collections API</a>. This allows the backups to be generated across multiple shards, and restored to the same number of shards and replicas as the original collection.</p>
<div class="admonitionblock note">
<table>
<tr>
@@ -1699,7 +1694,7 @@ SolrCloud Backup/Restore requires a shar
</table>
</div>
<p>Two commands are available:</p>
-<div class="ulist"><ul><li><code>action=BACKUP</code>: This command backs up Solr indexes and configurations. More information is available in the section <a href="collection-management.html#backup">Backup Collection</a>.</li><li><code>action=RESTORE</code>: This command restores Solr indexes and configurations. More information is available in the section <a href="collection-management.html#restore">Restore Collection</a>.</li></ul></div></section>
+<div class="ulist"><ul><li><p><code>action=BACKUP</code>: This command backs up Solr indexes and configurations. More information is available in the section <a href="collection-management.html#backup">Backup Collection</a>.</p></li><li><p><code>action=RESTORE</code>: This command restores Solr indexes and configurations. More information is available in the section <a href="collection-management.html#restore">Restore Collection</a>.</p></li></ul></div></section>
<section class="sect1"><h2 id="standalone-mode-backups">Standalone Mode Backups</h2><p>Backups and restoration uses Solr’s replication handler. Out of the box, Solr includes implicit support for replication so this API can be used. Configuration of the replication handler can, however, be customized by defining your own replication handler in <code>solrconfig.xml</code>. For details on configuring the replication handler, see the section <a href="index-replication.html#configuring-the-replicationhandler">Configuring the ReplicationHandler</a>.</p>
<section class="sect2"><h3 id="backup-api">Backup API</h3><p>The <code>backup</code> API requires sending a command to the <code>/replication</code> handler to back up the system.</p>
<p>You can trigger a back-up with an HTTP command like this (replace "gettingstarted" with the name of the core you are working with):</p>
@@ -1805,7 +1800,7 @@ SolrCloud Backup/Restore requires a shar
<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/managed-resources.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/managed-resources.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/managed-resources.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Managed Resources | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Managed Resources | 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="managed-resources">
+<body class="" id="managed-resources">
<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-->
@@ -1854,7 +1849,7 @@ PUT/POST is used to add terms to an exis
<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/math-expressions.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/math-expressions.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/math-expressions.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Math Expressions | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Math Expressions | 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="math-expressions">
+<body class="" id="math-expressions">
<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-->
@@ -1711,7 +1706,7 @@ record in your Solr Cloud cluster comput
<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/matrix-math.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/matrix-math.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/matrix-math.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Matrices and Matrix Math | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Matrices and Matrix Math | 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="matrix-math">
+<body class="" id="matrix-math">
<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-->
@@ -2030,7 +2025,7 @@ responds with:</p>
<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/mbean-request-handler.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/mbean-request-handler.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/mbean-request-handler.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>MBean Request Handler | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>MBean Request Handler | 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="mbean-request-handler">
+<body class="" id="mbean-request-handler">
<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-->
@@ -1700,7 +1695,7 @@
<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/merging-indexes.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/merging-indexes.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/merging-indexes.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Merging Indexes | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Merging Indexes | 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="merging-indexes">
+<body class="" id="merging-indexes">
<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-->
@@ -1661,7 +1656,7 @@
<section class="content">
<section id="preamble" aria-label="Preamble"><p>If you need to combine indexes from two different projects or from multiple servers previously used in a distributed configuration, you can use either the IndexMergeTool included in <code>lucene-misc</code> or the <code>CoreAdminHandler</code>.</p>
<p>To merge indexes, they must meet these requirements:</p>
-<div class="ulist"><ul><li>The two indexes must be compatible: their schemas should include the same fields and they should analyze fields the same way.</li><li>The indexes must not include duplicate data.</li></ul></div>
+<div class="ulist"><ul><li><p>The two indexes must be compatible: their schemas should include the same fields and they should analyze fields the same way.</p></li><li><p>The indexes must not include duplicate data.</p></li></ul></div>
<p>Optimally, the two indexes should be built using the same schema.</p></section>
<section class="sect1"><h2 id="using-indexmergetool">Using IndexMergeTool</h2><p>To merge the indexes, do the following:</p>
<div class="olist arabic"><ol class="arabic"><li>Make sure that both indexes you want to merge are closed.</li><li><p>Issue this command:</p><div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code>java -cp <span style="color: #008080">$SOLR</span>/server/solr-webapp/webapp/WEB-INF/lib/lucene-core-VERSION.jar:<span style="color: #008080">$SOLR</span>/server/solr-webapp/webapp/WEB-INF/lib/lucene-misc-VERSION.jar org/apache/lucene/misc/IndexMergeTool /path/to/newindex /path/to/old/index1 /path/to/old/index2</code></pre></code></pre></div>
@@ -1697,7 +1692,7 @@
<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>