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 [7/28] - in /websites/production/lucene/content/solr/guide/8_6: ./ meta-docs/

Modified: websites/production/lucene/content/solr/guide/8_6/faceting.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/faceting.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/faceting.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Faceting | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Faceting | 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="faceting">
+<body class="" id="faceting">
 <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-->
@@ -1720,7 +1715,7 @@ If you do not set this parameter to at l
 <p><code>f.lastModified_dt.facet.range.start=NOW/DAY-30DAYS</code></p></dd><dt><code>facet.range.end</code></dt><dd><p>The <code>facet.range.end</code> specifies the upper bound of the ranges. You can specify this parameter on a per field basis with the syntax of <code>f.&lt;fieldname&gt;.facet.range.end</code>. For example:</p><p><code>f.price.facet.range.end=1000.0&amp;f.age.facet.range.start=99</code></p>
 <p><code>f.lastModified_dt.facet.range.end=NOW/DAY+30DAYS</code></p></dd><dt><code>facet.range.gap</code></dt><dd><p>The span of each range expressed as a value to be added to the lower bound. For date fields, this should be expressed using the <a href="https://lucene.apache.org/solr/8_6_0//solr-core/org/apache/solr/util/DateMathParser.html"><code>DateMathParser</code> syntax</a> (such as, <code>facet.range.gap=%2B1DAY &#8230;&#8203; '+1DAY'</code>). You can specify this parameter on a per-field basis with the syntax of <code>f.&lt;fieldname&gt;.facet.range.gap</code>. For example:</p><p><code>f.price.facet.range.gap=100&amp;f.age.facet.range.gap=10</code></p>
 <p><code>f.lastModified_dt.facet.range.gap=+1DAY</code></p></dd><dt><code>facet.range.hardend</code></dt><dd><p>The <code>facet.range.hardend</code> parameter is a Boolean parameter that specifies how Solr should handle cases where the <code>facet.range.gap</code> does not divide evenly between <code>facet.range.start</code> and <code>facet.range.end</code>.</p><p>If <code>true</code>, the last range constraint will have the <code>facet.range.end</code> value as an upper bound. If <code>false</code>, the last range will have the smallest possible upper bound greater then <code>facet.range.end</code> such that the range is the exact width of the specified range gap. The default value for this parameter is false.</p>
-<p>This parameter can be specified on a per field basis with the syntax <code>f.&lt;fieldname&gt;.facet.range.hardend</code>.</p></dd><dt><code>facet.range.include</code></dt><dd><p>By default, the ranges used to compute range faceting between <code>facet.range.start</code> and <code>facet.range.end</code> are inclusive of their lower bounds and exclusive of the upper bounds. The "before" range defined with the <code>facet.range.other</code> parameter is exclusive and the "after" range is inclusive. This default, equivalent to "lower" below, will not result in double counting at the boundaries. You can use the <code>facet.range.include</code> parameter to modify this behavior using the following options:</p><div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li><code>lower</code>: All gap-based ranges include their lower bound.</li><li><code>upper</code>: All gap-based ranges include their upper bound.</li><li><code>edge</code>: The first and last gap
  ranges include their edge bounds (lower for the first one, upper for the last one) even if the corresponding upper/lower option is not specified.</li><li><code>outer</code>: The "before" and "after" ranges will be inclusive of their bounds, even if the first or last ranges already include those boundaries.</li><li><code>all</code>: Includes all options: <code>lower</code>, <code>upper</code>, <code>edge</code>, and <code>outer</code>.</li></ul></div></div></div>
+<p>This parameter can be specified on a per field basis with the syntax <code>f.&lt;fieldname&gt;.facet.range.hardend</code>.</p></dd><dt><code>facet.range.include</code></dt><dd><p>By default, the ranges used to compute range faceting between <code>facet.range.start</code> and <code>facet.range.end</code> are inclusive of their lower bounds and exclusive of the upper bounds. The "before" range defined with the <code>facet.range.other</code> parameter is exclusive and the "after" range is inclusive. This default, equivalent to "lower" below, will not result in double counting at the boundaries. You can use the <code>facet.range.include</code> parameter to modify this behavior using the following options:</p><div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li><p><code>lower</code>: All gap-based ranges include their lower bound.</p></li><li><p><code>upper</code>: All gap-based ranges include their upper bound.</p></li><li><p><code>edge</code>: The f
 irst and last gap ranges include their edge bounds (lower for the first one, upper for the last one) even if the corresponding upper/lower option is not specified.</p></li><li><p><code>outer</code>: The "before" and "after" ranges will be inclusive of their bounds, even if the first or last ranges already include those boundaries.</p></li><li><p><code>all</code>: Includes all options: <code>lower</code>, <code>upper</code>, <code>edge</code>, and <code>outer</code>.</p></li></ul></div></div></div>
 <p>You can specify this parameter on a per field basis with the syntax of <code>f.&lt;fieldname&gt;.facet.range.include</code>, and you can specify it multiple times to indicate multiple choices.</p>
 <div class="admonitionblock note">
 <table>
@@ -1733,7 +1728,7 @@ To ensure you avoid double-counting, do
 </td>
 </tr>
 </table>
-</div></dd><dt><code>facet.range.other</code></dt><dd><p>The <code>facet.range.other</code> parameter specifies that in addition to the counts for each range constraint between <code>facet.range.start</code> and <code>facet.range.end</code>, counts should also be computed for these options:</p><div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li><code>before</code>: All records with field values lower then lower bound of the first range.</li><li><code>after</code>: All records with field values greater then the upper bound of the last range.</li><li><code>between</code>: All records with field values between the start and end bounds of all ranges.</li><li><code>none</code>: Do not compute any counts.</li><li><code>all</code>: Compute counts for before, between, and after.</li></ul></div></div></div>
+</div></dd><dt><code>facet.range.other</code></dt><dd><p>The <code>facet.range.other</code> parameter specifies that in addition to the counts for each range constraint between <code>facet.range.start</code> and <code>facet.range.end</code>, counts should also be computed for these options:</p><div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li><p><code>before</code>: All records with field values lower then lower bound of the first range.</p></li><li><p><code>after</code>: All records with field values greater then the upper bound of the last range.</p></li><li><p><code>between</code>: All records with field values between the start and end bounds of all ranges.</p></li><li><p><code>none</code>: Do not compute any counts.</p></li><li><p><code>all</code>: Compute counts for before, between, and after.</p></li></ul></div></div></div>
 <p>This parameter can be specified on a per field basis with the syntax of <code>f.&lt;fieldname&gt;.facet.range.other</code>. In addition to the <code>all</code> option, this parameter can be specified multiple times to indicate multiple choices, but <code>none</code> will override all other options.</p></dd><dt><code>facet.range.method</code></dt><dd><p>The <code>facet.range.method</code> parameter selects the type of algorithm or method Solr should use for range faceting. Both methods produce the same results, but performance may vary.</p><div class="openblock"><div class="content d-flex flex-row"><div class="dlist"><dl><dt>filter</dt><dd>This method generates the ranges based on other facet.range parameters, and for each of them executes a filter that later intersects with the main query resultset to get the count. It will make use of the filterCache, so it will benefit of a cache large enough to contain all ranges.</dd><dt>dv</dt><dd>This method iterates the documents that matc
 h the main query, and for each of them finds the correct range for the value. This method will make use of <a href="docvalues.html#docvalues">docValues</a> (if enabled for the field) or fieldCache. The <code>dv</code> method is not supported for field type DateRangeField or when using <a href="result-grouping.html#result-grouping">group.facets</a>.</dd></dl></div></div></div>
 <p>The default value for this parameter is <code>filter</code>.</p></dd></dl></div>
 <div class="admonitionblock note">
@@ -1963,7 +1958,7 @@ facet.pivot={!range=r1}cat,inStock</code
                   </span><span style="color: #000080">"end"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"2015-01-01T00:00:00Z"</span><span style="background-color: #f8f8f8">}}},</span><span style="color: #bbbbbb">
                   </span><span style="color: #d14">"..."</span><span style="background-color: #f8f8f8">]}]}}}</span></code></pre></code></pre></div></section>
 <section class="sect2"><h3 id="additional-pivot-parameters">Additional Pivot Parameters</h3><p>Although <code>facet.pivot.mincount</code> deviates in name from the <code>facet.mincount</code> parameter used by field faceting, many of the faceting parameters described above can also be used with pivot faceting:</p>
-<div class="ulist"><ul><li><code>facet.limit</code></li><li><code>facet.offset</code></li><li><code>facet.sort</code></li><li><code>facet.overrequest.count</code></li><li><code>facet.overrequest.ratio</code></li></ul></div></section></section>
+<div class="ulist"><ul><li><p><code>facet.limit</code></p></li><li><p><code>facet.offset</code></p></li><li><p><code>facet.sort</code></p></li><li><p><code>facet.overrequest.count</code></p></li><li><p><code>facet.overrequest.ratio</code></p></li></ul></div></section></section>
 <section class="sect1"><h2 id="interval-faceting">Interval Faceting</h2><p>Another supported form of faceting is interval faceting. This sounds similar to range faceting, but the functionality is really closer to doing facet queries with range queries. Interval faceting allows you to set variable intervals and count the number of documents that have values within those intervals in the specified field.</p>
 <p>Even though the same functionality can be achieved by using a facet query with range queries, the implementation of these two methods is very different and will provide different performance depending on the context.</p>
 <p>If you are concerned about the performance of your searches you should test with both options. Interval faceting tends to be better with multiple intervals for the same fields, while facet query tend to be better in environments where filter cache is more effective (static indexes for example).</p>
@@ -1972,7 +1967,7 @@ facet.pivot={!range=r1}cat,inStock</code
 <div class="dlist"><dl><dt><code>facet.interval</code></dt><dd><p>This parameter Indicates the field where interval faceting must be applied. It can be used multiple times in the same request to indicate multiple fields.</p><p><code>facet.interval=price&amp;facet.interval=size</code></p></dd><dt><code>facet.interval.set</code></dt><dd><p>This parameter is used to set the intervals for the field, it can be specified multiple times to indicate multiple intervals. This parameter is global, which means that it will be used for all fields indicated with <code>facet.interval</code> unless there is an override for a specific field. To override this parameter on a specific field you can use: <code>f.&lt;fieldname&gt;.facet.interval.set</code>, for example:</p><div class="listingblock"><pre class="rouge highlight"><code class="language-text" data-lang="text"><pre class="highlight"><code>f.price.facet.interval.set=[0,10]&amp;f.price.facet.interval.set=(10,100]</code></pre></code></pre></div><
 /dd></dl></div>
 <section class="sect2"><h3 id="interval-syntax">Interval Syntax</h3><p>Intervals must begin with either '(' or '[', be followed by the start value, then a comma (','), the end value, and finally a closing ')' or ']’.</p>
 <p>For example:</p>
-<div class="ulist"><ul><li>(1,10) -&gt; will include values greater than 1 and lower than 10</li><li>[1,10) -&gt; will include values greater or equal to 1 and lower than 10</li><li>[1,10] -&gt; will include values greater or equal to 1 and lower or equal to 10</li></ul></div>
+<div class="ulist"><ul><li><p>(1,10) -&gt; will include values greater than 1 and lower than 10</p></li><li><p>[1,10) -&gt; will include values greater or equal to 1 and lower than 10</p></li><li><p>[1,10] -&gt; will include values greater or equal to 1 and lower or equal to 10</p></li></ul></div>
 <p>The initial and end values cannot be empty.</p>
 <p>If the interval needs to be unbounded, the special character <code>*</code> can be used for both, start and end, limits. When using this special character, the start syntax options (<code>(</code> and <code>[</code>), and end syntax options (<code>)</code> and <code>]</code>) will be treated the same. <code>[*,*]</code> will include all documents with a value in the field.</p>
 <p>The interval limits may be strings but there is no need to add quotes. All the text until the comma will be treated as the start limit, and the text after that will be the end limit. For example: <code>[Buenos Aires,New York]</code>. Keep in mind that a string-like comparison will be done to match documents in string intervals (case-sensitive). The comparator can&#8217;t be changed.</p>
@@ -2033,7 +2028,7 @@ facet.pivot={!range=r1}cat,inStock</code
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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/field-properties-by-use-case.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/field-properties-by-use-case.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/field-properties-by-use-case.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Field Properties by Use Case | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Field Properties by Use Case | 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="field-properties-by-use-case">
+<body class="" id="field-properties-by-use-case">
 <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-->
@@ -1689,7 +1684,7 @@
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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/field-type-definitions-and-properties.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/field-type-definitions-and-properties.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/field-type-definitions-and-properties.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Field Type Definitions and Properties | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Field Type Definitions and Properties | 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="field-type-definitions-and-properties">
+<body class="" id="field-type-definitions-and-properties">
 <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-->
@@ -1667,7 +1662,7 @@
   <section class="content">
      <section id="preamble" aria-label="Preamble"><p>A field type defines the analysis that will occur on a field when documents are indexed or queries are sent to the index.</p>
 <p>A field type definition can include four types of information:</p>
-<div class="ulist"><ul><li>The name of the field type (mandatory).</li><li>An implementation class name (mandatory).</li><li>If the field type is <code>TextField</code>, a description of the field analysis for the field type.</li><li>Field type properties - depending on the implementation class, some properties may be mandatory.</li></ul></div></section>
+<div class="ulist"><ul><li><p>The name of the field type (mandatory).</p></li><li><p>An implementation class name (mandatory).</p></li><li><p>If the field type is <code>TextField</code>, a description of the field analysis for the field type.</p></li><li><p>Field type properties - depending on the implementation class, some properties may be mandatory.</p></li></ul></div></section>
 <section class="sect1"><h2 id="field-type-definitions-in-schema-xml">Field Type Definitions in schema.xml</h2><p>Field types are defined in <code>schema.xml</code>. Each field type is defined between <code>fieldType</code> elements. They can optionally be grouped within a <code>types</code> element. Here is an example of a field type definition for a type called <code>text_general</code>:</p>
 <div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080">&lt;fieldType</span> <span style="color: #008080">name=</span><span style="color: #d14">"text_general"</span> <span style="color: #008080">class=</span><span style="color: #d14">"solr.TextField"</span> <span style="color: #008080">positionIncrementGap=</span><span style="color: #d14">"100"</span><span style="color: #000080">&gt;</span> <i class="conum" data-value="1"></i>
   <span style="color: #000080">&lt;analyzer</span> <span style="color: #008080">type=</span><span style="color: #d14">"index"</span><span style="color: #000080">&gt;</span> <i class="conum" data-value="2"></i>
@@ -1691,7 +1686,7 @@
 <div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080">&lt;fieldType</span> <span style="color: #008080">name=</span><span style="color: #d14">"date"</span> <span style="color: #008080">class=</span><span style="color: #d14">"solr.DatePointField"</span>
            <span style="color: #008080">sortMissingLast=</span><span style="color: #d14">"true"</span> <span style="color: #008080">omitNorms=</span><span style="color: #d14">"true"</span><span style="color: #000080">/&gt;</span></code></pre></code></pre></div>
 <p>The properties that can be specified for a given field type fall into three major categories:</p>
-<div class="ulist"><ul><li>Properties specific to the field type&#8217;s class.</li><li><a href="#general-properties">General Properties</a> Solr supports for any field type.</li><li><a href="#field-default-properties">Field Default Properties</a> that can be specified on the field type that will be inherited by fields that use this type instead of the default behavior.</li></ul></div>
+<div class="ulist"><ul><li><p>Properties specific to the field type&#8217;s class.</p></li><li><p><a href="#general-properties">General Properties</a> Solr supports for any field type.</p></li><li><p><a href="#field-default-properties">Field Default Properties</a> that can be specified on the field type that will be inherited by fields that use this type instead of the default behavior.</p></li></ul></div>
 <section class="sect2"><h3 id="general-properties">General Properties</h3><p>These are the general properties for fields:</p>
 <div class="dlist"><dl><dt><code>name</code></dt><dd>The name of the fieldType. This value gets used in field definitions, in the "type" attribute. It is strongly recommended that names consist of alphanumeric or underscore characters only and not start with a digit. This is not currently strictly enforced.</dd><dt><code>class</code></dt><dd><p>The class name that gets used to store and index the data for this type. Note that you may prefix included class names with "solr." and Solr will automatically figure out which packages to search for the class - so <code>solr.TextField</code> will work.</p><p>If you are using a third-party class, you will probably need to have a fully qualified class name. The fully qualified equivalent for <code>solr.TextField</code> is <code>org.apache.solr.schema.TextField</code>.</p></dd><dt><code>positionIncrementGap</code></dt><dd>For multivalued fields, specifies a distance between multiple values, which prevents spurious phrase matches.</dd><dt><code>
 autoGeneratePhraseQueries</code></dt><dd>For text fields. If <code>true</code>, Solr automatically generates phrase queries for adjacent terms. If <code>false</code>, terms must be enclosed in double-quotes to be treated as phrases.</dd><dt><code>synonymQueryStyle</code></dt><dd><p>Query used to combine scores of overlapping query terms (i.e., synonyms). Consider a search for "blue tee" with query-time synonyms <code>tshirt,tee</code>.</p><p>Use <code>as_same_term</code> (default) to blend terms, i.e., <code>SynonymQuery(tshirt,tee)</code> where each term will be treated as equally important. Use <code>pick_best</code> to select the most significant synonym when scoring <code>Dismax(tee,tshirt)</code>. Use <code>as_distinct_terms</code> to bias scoring towards the most significant synonym <code>(pants OR slacks)</code>.</p>
 <p><code>as_same_term</code> is appropriate when terms are true synonyms (television, tv). Use <code>pick_best</code> or <code>as_distinct_terms</code> when synonyms are expanding to hyponyms <code>(q=jeans w/ jeans=&gt;jeans,pants)</code> and you want exact to come before parent and sibling concepts. See this <a href="http://opensourceconnections.com/blog/2017/11/21/solr-synonyms-mea-culpa/">blog article</a>.</p></dd><dt><code>enableGraphQueries</code></dt><dd><p>For text fields, applicable when querying with <a href="the-standard-query-parser.html#standard-query-parser-parameters"><code>sow=false</code></a> (which is the default for the <code>sow</code> parameter). Use <code>true</code>, the default, for field types with query analyzers including graph-aware filters, e.g., <a href="filter-descriptions.html#synonym-graph-filter">Synonym Graph Filter</a> and <a href="filter-descriptions.html#word-delimiter-graph-filter">Word Delimiter Graph Filter</a>.</p><p>Use <code>false</code> f
 or field types with query analyzers including filters that can match docs when some tokens are missing, e.g., <a href="filter-descriptions.html#shingle-filter">Shingle Filter</a>.</p></dd></dl></div>
@@ -1742,7 +1737,7 @@
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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/field-types-included-with-solr.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/field-types-included-with-solr.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/field-types-included-with-solr.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Field Types Included with Solr | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Field Types Included with Solr | 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="field-types-included-with-solr">
+<body class="" id="field-types-included-with-solr">
 <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-->
@@ -1702,7 +1697,7 @@ All Trie* numeric and date field types h
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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/files-screen.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/files-screen.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/files-screen.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Files Screen | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Files Screen | 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="files-screen">
+<body class="" id="files-screen">
 <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-->
@@ -1664,7 +1659,7 @@
 <p>Configuration files cannot be edited with this screen, so a text editor of some kind must be used.</p>
 <p>This screen is related to the <a href="schema-browser-screen.html#schema-browser-screen">Schema Browser Screen</a>, in that they both can display information from the schema, but the Schema Browser provides a way to drill into the analysis chain and displays linkages between field types, fields, and dynamic field rules.</p>
 <p>Many of the options defined in these configuration files are described throughout the rest of this Guide. In particular, you will want to review these sections:</p>
-<div class="ulist"><ul><li><a href="indexing-and-basic-data-operations.html#indexing-and-basic-data-operations">Indexing and Basic Data Operations</a></li><li><a href="searching.html#searching">Searching</a></li><li><a href="the-well-configured-solr-instance.html#the-well-configured-solr-instance">The Well-Configured Solr Instance</a></li><li><a href="documents-fields-and-schema-design.html#documents-fields-and-schema-design">Documents, Fields, and Schema Design</a></li></ul></div>
+<div class="ulist"><ul><li><p><a href="indexing-and-basic-data-operations.html#indexing-and-basic-data-operations">Indexing and Basic Data Operations</a></p></li><li><p><a href="searching.html#searching">Searching</a></p></li><li><p><a href="the-well-configured-solr-instance.html#the-well-configured-solr-instance">The Well-Configured Solr Instance</a></p></li><li><p><a href="documents-fields-and-schema-design.html#documents-fields-and-schema-design">Documents, Fields, and Schema Design</a></p></li></ul></div>
   </section>
 
 
@@ -1694,7 +1689,7 @@
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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/filter-descriptions.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/filter-descriptions.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/filter-descriptions.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Filter Descriptions | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Filter Descriptions | 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="filter-descriptions">
+<body class="" id="filter-descriptions">
 <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-->
@@ -1724,7 +1719,7 @@
 <span style="color: #000080">&lt;/fieldType&gt;</span></code></pre></code></pre></div>
 <p>The following sections describe the filter factories that are included in this release of Solr.</p></section>
 <section class="sect1"><h2 id="ascii-folding-filter">ASCII Folding Filter</h2><p>This filter converts alphabetic, numeric, and symbolic Unicode characters which are not in the Basic Latin Unicode block (the first 127 ASCII characters) to their ASCII equivalents, if one exists. This filter converts characters from the following Unicode blocks:</p>
-<div class="ulist"><ul><li><a href="http://www.unicode.org/charts/PDF/U0080.pdf">C1 Controls and Latin-1 Supplement</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U0100.pdf">Latin Extended-A</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U0180.pdf">Latin Extended-B</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U1E00.pdf">Latin Extended Additional</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U2C60.pdf">Latin Extended-C</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/UA720.pdf">Latin Extended-D</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U0250.pdf">IPA Extensions</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U1D00.pdf">Phonetic Extensions</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U1D80.pdf">Phonetic Extensions Supplement</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U2000.pdf">General Punctuation</a> (PDF)</li><li><a href="http://www.unicode.org/cha
 rts/PDF/U2070.pdf">Superscripts and Subscripts</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U2460.pdf">Enclosed Alphanumerics</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U2700.pdf">Dingbats</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/U2E00.pdf">Supplemental Punctuation</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/UFB00.pdf">Alphabetic Presentation Forms</a> (PDF)</li><li><a href="http://www.unicode.org/charts/PDF/UFF00.pdf">Halfwidth and Fullwidth Forms</a> (PDF)</li></ul></div>
+<div class="ulist"><ul><li><p><a href="http://www.unicode.org/charts/PDF/U0080.pdf">C1 Controls and Latin-1 Supplement</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U0100.pdf">Latin Extended-A</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U0180.pdf">Latin Extended-B</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U1E00.pdf">Latin Extended Additional</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U2C60.pdf">Latin Extended-C</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/UA720.pdf">Latin Extended-D</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U0250.pdf">IPA Extensions</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U1D00.pdf">Phonetic Extensions</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U1D80.pdf">Phonetic Extensions Supplement</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U2000.pdf">General
  Punctuation</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U2070.pdf">Superscripts and Subscripts</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U2460.pdf">Enclosed Alphanumerics</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U2700.pdf">Dingbats</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/U2E00.pdf">Supplemental Punctuation</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/UFB00.pdf">Alphabetic Presentation Forms</a> (PDF)</p></li><li><p><a href="http://www.unicode.org/charts/PDF/UFF00.pdf">Halfwidth and Fullwidth Forms</a> (PDF)</p></li></ul></div>
 <p><strong>Factory class:</strong> <code>solr.ASCIIFoldingFilterFactory</code></p>
 <p><strong>Arguments:</strong></p>
 <div class="dlist"><dl><dt><code>preserveOriginal</code></dt><dd>(boolean, default false) If true, the original token is preserved: "thé" -&gt; "the", "thé"</dd></dl></div>
@@ -1967,7 +1962,7 @@
 <span style="color: #000080">&lt;/analyzer&gt;</span></code></pre></code></pre></div>
 <p>For detailed information on this normalization form, see <a href="http://www.unicode.org/reports/tr30/tr30-4.html">Unicode TR #30: Character Foldings</a>.</p></section>
 <section class="sect1"><h2 id="icu-normalizer-2-filter">ICU Normalizer 2 Filter</h2><p>This filter factory normalizes text according to one of five Unicode Normalization Forms as described in <a href="http://unicode.org/reports/tr15/">Unicode Standard Annex #15</a>:</p>
-<div class="ulist"><ul><li>NFC: (<code>name="nfc" mode="compose"</code>) Normalization Form C, canonical decomposition</li><li>NFD: (<code>name="nfc" mode="decompose"</code>) Normalization Form D, canonical decomposition, followed by canonical composition</li><li>NFKC: (<code>name="nfkc" mode="compose"</code>) Normalization Form KC, compatibility decomposition</li><li>NFKD: (<code>name="nfkc" mode="decompose"</code>) Normalization Form KD, compatibility decomposition, followed by canonical composition</li><li>NFKC_Casefold: (<code>name="nfkc_cf" mode="compose"</code>) Normalization Form KC, with additional Unicode case folding. Using the ICU Normalizer 2 Filter is a better-performing substitution for the <a href="#lower-case-filter">Lower Case Filter</a> and NFKC normalization.</li></ul></div>
+<div class="ulist"><ul><li><p>NFC: (<code>name="nfc" mode="compose"</code>) Normalization Form C, canonical decomposition</p></li><li><p>NFD: (<code>name="nfc" mode="decompose"</code>) Normalization Form D, canonical decomposition, followed by canonical composition</p></li><li><p>NFKC: (<code>name="nfkc" mode="compose"</code>) Normalization Form KC, compatibility decomposition</p></li><li><p>NFKD: (<code>name="nfkc" mode="decompose"</code>) Normalization Form KD, compatibility decomposition, followed by canonical composition</p></li><li><p>NFKC_Casefold: (<code>name="nfkc_cf" mode="compose"</code>) Normalization Form KC, with additional Unicode case folding. Using the ICU Normalizer 2 Filter is a better-performing substitution for the <a href="#lower-case-filter">Lower Case Filter</a> and NFKC normalization.</p></li></ul></div>
 <p><strong>Factory class:</strong> <code>solr.ICUNormalizer2FilterFactory</code></p>
 <p><strong>Arguments:</strong></p>
 <div class="dlist"><dl><dt><code>name</code></dt><dd>The name of the normalization form. Valid options are <code>nfc</code>, <code>nfd</code>, <code>nfkc</code>, <code>nfkd</code>, or <code>nfkc_cf</code> (the default). Required.</dd><dt><code>mode</code></dt><dd>The mode of Unicode character composition and decomposition. Valid options are: <code>compose</code> (the default) or <code>decompose</code>. Required.</dd><dt><code>filter</code></dt><dd>A Unicode set filter that can be used to e.g., exclude a set of characters from being processed. See the <a href="http://icu-project.org/apiref/icu4j/com/ibm/icu/text/UnicodeSet.html">UnicodeSet javadocs</a> for more information. Optional.</dd></dl></div>
@@ -2466,7 +2461,7 @@ Although this filter produces correct to
 <p><strong>Factory class:</strong> <code>solr.SynonymGraphFilterFactory</code></p>
 <p><strong>Arguments:</strong></p>
 <div class="dlist"><dl><dt><code>synonyms</code></dt><dd><p>(required) The path of a file that contains a list of synonyms, one per line. In the (default) <code>solr</code> format - see the <code>format</code> argument below for alternatives - blank lines and lines that begin with &#8220;#&#8221; are ignored. This may be a comma-separated list of paths.  See <a href="resource-loading.html#resource-loading">Resource Loading</a> for more information.</p><p>There are two ways to specify synonym mappings:</p>
-<ul><li>A comma-separated list of words. If the token matches any of the words, then all the words in the list are substituted, which will include the original token.</li><li>Two comma-separated lists of words with the symbol "=&gt;" between them. If the token matches any word on the left, then the list on the right is substituted. The original token will not be included unless it is also in the list on the right.</li></ul></dd><dt><code>ignoreCase</code></dt><dd>(optional; default: <code>false</code>) If <code>true</code>, synonyms will be matched case-insensitively.</dd><dt><code>expand</code></dt><dd>(optional; default: <code>true</code>) If <code>true</code>, a synonym will be expanded to all equivalent synonyms. If <code>false</code>, all equivalent synonyms will be reduced to the first in the list.</dd><dt><code>format</code></dt><dd>(optional; default: <code>solr</code>) Controls how the synonyms will be parsed. The short names <code>solr</code> (for <a href="https://lucene.a
 pache.org/core/8_6_0//analyzers-common/org/apache/lucene/analysis/synonym/SolrSynonymParser.html"><code>SolrSynonymParser)</code></a> and <code>wordnet</code> (for <a href="https://lucene.apache.org/core/8_6_0//analyzers-common/org/apache/lucene/analysis/synonym/WordnetSynonymParser.html"><code>WordnetSynonymParser</code></a> ) are supported, or you may alternatively supply the name of your own <a href="https://lucene.apache.org/core/8_6_0//analyzers-common/org/apache/lucene/analysis/synonym/SynonymMap.Builder.html"><code>SynonymMap.Builder</code></a> subclass.</dd><dt><code>tokenizerFactory</code></dt><dd><p>(optional; default: <code>WhitespaceTokenizerFactory</code>) The name of the tokenizer factory to use when parsing the synonyms file. Arguments with the name prefix <code>tokenizerFactory.*</code> will be supplied as init params to the specified tokenizer factory.</p><p>Any arguments not consumed by the synonym filter factory, including those without the <code>tokenizerFactory.
 *</code> prefix, will also be supplied as init params to the tokenizer factory.</p>
+<ul><li><p>A comma-separated list of words. If the token matches any of the words, then all the words in the list are substituted, which will include the original token.</p></li><li><p>Two comma-separated lists of words with the symbol "=&gt;" between them. If the token matches any word on the left, then the list on the right is substituted. The original token will not be included unless it is also in the list on the right.</p></li></ul></dd><dt><code>ignoreCase</code></dt><dd>(optional; default: <code>false</code>) If <code>true</code>, synonyms will be matched case-insensitively.</dd><dt><code>expand</code></dt><dd>(optional; default: <code>true</code>) If <code>true</code>, a synonym will be expanded to all equivalent synonyms. If <code>false</code>, all equivalent synonyms will be reduced to the first in the list.</dd><dt><code>format</code></dt><dd>(optional; default: <code>solr</code>) Controls how the synonyms will be parsed. The short names <code>solr</code> (for <a href="ht
 tps://lucene.apache.org/core/8_6_0//analyzers-common/org/apache/lucene/analysis/synonym/SolrSynonymParser.html"><code>SolrSynonymParser)</code></a> and <code>wordnet</code> (for <a href="https://lucene.apache.org/core/8_6_0//analyzers-common/org/apache/lucene/analysis/synonym/WordnetSynonymParser.html"><code>WordnetSynonymParser</code></a> ) are supported, or you may alternatively supply the name of your own <a href="https://lucene.apache.org/core/8_6_0//analyzers-common/org/apache/lucene/analysis/synonym/SynonymMap.Builder.html"><code>SynonymMap.Builder</code></a> subclass.</dd><dt><code>tokenizerFactory</code></dt><dd><p>(optional; default: <code>WhitespaceTokenizerFactory</code>) The name of the tokenizer factory to use when parsing the synonyms file. Arguments with the name prefix <code>tokenizerFactory.*</code> will be supplied as init params to the specified tokenizer factory.</p><p>Any arguments not consumed by the synonym filter factory, including those without the <code>tok
 enizerFactory.*</code> prefix, will also be supplied as init params to the tokenizer factory.</p>
 <p>If <code>tokenizerFactory</code> is specified, then <code>analyzer</code> may not be, and vice versa.</p></dd><dt><code>analyzer</code></dt><dd>(optional; default: <code>WhitespaceTokenizerFactory</code>) The name of the analyzer class to use when parsing the synonyms file. If <code>analyzer</code> is specified, then <code>tokenizerFactory</code> may not be, and vice versa.</dd></dl></div>
 <p>For the following examples, assume a synonyms file named <code>mysynonyms.txt</code>:</p>
 <div class="listingblock"><pre class="rouge highlight"><code class="language-text" data-lang="text"><pre class="highlight"><code>couch,sofa,divan
@@ -2585,7 +2580,7 @@ lion =&gt; panthera leo|0.9, simba|0.8,
 <p>If you use this filter during indexing, you must follow it with a Flatten Graph Filter to squash tokens on top of one another like the Word Delimiter Filter, because the indexer can&#8217;t directly consume a graph. To get fully correct positional queries when tokens are split, you should instead use this filter at query time.</p>
 <p>Note: although this filter produces correct token graphs, it cannot consume an input token graph correctly.</p>
 <p>The rules for determining delimiters are determined as follows:</p>
-<div class="ulist"><ul><li>A change in case within a word: "CamelCase" -&gt; "Camel", "Case". This can be disabled by setting <code>splitOnCaseChange="0"</code>.</li><li>A transition from alpha to numeric characters or vice versa: "Gonzo5000" -&gt; "Gonzo", "5000" "4500XL" -&gt; "4500", "XL". This can be disabled by setting <code>splitOnNumerics="0"</code>.</li><li>Non-alphanumeric characters (discarded): "hot-spot" -&gt; "hot", "spot"</li><li>A trailing "'s" is removed: "O&#8217;Reilly&#8217;s" -&gt; "O", "Reilly"</li><li>Any leading or trailing delimiters are discarded: "--hot-spot--" -&gt; "hot", "spot"</li></ul></div>
+<div class="ulist"><ul><li><p>A change in case within a word: "CamelCase" -&gt; "Camel", "Case". This can be disabled by setting <code>splitOnCaseChange="0"</code>.</p></li><li><p>A transition from alpha to numeric characters or vice versa: "Gonzo5000" -&gt; "Gonzo", "5000" "4500XL" -&gt; "4500", "XL". This can be disabled by setting <code>splitOnNumerics="0"</code>.</p></li><li><p>Non-alphanumeric characters (discarded): "hot-spot" -&gt; "hot", "spot"</p></li><li><p>A trailing "'s" is removed: "O&#8217;Reilly&#8217;s" -&gt; "O", "Reilly"</p></li><li><p>Any leading or trailing delimiters are discarded: "--hot-spot--" -&gt; "hot", "spot"</p></li></ul></div>
 <p><strong>Factory class:</strong> <code>solr.WordDelimiterGraphFilterFactory</code></p>
 <p><strong>Arguments:</strong></p>
 <div class="dlist"><dl><dt><code>generateWordParts</code></dt><dd>(integer, default 1) If non-zero, splits words at delimiters. For example:"CamelCase", "hot-spot" -&gt; "Camel", "Case", "hot", "spot"</dd><dt><code>generateNumberParts</code></dt><dd>(integer, default 1) If non-zero, splits numeric strings at delimiters:"1947-32" -&gt;*"1947", "32"</dd><dt><code>splitOnCaseChange</code></dt><dd>(integer, default 1) If 0, words are not split on camel-case changes:"BugBlaster-XL" -&gt; "BugBlaster", "XL". Example 1 below illustrates the default (non-zero) splitting behavior.</dd><dt><code>splitOnNumerics</code></dt><dd>(integer, default 1) If 0, don&#8217;t split words on transitions from alpha to numeric:"FemBot3000" -&gt; "Fem", "Bot3000"</dd><dt><code>catenateWords</code></dt><dd>(integer, default 0) If non-zero, maximal runs of word parts will be joined: "hot-spot-sensor&#8217;s" -&gt; "hotspotsensor"</dd><dt><code>catenateNumbers</code></dt><dd>(integer, default 0) If non-zero, ma
 ximal runs of number parts will be joined: 1947-32" -&gt; "194732"</dd><dt><code>catenateAll</code></dt><dd>(0/1, default 0) If non-zero, runs of word and number parts will be joined: "Zap-Master-9000" -&gt; "ZapMaster9000"</dd><dt><code>preserveOriginal</code></dt><dd>(integer, default 0) If non-zero, the original token is preserved: "Zap-Master-9000" -&gt; "Zap-Master-9000", "Zap", "Master", "9000"</dd><dt><code>protected</code></dt><dd>(optional) The pathname of a file that contains a list of protected words that should be passed through without splitting.</dd><dt><code>stemEnglishPossessive</code></dt><dd>(integer, default 1) If 1, strips the possessive <code>'s</code> from each subword.</dd><dt><code>types</code></dt><dd><p>(optional) The pathname of a file that contains <strong>character =&gt; type</strong> mappings, which enable customization of this filter&#8217;s splitting behavior. Recognized character types: <code>LOWER</code>, <code>UPPER</code>, <code>ALPHA</code>, <cod
 e>DIGIT</code>, <code>ALPHANUM</code>, and <code>SUBWORD_DELIM</code>.</p><p>The default for any character without a customized mapping is computed from Unicode character properties. Blank lines and comment lines starting with '#' are ignored. An example file:</p>
@@ -2676,7 +2671,7 @@ $ =&gt; DIGIT
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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/format-of-solr-xml.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/format-of-solr-xml.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/format-of-solr-xml.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
 <meta name="description" content="">
 <meta name="keywords" content=" ">
 
-<title>Format of solr.xml | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Format of solr.xml | 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="format-of-solr-xml">
+<body class="" id="format-of-solr-xml">
 <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-->
@@ -1767,7 +1762,7 @@ The <code>dividend</code> parameter must
             <div class="row">
                 <div class="col-lg-12 footer">
                &copy;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>