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 [14/28] - in
/websites/production/lucene/content/solr/guide/8_6: ./ meta-docs/
Modified: websites/production/lucene/content/solr/guide/8_6/meta-docs/asciidoc-syntax.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/meta-docs/asciidoc-syntax.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/meta-docs/asciidoc-syntax.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>AsciiDoc Syntax Cheatsheet | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>AsciiDoc Syntax Cheatsheet | 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="asciidoc-syntax">
+<body class="" id="asciidoc-syntax">
<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-->
@@ -1764,24 +1759,24 @@ Field definitions can have the following
<div class="dlist"><dl><dt>Example</dt><dd><p>Take this example from <code>configsets-api.adoc</code>:</p><div class="listingblock"><pre class="rouge highlight"><code><pre class="highlight"><code>[[configsets-create]]
== Create a ConfigSet</code></pre></code></pre></div>
<p>To link to this section, there are two approaches depending on where you are linking from:</p>
-<ul><li>From the same page, simply use the anchor name: <code><<configsets-create>></code>.</li><li>From another page, use the page name and the anchor name: <code><<configsets-api.adoc#configsets-create>></code>.</li></ul></dd></dl></div></section>
+<ul><li><p>From the same page, simply use the anchor name: <code><<configsets-create>></code>.</p></li><li><p>From another page, use the page name and the anchor name: <code><<configsets-api.adoc#configsets-create>></code>.</p></li></ul></dd></dl></div></section>
<section class="sect3"><h4 id="link-to-another-page">Link to Another Page</h4><p>To link to <em>another page</em> or a section on another page, you must refer to the full filename and refer to the section you want to link to.</p>
<p>Unfortunately, when you want to refer the reader to another page without deep-linking to a section, you cannot simply put the other file name in angle brackets and call it a day.
<strong>You must always link to a specific section</strong>. If all you want is a reference to the top of another page, you can use the implicit <code>id</code> of the page — the filename w/o the <code>.adoc</code> extension — as your anchor reference.</p>
<div class="dlist"><dl><dt>Example</dt><dd><p>To construct a link to the <code>upgrading-solr.adoc</code> page, we need to refer to the file name (<code>upgrading-solr.adoc</code>), then use the page id (<code>upgrading-solr</code>) as the anchor reference. As in:</p><div class="listingblock"><pre class="rouge highlight"><code><pre class="highlight"><code>For more information about upgrades, see <<upgrading-solr.adoc#upgrading-solr>>.</code></pre></code></pre></div></dd></dl></div></section>
<section class="sect3"><h4 id="link-to-a-section-on-another-page">Link to a Section on Another Page</h4><p>Linking to a section is the same conceptually as linking to the top of a page, you just need to take a little extra care to format the anchor ID in your link reference properly.</p>
<p>When you link to a section on another page, you must make a simple conversion of the title into the format the section ID will be created during the conversion. These are the rules that transform the sections:</p>
-<div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li>All characters are lower-cased.<ul><li><code>Using security.json with Solr</code> becomes <code>using security.json with solr</code></li></ul></li><li>All non-alpha characters are removed, with the exception of hyphens (so all periods, commas, ampersands, parentheses, etc., are stripped).<ul><li><code>using security.json with solr</code> becomes <code>using security json with solr</code></li></ul></li><li>All whitespaces are replaced with hyphens.<ul><li><code>using security json with solr</code> becomes <code>using-security-json-with-solr</code></li></ul></li></ul></div></div></div>
+<div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li><p>All characters are lower-cased.<ul><li><p><code>Using security.json with Solr</code> becomes <code>using security.json with solr</code></p></li></ul></p></li><li><p>All non-alpha characters are removed, with the exception of hyphens (so all periods, commas, ampersands, parentheses, etc., are stripped).<ul><li><p><code>using security.json with solr</code> becomes <code>using security json with solr</code></p></li></ul></p></li><li><p>All whitespaces are replaced with hyphens.<ul><li><p><code>using security json with solr</code> becomes <code>using-security-json-with-solr</code></p></li></ul></p></li></ul></div></div></div>
<div class="dlist"><dl><dt>Example</dt><dd><p>The file <code>schema-api.adoc</code> has a section "Modify the Schema" that looks like this:</p><div class="listingblock"><pre class="rouge highlight"><code><pre class="highlight"><code>== Modify the Schema
`POST /_collection_/schema`</code></pre></code></pre></div>
<p>To link from to this section from another page, you would create a link structured like this:</p>
-<div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li>the file name of the page with the section (<code>schema-api.adoc</code>),</li><li>then the hash symbol (<code>#</code>),</li><li>then the converted section title (<code>modify-the-schema</code>),</li><li>then a comma and any link title for display.</li></ul></div></div></div>
+<div class="openblock"><div class="content d-flex flex-row"><div class="ulist"><ul><li><p>the file name of the page with the section (<code>schema-api.adoc</code>),</p></li><li><p>then the hash symbol (<code>#</code>),</p></li><li><p>then the converted section title (<code>modify-the-schema</code>),</p></li><li><p>then a comma and any link title for display.</p></li></ul></div></div></div>
<p>The link in context would look like this:</p>
<div class="listingblock"><pre class="rouge highlight"><code><pre class="highlight"><code>For more information, see the section <<schema-api.adoc#modify-the-schema,Modify the Schema>>.</code></pre></code></pre></div></dd></dl></div>
<p>More info: <a class="bare" href="http://asciidoctor.org/docs/user-manual/#inter-document-cross-references">http://asciidoctor.org/docs/user-manual/#inter-document-cross-references</a></p></section></section></section>
<section class="sect1"><h2 id="ordered-and-unordered-lists">Ordered and Unordered Lists</h2><p>AsciiDoc supports three types of lists:</p>
-<div class="ulist"><ul><li>Unordered lists</li><li>Ordered lists</li><li>Labeled lists</li></ul></div>
+<div class="ulist"><ul><li><p>Unordered lists</p></li><li><p>Ordered lists</p></li><li><p>Labeled lists</p></li></ul></div>
<p>Each type of list can be mixed with the other types. So, you could have an ordered list inside a labeled list if necessary.</p>
<section class="sect2"><h3 id="unordered-lists">Unordered Lists</h3><p>Simple bulleted lists need each line to start with an asterisk (<code>*</code>). It should be the first character of the line, and be followed by a space.</p>
<p>These lists also need to be separated from the</p>
@@ -1841,12 +1836,12 @@ We prefer this style of list for paramet
| col 1 row 2 | col 2 row 2|
|===</code></pre></code></pre></div>
<p>Many more examples of formatting:</p>
-<div class="ulist"><ul><li>Columns: <a class="bare" href="http://asciidoctor.org/docs/user-manual/#cols-format">http://asciidoctor.org/docs/user-manual/#cols-format</a></li><li>Cells: <a class="bare" href="http://asciidoctor.org/docs/user-manual/#cell">http://asciidoctor.org/docs/user-manual/#cell</a></li></ul></div></section>
+<div class="ulist"><ul><li><p>Columns: <a class="bare" href="http://asciidoctor.org/docs/user-manual/#cols-format">http://asciidoctor.org/docs/user-manual/#cols-format</a></p></li><li><p>Cells: <a class="bare" href="http://asciidoctor.org/docs/user-manual/#cell">http://asciidoctor.org/docs/user-manual/#cell</a></p></li></ul></div></section>
<section class="sect2"><h3 id="more-options">More Options</h3><p>Tables can also be given footer rows, borders, and captions. You can determine the width of columns, or the width of the table as a whole.</p>
<p>CSV or DSV can also be used instead of formatting the data in pipes.</p>
<p>More info: <a class="bare" href="http://asciidoctor.org/docs/user-manual/#tables">http://asciidoctor.org/docs/user-manual/#tables</a></p></section></section>
<section class="sect1"><h2 id="admonitions-notes-warnings">Admonitions (Notes, Warnings)</h2><p>AsciiDoc supports several types of callout boxes, called "admonitions":</p>
-<div class="ulist"><ul><li>NOTE</li><li>TIP</li><li>IMPORTANT</li><li>CAUTION</li><li>WARNING</li></ul></div>
+<div class="ulist"><ul><li><p>NOTE</p></li><li><p>TIP</p></li><li><p>IMPORTANT</p></li><li><p>CAUTION</p></li><li><p>WARNING</p></li></ul></div>
<p>It is enough to start a paragraph with one of these words followed by a colon (such as <code>NOTE:</code>). When it is converted to HTML, those sections will be formatted properly - indented from the main text and showing an icon inline.</p>
<p>You can add titles to admonitions by making it an admonition block. The structure of an admonition block is like this:</p>
<div class="listingblock"><pre class="rouge highlight"><code><pre class="highlight"><code>.Title of Note
@@ -1874,7 +1869,7 @@ Text of note
<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/meta-docs/editing-tools.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/meta-docs/editing-tools.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/meta-docs/editing-tools.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Tools for Working with AsciiDoc Files | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Tools for Working with AsciiDoc Files | 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="editing-tools">
+<body class="" id="editing-tools">
<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-->
@@ -1669,7 +1664,7 @@
<p>Having some tools in your editor is helpful, though.</p>
<section class="sect2"><h3 id="doc-preview">Doc Preview</h3><p>This allows you to see your document in something close to what it might appear like when output to HTML.</p>
<p>The following information is from <a class="bare" href="http://asciidoctor.org/docs/editing-asciidoc-with-live-preview">http://asciidoctor.org/docs/editing-asciidoc-with-live-preview</a>.</p>
-<div class="ulist"><ul><li>Atom has AsciiDoc Preview, which gives you a panel that updates as you type. There are also a couple of other plugins to support AsciiDoc format and auto-complete.</li><li>There is a Live Preview browser plugin for Chrome, Firefox and Opera which allow you to open your AsciiDoc page in the browser. It will also update as you type.</li><li>There is also an Intellij IDEA plugin to support AsciiDoc format.</li></ul></div></section></section>
+<div class="ulist"><ul><li><p>Atom has AsciiDoc Preview, which gives you a panel that updates as you type. There are also a couple of other plugins to support AsciiDoc format and auto-complete.</p></li><li><p>There is a Live Preview browser plugin for Chrome, Firefox and Opera which allow you to open your AsciiDoc page in the browser. It will also update as you type.</p></li><li><p>There is also an Intellij IDEA plugin to support AsciiDoc format.</p></li></ul></div></section></section>
</section>
@@ -1688,7 +1683,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/meta-docs/jekyll.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/meta-docs/jekyll.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/meta-docs/jekyll.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Working with HTML Templates | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Working with HTML Templates | 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="jekyll">
+<body class="" id="jekyll">
<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-->
@@ -1687,7 +1682,7 @@
<p>Every document that will be converted to HTML <strong>must</strong> include at least the page title at the top of the page. Page titles are defined with a single equal sign (<code>=</code>) followed by the title that will appear at the top of the page (such as <code>= Topic of the Page</code>).</p>
<p>Many guides to Jekyll also say that defining the <code>layout</code> in the front matter is required. However, since we only use one layout for all pages, we have defined this as a default.</p>
<p>The Solr Ref Guide uses the front matter to define some custom attributes on a per-page basis:</p>
-<div class="ulist"><ul><li><code>page-children</code> - ordered list of child pages, this is used to build the site navigation menu that appears to the left of each page’s content.</li></ul></div>
+<div class="ulist"><ul><li><p><code>page-children</code> - ordered list of child pages, this is used to build the site navigation menu that appears to the left of each page’s content.</p></li></ul></div>
<p>Other page-level elements can also be defined, such as an Asciidoctor attribute that should apply only to that page, but are not needed on a regular basis.</p>
<p>The format for adding any parameter to the front matter is to use colons on both sides of the parameter, followed by the value for the parameter (such as <code>:page-toc: false</code>).</p>
<section class="sect3"><h4 id="table-of-contents">Table of Contents</h4><p>There are some optional custom attributes that can be defined in pages to affect the Table of Contents presentation in Jekyll:</p>
@@ -1795,7 +1790,7 @@ My content...
<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/meta-docs/publish.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/meta-docs/publish.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/meta-docs/publish.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Ref Guide Publication Process | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Ref Guide Publication Process | 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="publish">
+<body class="" id="publish">
<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-->
@@ -1670,7 +1665,7 @@
<section id="preamble" aria-label="Preamble"><p>This section details how to build the Guide for publication.</p></section>
<section class="sect1"><h2 id="guide-publication-overview">Guide Publication Overview</h2><div class="olist arabic"><ol class="arabic"><li>Build and publish the DRAFT version.</li><li>Continue to update docs as needed while Lucene/Solr artifact VOTE thread is ongoing.</li><li>After VOTE has passed, build and publish final version to overwrite DRAFT watermarked pages.</li></ol></div></section>
<section class="sect1"><h2 id="pre-requisites">Pre-Requisites</h2><p>In order to build the Ref Guide, you must have the following:</p>
-<div class="ulist"><ul><li>You have checked out the Lucene/Solr source code on the machine you will be doing the release from.</li><li>You have Subversion installed. This is needed for committing the HTML files to the production website repo.</li><li>You have installed Ruby and several gems described in the README file located at <code>solr/solr-ref-guide/README.adoc</code> in your Lucene/Solr checkout.</li><li>All builds must be done from the release branch the Guide is for.</li></ul></div>
+<div class="ulist"><ul><li><p>You have checked out the Lucene/Solr source code on the machine you will be doing the release from.</p></li><li><p>You have Subversion installed. This is needed for committing the HTML files to the production website repo.</p></li><li><p>You have installed Ruby and several gems described in the README file located at <code>solr/solr-ref-guide/README.adoc</code> in your Lucene/Solr checkout.</p></li><li><p>All builds must be done from the release branch the Guide is for.</p></li></ul></div>
<div class="admonitionblock note">
<table>
<tr>
@@ -1711,7 +1706,7 @@ The <code>-Dsolr-guide-version</code> sy
</div>
<p><strong>Pull Production Repo and Upload New Files</strong></p>
<div class="olist arabic"><ol class="arabic"><li><p>Checkout the directory you need to update from the svn production repo:</p><div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code><span style="color: #555555">$ </span>svn co https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/guide/<dir></code></pre></code></pre></div>
-<ul><li>This command checks out the Guide version directory into a local subdirectory with the same name as the version (such as "7_7"). You can provide a better name locally if you prefer by adding it to the end of the command shown above.</li><li>Don’t shortcut this and download the whole production website. It will take an incredibly long time and that will feel like <em>forever</em>.</li></ul></li><li>Copy the files from the build location to the checked out Guide directory. For example, if we needed to replace the Guide for Solr 7.7, we’d do <code>cp -r ./solr/build/solr-ref-guide/html-site 7_7/.</code></li><li>Use <code>svn status</code> to see the files modified. If there are any pages added or deleted, use <code>svn add <file></code> or <code>svn rm <file></code> as needed.</li><li>Commit the changes: <code>svn commit -m "Update production 7.7 Ref Guide"</code></li></ol></div>
+<ul><li><p>This command checks out the Guide version directory into a local subdirectory with the same name as the version (such as "7_7"). You can provide a better name locally if you prefer by adding it to the end of the command shown above.</p></li><li><p>Don’t shortcut this and download the whole production website. It will take an incredibly long time and that will feel like <em>forever</em>.</p></li></ul></li><li>Copy the files from the build location to the checked out Guide directory. For example, if we needed to replace the Guide for Solr 7.7, we’d do <code>cp -r ./solr/build/solr-ref-guide/html-site 7_7/.</code></li><li>Use <code>svn status</code> to see the files modified. If there are any pages added or deleted, use <code>svn add <file></code> or <code>svn rm <file></code> as needed.</li><li>Commit the changes: <code>svn commit -m "Update production 7.7 Ref Guide"</code></li></ol></div>
<p><strong>Verify Upload Successful</strong></p>
<p>Spot-check a few pages to verify that the DRAFT watermark is gone, and also
that Solr Javadocs link back to Lucene’s correctly (the UpdateRequestProcessor
@@ -1741,7 +1736,7 @@ The <code>-Dsolr-guide-version</code> sy
<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/metrics-history.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/metrics-history.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/metrics-history.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Metrics History | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Metrics History | 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="metrics-history">
+<body class="" id="metrics-history">
<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-->
@@ -1703,7 +1698,7 @@ time series is periodically resampled to
are periodically resampled again to build even coarser-grained series.</p>
<p>In the default configuration selected metrics are sampled every 60 seconds, and the following
time series are built:</p>
-<div class="ulist"><ul><li>240 samples, every 60 sec (4 hours)</li><li>288 samples, every 600 sec (48 hours)</li><li>336 samples, every 1h (2 weeks)</li><li>180 samples, every 4h (2 months)</li><li>365 samples, every 1 day (1 year)</li></ul></div>
+<div class="ulist"><ul><li><p>240 samples, every 60 sec (4 hours)</p></li><li><p>288 samples, every 600 sec (48 hours)</p></li><li><p>336 samples, every 1h (2 weeks)</p></li><li><p>180 samples, every 4h (2 months)</p></li><li><p>365 samples, every 1 day (1 year)</p></li></ul></div>
<p>This means that the total number of samples in all data series is constant, and consequently
the size of this data structure is also constant (because the size of the moving window is fixed, and
older samples are replaced by newer ones). This arrangement is referred to as a
@@ -1724,7 +1719,7 @@ to identify databases with the same name
named like this: <code>solr.jvm.localhost:8983_solr</code>, <code>solr.node.localhost:7574_solr</code>, but per-replica names are
already unique across the cluster so they are named like this: <code>solr.core.gettingstarted.shard1.replica_n1</code>.</p></section>
<section class="sect2"><h3 id="collected-metrics">Collected Metrics</h3><p>Currently the following selected metrics are tracked:</p>
-<div class="ulist"><ul><li>Non-aggregated <code>solr.core</code> and aggregated <code>solr.collection</code> metrics:<ul><li><code>QUERY./select.requests</code></li><li><code>UPDATE./update.requests</code></li><li><code>INDEX.sizeInBytes</code></li><li><code>numShards</code> (aggregated, active shards)</li><li><code>numReplicas</code> (aggregated, active replicas)</li></ul></li><li><code>solr.node</code> metrics:<ul><li><code>CONTAINER.fs.coreRoot.usableSpace</code></li><li><code>numNodes</code> (aggregated, number of live nodes)</li></ul></li><li><code>solr.jvm</code> metrics:<ul><li><code>memory.heap.used</code></li><li><code>os.processCpuLoad</code></li><li><code>os.systemLoadAverage</code></li></ul></li></ul></div>
+<div class="ulist"><ul><li><p>Non-aggregated <code>solr.core</code> and aggregated <code>solr.collection</code> metrics:<ul><li><p><code>QUERY./select.requests</code></p></li><li><p><code>UPDATE./update.requests</code></p></li><li><p><code>INDEX.sizeInBytes</code></p></li><li><p><code>numShards</code> (aggregated, active shards)</p></li><li><p><code>numReplicas</code> (aggregated, active replicas)</p></li></ul></p></li><li><p><code>solr.node</code> metrics:<ul><li><p><code>CONTAINER.fs.coreRoot.usableSpace</code></p></li><li><p><code>numNodes</code> (aggregated, number of live nodes)</p></li></ul></p></li><li><p><code>solr.jvm</code> metrics:<ul><li><p><code>memory.heap.used</code></p></li><li><p><code>os.processCpuLoad</code></p></li><li><p><code>os.systemLoadAverage</code></p></li></ul></p></li></ul></div>
<p>Separate databases are created for each of these groups, and each database keeps data for
all metrics listed in that group.</p>
<div class="admonitionblock note">
@@ -1757,10 +1752,10 @@ the call from originating node to the cu
sufficient. This happens to make sense for the default built-in sets of metrics. Future extensions will
provide other aggregation strategies (such as, average, max, min, etc.).</p></section></section>
<section class="sect1"><h2 id="metrics-history-configuration">Metrics History Configuration</h2><p>There are two ways to configure this subsystem:</p>
-<div class="ulist"><ul><li><code>/clusterprops.json</code> - this is the primary mechanism. It uses the cluster properties JSON
-file in ZooKeeper. Configuration is stored in the <code>/metrics/history</code> element in a JSON map.</li><li><code>solr.xml</code> - this is the secondary mechanism, which is not recommended but provided for consistency
+<div class="ulist"><ul><li><p><code>/clusterprops.json</code> - this is the primary mechanism. It uses the cluster properties JSON
+file in ZooKeeper. Configuration is stored in the <code>/metrics/history</code> element in a JSON map.</p></li><li><p><code>solr.xml</code> - this is the secondary mechanism, which is not recommended but provided for consistency
with the existing metrics configuration section in this file. Configuration is stored in the
-<code>/solr/metrics/history</code> element of this file.</li></ul></div>
+<code>/solr/metrics/history</code> element of this file.</p></li></ul></div>
<p>Currently the following configuration options are supported:</p>
<div class="dlist"><dl><dt><code>enable</code></dt><dd>boolean, default is <code>true</code>. If this is <code>false</code> then metrics history is not collected
but can still be retrieved from existing databases. When this is <code>true</code> then metrics are
@@ -1804,10 +1799,10 @@ for v2 API).</p>
<p>The following sections describe actions available in this API. All calls have at least one
required parameter <code>action</code>.</p>
<p>All responses contain a section named <code>state</code>, which reports the current internal state of the API:</p>
-<div class="dlist"><dl><dt><code>enableReplicas</code></dt><dd>boolean, corresponds to the <code>enableReplicas</code> configuration setting.</dd><dt><code>enableNodes</code></dt><dd>boolean, corresponds to the <code>enableNodes</code> configuration setting.</dd><dt><code>mode</code></dt><dd>one of the following values:<ul><li><code>inactive</code> - when metrics collection is disabled (but access to existing metrics history is still available).</li><li><code>memory</code> - when metrics history is kept only in memory because <code>.system</code> collection doesn’t exist. In this mode
-clients can access metrics history available on the node that received the request and on the Overseer leader.</li><li><code>index</code> - when metrics history is periodically stored in the <code>.system</code> collection. Data available in memory on
+<div class="dlist"><dl><dt><code>enableReplicas</code></dt><dd>boolean, corresponds to the <code>enableReplicas</code> configuration setting.</dd><dt><code>enableNodes</code></dt><dd>boolean, corresponds to the <code>enableNodes</code> configuration setting.</dd><dt><code>mode</code></dt><dd>one of the following values:<ul><li><p><code>inactive</code> - when metrics collection is disabled (but access to existing metrics history is still available).</p></li><li><p><code>memory</code> - when metrics history is kept only in memory because <code>.system</code> collection doesn’t exist. In this mode
+clients can access metrics history available on the node that received the request and on the Overseer leader.</p></li><li><p><code>index</code> - when metrics history is periodically stored in the <code>.system</code> collection. Data available in memory on
the node that accepted the request is retrieved from memory, any other data is retrieved from the
-<code>.system</code> collection (so it’s at least <code>syncPeriod</code> old).</li></ul></dd></dl></div>
+<code>.system</code> collection (so it’s at least <code>syncPeriod</code> old).</p></li></ul></dd></dl></div>
<p>Also, the response header section (<code>responseHeader</code>) contains <code>zkConnected</code> boolean property that indicates
whether the current node is a part of SolrCloud cluster.</p>
<section class="sect2"><h3 id="list-databases">List Databases</h3><p>The query parameter <code>action=list</code> produces a list of available databases. It supports the following parameters:</p>
@@ -1922,9 +1917,9 @@ database was update. All timestamps retu
<section class="sect2"><h3 id="get-database-data">Get Database Data</h3><p>The query parameter <code>action=get</code> retrieves all data collected in the specified database.</p>
<p>The following parameters are supported:</p>
<div class="dlist"><dl><dt><code>name</code></dt><dd>string, required: database name.</dd><dt><code>format</code></dt><dd>string, optional, default is <code>list</code>. Format of the data. Currently the
-following formats are supported:<ul><li><code>list</code> - each datapoint is returned as separate JSON element. For efficiency, for each
+following formats are supported:<ul><li><p><code>list</code> - each datapoint is returned as separate JSON element. For efficiency, for each
datasource in a database for each time series the timestamps are provided separately from
-values (because points from all datasources in a given time series share the same timestamps).</li><li><code>string</code> - all datapoint values and timestamps are returned as strings, with values separated by new line character.</li><li><code>graph</code> - data is returned as PNG images, Base64-encoded, containing graphs of each time series values over time.</li></ul></dd></dl></div>
+values (because points from all datasources in a given time series share the same timestamps).</p></li><li><p><code>string</code> - all datapoint values and timestamps are returned as strings, with values separated by new line character.</p></li><li><p><code>graph</code> - data is returned as PNG images, Base64-encoded, containing graphs of each time series values over time.</p></li></ul></dd></dl></div>
<p>In each case the response is structured in a similar way: archive identifiers are keys in a JSON map,
all data is placed in a <code>data</code> element, with timestamps / datapoints / graphs as values in lists or maps.</p>
<section class="sect3"><h4 id="examples">Examples</h4><p>This is the output using the default <code>list</code> format:</p>
@@ -2058,7 +2053,7 @@ all data is placed in a <code>data</code
<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/metrics-reporting.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/metrics-reporting.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/metrics-reporting.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Metrics Reporting | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Metrics Reporting | 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="metrics-reporting">
+<body class="" id="metrics-reporting">
<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-->
@@ -1694,7 +1689,7 @@
<section class="content">
<section id="preamble" aria-label="Preamble"><p>Solr includes a developer API and instrumentation for the collection of detailed performance-oriented metrics throughout the life-cycle of Solr service and its various components.</p>
<p>Internally this feature uses the <a href="http://metrics.dropwizard.io">Dropwizard Metrics API</a>, which uses the following classes of meters to measure events:</p>
-<div class="ulist"><ul><li><strong>counters</strong> - simply count events. They provide a single long value, e.g., the number of requests.</li><li><strong>meters</strong> - additionally compute rates of events. Provide a count (as above) and 1-, 5-, and 15-minute exponentially decaying rates, similar to the Unix system load average.</li><li><strong>histograms</strong> - calculate approximate distribution of events according to their values. Provide the following approximate statistics, with a similar exponential decay as above: mean (arithmetic average), median, maximum, minimum, standard deviation, and 75<sup>th</sup>, 95<sup>th</sup>, 98<sup>th</sup>, 99<sup>th</sup> and 999<sup>th</sup> percentiles.</li><li><strong>timers</strong> - measure the number and duration of events. They provide a count and histogram of timings.</li><li><strong>gauges</strong> - offer instantaneous reading of a current value, e.g., current queue depth, current number of active connections, free heap siz
e.</li></ul></div>
+<div class="ulist"><ul><li><p><strong>counters</strong> - simply count events. They provide a single long value, e.g., the number of requests.</p></li><li><p><strong>meters</strong> - additionally compute rates of events. Provide a count (as above) and 1-, 5-, and 15-minute exponentially decaying rates, similar to the Unix system load average.</p></li><li><p><strong>histograms</strong> - calculate approximate distribution of events according to their values. Provide the following approximate statistics, with a similar exponential decay as above: mean (arithmetic average), median, maximum, minimum, standard deviation, and 75<sup>th</sup>, 95<sup>th</sup>, 98<sup>th</sup>, 99<sup>th</sup> and 999<sup>th</sup> percentiles.</p></li><li><p><strong>timers</strong> - measure the number and duration of events. They provide a count and histogram of timings.</p></li><li><p><strong>gauges</strong> - offer instantaneous reading of a current value, e.g., current queue depth, current number of ac
tive connections, free heap size.</p></li></ul></div>
<p>Each group of related metrics with unique names is managed in a <strong>metric registry</strong>. Solr maintains several such registries, each corresponding to a high-level group such as: <code>jvm</code>, <code>jetty</code>, <code>node</code>, and <code>core</code> (see <a href="#metric-registries">Metric Registries</a> below).</p>
<p>For each group (and/or for each registry) there can be several <strong>reporters</strong>, which are components responsible for communication of metrics from selected registries to external systems. Currently implemented reporters support emitting metrics via JMX, Ganglia, Graphite and SLF4J.</p>
<p>There is also a dedicated <code>/admin/metrics</code> handler that can be queried to report all or a subset of the current metrics from multiple registries.</p></section>
@@ -1702,15 +1697,15 @@
<p>Metrics are maintained and accumulated through all lifecycles of components from the start of the process until its shutdown - e.g., metrics for a particular SolrCore are tracked through possibly several load, unload and/or rename operations, and are deleted only when a core is explicitly deleted. However, metrics are not persisted across process restarts; restarting Solr will discard all collected metrics.</p>
<p>These are the major groups of metrics that are collected:</p>
<section class="sect2"><h3 id="jvm-registry">JVM Registry</h3><p>This registry is returned at <code>solr.jvm</code> and includes the following information. When making requests with the <a href="#metrics-api">Metrics API</a>, you can specify <code>&group=jvm</code> to limit to only these metrics.</p>
-<div class="ulist"><ul><li>direct and mapped buffer pools</li><li>class loading / unloading</li><li>OS memory, CPU time, file descriptors, swap, system load</li><li>GC count and time</li><li>heap, non-heap memory and GC pools</li><li>number of threads, their states and deadlocks</li><li>System properties such as Java information, various installation directory paths, ports, and similar information. You can control what appears here by modifying <code>solr.xml</code>.</li></ul></div></section>
+<div class="ulist"><ul><li><p>direct and mapped buffer pools</p></li><li><p>class loading / unloading</p></li><li><p>OS memory, CPU time, file descriptors, swap, system load</p></li><li><p>GC count and time</p></li><li><p>heap, non-heap memory and GC pools</p></li><li><p>number of threads, their states and deadlocks</p></li><li><p>System properties such as Java information, various installation directory paths, ports, and similar information. You can control what appears here by modifying <code>solr.xml</code>.</p></li></ul></div></section>
<section class="sect2"><h3 id="node-corecontainer-registry">Node / CoreContainer Registry</h3><p>This registry is returned at <code>solr.node</code> and includes the following information. When making requests with the <a href="#metrics-api">Metrics API</a>, you can specify <code>&group=node</code> to limit to only these metrics.</p>
-<div class="ulist"><ul><li>handler requests (count, timing): collections, info, admin, configsets, etc.</li><li>number of cores (loaded, lazy, unloaded)</li></ul></div></section>
+<div class="ulist"><ul><li><p>handler requests (count, timing): collections, info, admin, configsets, etc.</p></li><li><p>number of cores (loaded, lazy, unloaded)</p></li></ul></div></section>
<section class="sect2"><h3 id="core-solrcore-registry">Core (SolrCore) Registry</h3><p>The <a href="#core-level-metrics">Core (SolrCore) Registry</a> includes <code>solr.core.<collection></code>, one for each core. When making requests with the <a href="#metrics-api">Metrics API</a>, you can specify <code>&group=core</code> to limit to only these metrics.</p>
-<div class="ulist"><ul><li>all common RequestHandlers report: request timers / counters, timeouts, errors. Handlers that support
+<div class="ulist"><ul><li><p>all common RequestHandlers report: request timers / counters, timeouts, errors. Handlers that support
process distributed shard requests also report <code>shardRequests</code> sub-counters for each type of distributed
-request.</li><li><a href="#index-merge-metrics">index-level events</a>: meters for minor / major merges, number of merged docs, number of deleted docs, gauges for currently running merges and their size.</li><li>shard replication and transaction log replay on replicas,</li><li>open / available / pending connections for shard handler and update handler.</li></ul></div></section>
+request.</p></li><li><p><a href="#index-merge-metrics">index-level events</a>: meters for minor / major merges, number of merged docs, number of deleted docs, gauges for currently running merges and their size.</p></li><li><p>shard replication and transaction log replay on replicas,</p></li><li><p>open / available / pending connections for shard handler and update handler.</p></li></ul></div></section>
<section class="sect2"><h3 id="jetty-registry">Jetty Registry</h3><p>This registry is returned at <code>solr.jetty</code> and includes the following information. When making requests with the <a href="#metrics-api">Metrics API</a>, you can specify <code>&group=jetty</code> to limit to only these metrics.</p>
-<div class="ulist"><ul><li>threads and pools,</li><li>connection and request timers,</li><li>meters for responses by HTTP class (1xx, 2xx, etc.)</li></ul></div>
+<div class="ulist"><ul><li><p>threads and pools,</p></li><li><p>connection and request timers,</p></li><li><p>meters for responses by HTTP class (1xx, 2xx, etc.)</p></li></ul></div>
<p>In the future, metrics will be added for shard leaders and cluster nodes, including aggregations from per-core metrics.</p></section></section>
<section class="sect1"><h2 id="metrics-configuration">Metrics Configuration</h2><p>The metrics available in your system can be customized by modifying the <code><metrics></code> element in <code>solr.xml</code>.</p>
<div class="admonitionblock tip">
@@ -1739,7 +1734,7 @@ See also the section <a href="format-of-
<section class="sect2"><h3 id="the-metrics-reporters-element">The <metrics> <reporters> Element</h3><p>Reporters consume the metrics data generated by Solr. See the section <a href="#reporters">Reporters</a> below for more details on how to configure custom reporters.</p></section>
<section class="sect2"><h3 id="the-metrics-suppliers-element">The <metrics> <suppliers> Element</h3><p>Suppliers help Solr generate metrics data. The <code><metrics><suppliers></code> section of <code>solr.xml</code> allows you to define your own implementations of metrics and configure parameters for them.</p>
<p>Implementation of a custom metrics supplier is beyond the scope of this guide, but there are other customizations possible with the default implementation, via the elements described below.</p>
-<div class="dlist"><dl><dt><counter></dt><dd>This element defines the implementation and configuration of a <code>Counter</code> supplier. The default implementation does not support any configuration.</dd><dt><meter></dt><dd>This element defines the implementation of a <code>Meter</code> supplier. The default implementation supports an additional parameter:<dl><dt><code><str name="clock"></code></dt><dd>The type of clock to use for calculating EWMA rates. The supported values are:<ul><li><code>user</code>, the default, which uses <code>System.nanoTime()</code></li><li><code>cpu</code>, which uses the current thread’s CPU time</li></ul></dd></dl></dd><dt><histogram></dt><dd>This element defines the implementation of a <code>Histogram</code> supplier. This element also supports the <code>clock</code> parameter shown above with the <code>meter</code> element, and also:<dl><dt><code><str name="reservoir"></code></dt><dd>The fully-qualified class name
of the <code>Reservoir</code> implementation to use. The default is <code>com.codahale.metrics.ExponentiallyDecayingReservoir</code> but there are other options available with the <a href="http://metrics.dropwizard.io/4.1.5/manual/core.html#histograms">Codahale Metrics library</a> that Solr uses. The following parameters are supported, within the mentioned limitations:<ul><li><code>size</code>, the reservoir size. The default is 1028.</li><li><code>alpha</code>, the decay parameter. The default is 0.015. This is only valid for the <code>ExponentiallyDecayingReservoir</code>.</li><li><code>window</code>, the window size, in seconds, and only valid for the <code>SlidingTimeWindowReservoir</code>. The default is 300 (5 minutes).</li></ul></dd></dl></dd><dt><timer></dt><dd>This element defines an implementation of a <code>Timer</code> supplier. The default implementation supports the <code>clock</code> and <code>reservoir</code> parameters described above.</dd></dl></div>
+<div class="dlist"><dl><dt><counter></dt><dd>This element defines the implementation and configuration of a <code>Counter</code> supplier. The default implementation does not support any configuration.</dd><dt><meter></dt><dd>This element defines the implementation of a <code>Meter</code> supplier. The default implementation supports an additional parameter:<dl><dt><code><str name="clock"></code></dt><dd>The type of clock to use for calculating EWMA rates. The supported values are:<ul><li><p><code>user</code>, the default, which uses <code>System.nanoTime()</code></p></li><li><p><code>cpu</code>, which uses the current thread’s CPU time</p></li></ul></dd></dl></dd><dt><histogram></dt><dd>This element defines the implementation of a <code>Histogram</code> supplier. This element also supports the <code>clock</code> parameter shown above with the <code>meter</code> element, and also:<dl><dt><code><str name="reservoir"></code></dt><dd>The fully-qualif
ied class name of the <code>Reservoir</code> implementation to use. The default is <code>com.codahale.metrics.ExponentiallyDecayingReservoir</code> but there are other options available with the <a href="http://metrics.dropwizard.io/4.1.5/manual/core.html#histograms">Codahale Metrics library</a> that Solr uses. The following parameters are supported, within the mentioned limitations:<ul><li><p><code>size</code>, the reservoir size. The default is 1028.</p></li><li><p><code>alpha</code>, the decay parameter. The default is 0.015. This is only valid for the <code>ExponentiallyDecayingReservoir</code>.</p></li><li><p><code>window</code>, the window size, in seconds, and only valid for the <code>SlidingTimeWindowReservoir</code>. The default is 300 (5 minutes).</p></li></ul></dd></dl></dd><dt><timer></dt><dd>This element defines an implementation of a <code>Timer</code> supplier. The default implementation supports the <code>clock</code> and <code>reservoir</code> parameters descr
ibed above.</dd></dl></div>
<p>As an example of a section of <code>solr.xml</code> that defines some of these custom parameters, the following defines the default <code>Meter</code> supplier with a non-default <code>clock</code> and the default <code>Timer</code> is used with a non-default reservoir:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><metrics></span>
<span style="color: #000080"><suppliers></span>
@@ -1788,7 +1783,7 @@ See also the section <a href="format-of-
<p>It takes the following arguments:</p>
<div class="dlist"><dl><dt><code>domain</code></dt><dd>The JMX domain name. If not specified then the registry name will be used.</dd><dt><code>serviceUrl</code></dt><dd>The service URL for a JMX server. If not specified, Solr will attempt to discover if the JVM has an MBean server and will use that address. See below for additional information on this.</dd><dt><code>agentId</code></dt><dd>The agent ID for a JMX server. Note either <code>serviceUrl</code> or <code>agentId</code> can be specified but not both - if both are specified then the default MBean server will be used.</dd></dl></div>
<p>Object names created by this reporter are hierarchical, dot-separated but also properly structured to form corresponding hierarchies in e.g., JConsole. This hierarchy consists of the following elements in the top-down order:</p>
-<div class="ulist"><ul><li>registry name (e.g., <code>solr.core.collection1.shard1.replica1</code>). Dot-separated registry names are also split into ObjectName hierarchy levels, so that metrics for this registry will be shown under <code>/solr/core/collection1/shard1/replica1</code> in JConsole, with each domain part being assigned to <code>dom1, dom2, …​ domN</code> property.</li><li>reporter name (the value of reporter’s <code>name</code> attribute)</li><li>category, scope and name for request handlers</li><li>or additional <code>name1, name2, …​ nameN</code> elements for metrics from other components.</li></ul></div>
+<div class="ulist"><ul><li><p>registry name (e.g., <code>solr.core.collection1.shard1.replica1</code>). Dot-separated registry names are also split into ObjectName hierarchy levels, so that metrics for this registry will be shown under <code>/solr/core/collection1/shard1/replica1</code> in JConsole, with each domain part being assigned to <code>dom1, dom2, …​ domN</code> property.</p></li><li><p>reporter name (the value of reporter’s <code>name</code> attribute)</p></li><li><p>category, scope and name for request handlers</p></li><li><p>or additional <code>name1, name2, …​ nameN</code> elements for metrics from other components.</p></li></ul></div>
<p>The JMX Reporter replaces the JMX functionality available in Solr versions before 7.0. If you have upgraded from an earlier version and have an MBean Server running when Solr starts, Solr will automatically discover the location of the local MBean server and use a default configuration for the SolrJmxReporter.</p>
<p>You can start a local MBean server with a system property at startup by adding <code>-Dcom.sun.management.jmxremote</code> to your start command. This will not add the reporter configuration to <code>solr.xml</code>, so if you enable it with a system property, you must always start Solr with the system property or JMX will not be enabled in subsequent starts.</p></section>
<section class="sect2"><h3 id="slf4j-reporter">SLF4J Reporter</h3><p>The SLF4J Reporter uses the <code>org.apache.solr.metrics.reporters.SolrSlf4jReporter</code> class.</p>
@@ -1962,11 +1957,11 @@ QUERY\./select.*requests</code></pre></c
...
<span style="color: #000080"></config></span></code></pre></code></pre></div>
<p>The following metrics are collected:</p>
-<div class="ulist"><ul><li><code>INDEX.merge.major</code> - timer for merge operations that include at least "majorMergeDocs" (default value for this parameter is 512k documents).</li><li><code>INDEX.merge.minor</code> - timer for merge operations that include less than "majorMergeDocs".</li><li><code>INDEX.merge.errors</code> - counter for merge errors.</li><li><code>INDEX.flush</code> - meter for index flush operations.</li></ul></div>
+<div class="ulist"><ul><li><p><code>INDEX.merge.major</code> - timer for merge operations that include at least "majorMergeDocs" (default value for this parameter is 512k documents).</p></li><li><p><code>INDEX.merge.minor</code> - timer for merge operations that include less than "majorMergeDocs".</p></li><li><p><code>INDEX.merge.errors</code> - counter for merge errors.</p></li><li><p><code>INDEX.flush</code> - meter for index flush operations.</p></li></ul></div>
<p>Additionally, the following gauges are reported, which help to monitor the momentary state of index merge operations:</p>
-<div class="ulist"><ul><li><code>INDEX.merge.major.running</code> - number of running major merge operations (depending on the implementation of <code>MergeScheduler</code> that is used there can be several concurrently running merge operations).</li><li><code>INDEX.merge.minor.running</code> - as above, for minor merge operations.</li><li><code>INDEX.merge.major.running.docs</code> - total number of documents in the segments being currently merged in major merge operations.</li><li><code>INDEX.merge.minor.running.docs</code> - as above, for minor merge operations.</li><li><code>INDEX.merge.major.running.segments</code> - number of segments being currently merged in major merge operations.</li><li><code>INDEX.merge.minor.running.segments</code> - as above, for minor merge operations.</li></ul></div>
+<div class="ulist"><ul><li><p><code>INDEX.merge.major.running</code> - number of running major merge operations (depending on the implementation of <code>MergeScheduler</code> that is used there can be several concurrently running merge operations).</p></li><li><p><code>INDEX.merge.minor.running</code> - as above, for minor merge operations.</p></li><li><p><code>INDEX.merge.major.running.docs</code> - total number of documents in the segments being currently merged in major merge operations.</p></li><li><p><code>INDEX.merge.minor.running.docs</code> - as above, for minor merge operations.</p></li><li><p><code>INDEX.merge.major.running.segments</code> - number of segments being currently merged in major merge operations.</p></li><li><p><code>INDEX.merge.minor.running.segments</code> - as above, for minor merge operations.</p></li></ul></div>
<p>If the boolean flag <code>mergeDetails</code> is true then the following additional metrics are collected:</p>
-<div class="ulist"><ul><li><code>INDEX.merge.major.docs</code> - meter for the number of documents merged in major merge operations</li><li><code>INDEX.merge.major.deletedDocs</code> - meter for the number of deleted documents expunged in major merge operations</li></ul></div></section></section>
+<div class="ulist"><ul><li><p><code>INDEX.merge.major.docs</code> - meter for the number of documents merged in major merge operations</p></li><li><p><code>INDEX.merge.major.deletedDocs</code> - meter for the number of deleted documents expunged in major merge operations</p></li></ul></div></section></section>
<section class="sect1"><h2 id="metrics-api">Metrics API</h2><p>The <code>admin/metrics</code> endpoint provides access to all the metrics for all metric groups.</p>
<p>A few query parameters are available to limit your request to only certain metrics:</p>
<div class="dlist"><dl><dt><code>group</code></dt><dd>The metric group to retrieve. The default is <code>all</code> to retrieve all metrics for all groups. Other possible values are: <code>jvm</code>, <code>jetty</code>, <code>node</code>, and <code>core</code>. More than one group can be specified in a request; multiple group names should be separated by a comma.</dd><dt><code>type</code></dt><dd>The type of metric to retrieve. The default is <code>all</code> to retrieve all metric types. Other possible values are <code>counter</code>, <code>gauge</code>, <code>histogram</code>, <code>meter</code>, and <code>timer</code>. More than one type can be specified in a request; multiple types should be separated by a comma.</dd><dt><code>prefix</code></dt><dd>The first characters of metric name that will filter the metrics returned to those starting with the provided string. It can be combined with <code>group</code> and/or <code>type</code> parameters. More than one prefix can be specifi
ed in a request; multiple prefixes should be separated by a comma. Prefix matching is also case-sensitive.</dd><dt><code>regex</code></dt><dd>A regular expression matching metric names. Note: dot separators in metric names must be escaped, e.g.,
@@ -1974,7 +1969,7 @@ QUERY\./select.*requests</code></pre></c
specified multiple times to retrieve multiple concrete metrics). <strong>NOTE: when this parameter is used, other
selection methods listed above are ignored.</strong> Fully-qualified name consists of registry name, colon and
metric name, with optional colon and metric property. Colons in names can be escaped using back-slash <code>\</code>
-character. Examples:<ul><li><code>key=solr.node:CONTAINER.fs.totalSpace</code></li><li><code>key=solr.core.collection1:QUERY./select.requestTimes:max_ms</code></li><li><code>key=solr.jvm:system.properties:user.name</code></li></ul></dd><dt><code>compact</code></dt><dd><p>When false, a more verbose format of the response will be returned. Instead of a response like this:</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">"metrics"</span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">[</span><span style="color: #bbbbbb">
+character. Examples:<ul><li><p><code>key=solr.node:CONTAINER.fs.totalSpace</code></p></li><li><p><code>key=solr.core.collection1:QUERY./select.requestTimes:max_ms</code></p></li><li><p><code>key=solr.jvm:system.properties:user.name</code></p></li></ul></dd><dt><code>compact</code></dt><dd><p>When false, a more verbose format of the response will be returned. Instead of a response like this:</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">"metrics"</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="color: #d14">"solr.core.gettingstarted"</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="color: #000080">"CORE.aliases"</span><span style="background-color: #f8f8f8">:</span><span style="color: #bbbbbb"> </span><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb">
@@ -2049,7 +2044,7 @@ character. Examples:<ul><li><code>key=so
<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/migrate-to-policy-rule.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/migrate-to-policy-rule.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/migrate-to-policy-rule.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Migrating Rule-Based Replica Rules to Autoscaling Policies | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Migrating Rule-Based Replica Rules to Autoscaling Policies | 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="migrate-to-policy-rule">
+<body class="" id="migrate-to-policy-rule">
<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-->
@@ -1684,7 +1679,7 @@ Policies can be configured for the entir
<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">"replica"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"<2"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"node"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"#ANY"</span><span style="background-color: #f8f8f8">,</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"shard"</span><span style="background-color: #f8f8f8">:</span><span style="color: #d14">"#EACH"</span><span style="background-color: #f8f8f8">}</span></code></pre></code></pre></div></section>
<section class="sect1"><h2 id="differences-in-rule-syntaxes">Differences in Rule Syntaxes</h2><p>Many elements of defining rules are similar in both frameworks, but some elements are different.</p>
<section class="sect2"><h3 id="rule-operators1">Rule Operators</h3><p>All of the following operators can be directly used in the new policy syntax and they mean the same in both frameworks.</p>
-<div class="ulist"><ul><li><strong>equals (no operator required)</strong>: <code>tag:x</code> means the value for a tag must be equal to <code>'x'</code>.</li><li><strong>greater than (>)</strong>: <code>tag:>x</code> means the tag value must be greater than <code>'x'</code>. In this case, <code>'x'</code> must be a number.</li><li><strong>less than (<)</strong>: <code>tag:<x</code> means the tag value must be less than <code>âxâ</code>. In this case also, <code>'x'</code> must be a number.</li><li><strong>not equal (!)</strong>: <code>tag:!x</code> means tag value MUST NOT be equal to <code>âxâ</code>. The equals check is performed on a String value.</li></ul></div>
+<div class="ulist"><ul><li><p><strong>equals (no operator required)</strong>: <code>tag:x</code> means the value for a tag must be equal to <code>'x'</code>.</p></li><li><p><strong>greater than (>)</strong>: <code>tag:>x</code> means the tag value must be greater than <code>'x'</code>. In this case, <code>'x'</code> must be a number.</p></li><li><p><strong>less than (<)</strong>: <code>tag:<x</code> means the tag value must be less than <code>âxâ</code>. In this case also, <code>'x'</code> must be a number.</p></li><li><p><strong>not equal (!)</strong>: <code>tag:!x</code> means tag value MUST NOT be equal to <code>âxâ</code>. The equals check is performed on a String value.</p></li></ul></div>
<section class="sect3"><h4 id="fuzzy-operator1">Fuzzy Operator (~)</h4><p>There is no <code>~</code> operator in the autoscaling policy syntax.
Instead, it uses the <code>strict</code> parameter, which can be <code>true</code> or <code>false</code>.
To replace the <code>~</code> operator, use the attribute <code>"strict":false</code> instead.</p>
@@ -1696,7 +1691,7 @@ To replace the <code>~</code> operator,
<section class="sect2"><h3 id="tag-names1">Attributes</h3><p>Attributes were known as "tags" in the rule-based replica placement framework.
In the autoscaling framework, they are attributes that are used for node selection or to set global cluster-wide rules.</p>
<p>The available attributes in the autoscaling framework are similar to the tags that were available with rule-based replica placement. Attributes with the same name mean the same in both frameworks.</p>
-<div class="ulist"><ul><li><strong>cores</strong>: Number of cores in the node</li><li><strong>freedisk</strong>: Disk space available in the node</li><li><strong>host</strong>: host name of the node</li><li><strong>port</strong>: port of the node</li><li><strong>node</strong>: node name</li><li><strong>role</strong>: The role of the node. The only supported role is 'overseer'</li><li><strong>ip_1, ip_2, ip_3, ip_4</strong>: These are ip fragments for each node. For example, in a host with ip <code>192.168.1.2</code>, <code>ip_1 = 2</code>, <code>ip_2 =1</code>, <code>ip_3 = 168</code> and` ip_4 = 192`</li><li><strong>sysprop.{PROPERTY_NAME}</strong>: These are values available from system properties. <code>sysprop.key</code> means a value that is passed to the node as <code>-Dkey=keyValue</code> during the node startup. It is possible to use rules like <code>sysprop.key:expectedVal,shard:*</code></li></ul></div></section>
+<div class="ulist"><ul><li><p><strong>cores</strong>: Number of cores in the node</p></li><li><p><strong>freedisk</strong>: Disk space available in the node</p></li><li><p><strong>host</strong>: host name of the node</p></li><li><p><strong>port</strong>: port of the node</p></li><li><p><strong>node</strong>: node name</p></li><li><p><strong>role</strong>: The role of the node. The only supported role is 'overseer'</p></li><li><p><strong>ip_1, ip_2, ip_3, ip_4</strong>: These are ip fragments for each node. For example, in a host with ip <code>192.168.1.2</code>, <code>ip_1 = 2</code>, <code>ip_2 =1</code>, <code>ip_3 = 168</code> and` ip_4 = 192`</p></li><li><p><strong>sysprop.{PROPERTY_NAME}</strong>: These are values available from system properties. <code>sysprop.key</code> means a value that is passed to the node as <code>-Dkey=keyValue</code> during the node startup. It is possible to use rules like <code>sysprop.key:expectedVal,shard:*</code></p></li></ul></div></section>
<section class="sect2"><h3 id="snitches1">Snitches</h3><p>There is no equivalent for a snitch in the autoscaling policy framework.</p></section></section>
<section class="sect1"><h2 id="porting-existing-replica-placement-rules">Porting Existing Replica Placement Rules</h2><p>There is no automatic way to move from using rule-based replica placement rules to an autoscaling policy.
Instead you will need to remove your replica rules from each collection and institute a policy using the <a href="solrcloud-autoscaling-api.html#solrcloud-autoscaling-api">autoscaling API</a>.</p>
@@ -1761,7 +1756,7 @@ Instead you will need to remove your rep
<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/monitoring-solr-with-prometheus-and-grafana.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/monitoring-solr-with-prometheus-and-grafana.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/monitoring-solr-with-prometheus-and-grafana.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Monitoring Solr with Prometheus and Grafana | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Monitoring Solr with Prometheus and Grafana | 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="monitoring-solr-with-prometheus-and-grafana">
+<body class="" id="monitoring-solr-with-prometheus-and-grafana">
<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-->
@@ -1691,7 +1686,7 @@ This feature is considered experimental,
</div>
<p>The Prometheus exporter is included in Solr as a contrib, and is located in <code>contrib/prometheus-exporter</code> in your Solr instance.</p>
<p>There are three aspects to running <code>solr-exporter</code>:</p>
-<div class="ulist"><ul><li>Modify the <code>solr-exporter-config.xml</code> to define the data to collect. Solr has a default configuration you can use, but if you would like to modify it before running the exporter the first time, see the section below <a href="#exporter-configuration">Exporter Configuration</a>.</li><li>Start the exporter from within Solr. See the section below <a href="#starting-the-exporter">Starting the Exporter</a>.</li><li>Modify your Prometheus configuration to listen on the correct port. See the section below <a href="#prometheus-configuration">Prometheus Configuration</a></li></ul></div></section>
+<div class="ulist"><ul><li><p>Modify the <code>solr-exporter-config.xml</code> to define the data to collect. Solr has a default configuration you can use, but if you would like to modify it before running the exporter the first time, see the section below <a href="#exporter-configuration">Exporter Configuration</a>.</p></li><li><p>Start the exporter from within Solr. See the section below <a href="#starting-the-exporter">Starting the Exporter</a>.</p></li><li><p>Modify your Prometheus configuration to listen on the correct port. See the section below <a href="#prometheus-configuration">Prometheus Configuration</a></p></li></ul></div></section>
<section class="sect1"><h2 id="starting-the-exporter">Starting the Exporter</h2><p>You can start <code>solr-exporter</code> by running <code>./bin/solr-exporter</code> (Linux) or <code>.\bin\solr-exporter.cmd</code> (Windows) from the <code>contrib/prometheus-exporter</code> directory.</p>
<p>See the commands below depending on your operating system and Solr operating mode:</p>
<div class="openblock dynamic-tabs"><div class="content d-flex flex-row"><div class="exampleblock tab-pane" id="solr-exporter-linux"><div class="example"><p><strong class="tab-label">Linux</strong></p>
@@ -1921,7 +1916,7 @@ You can place this with your other Grafa
<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/monitoring-solr.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/monitoring-solr.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/monitoring-solr.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Monitoring Solr | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Monitoring 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="monitoring-solr">
+<body class="" id="monitoring-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-->
@@ -1695,7 +1690,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/morelikethis.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/morelikethis.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/morelikethis.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>MoreLikeThis | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>MoreLikeThis | 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="morelikethis">
+<body class="" id="morelikethis">
<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-->
@@ -1712,7 +1707,7 @@ Unless <code>mlt.boost=true</code>, all
<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/near-real-time-searching.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/near-real-time-searching.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/near-real-time-searching.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Near Real Time Searching | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Near Real Time Searching | 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="near-real-time-searching">
+<body class="" id="near-real-time-searching">
<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-->
@@ -1757,7 +1752,7 @@ For extremely high bulk indexing, especi
<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/numerical-analysis.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/numerical-analysis.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/numerical-analysis.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Interpolation, Derivatives and Integrals | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Interpolation, Derivatives and Integrals | 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="numerical-analysis">
+<body class="" id="numerical-analysis">
<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-->
@@ -1679,10 +1674,10 @@ control points because interpolation pre
<p>There are different algorithms for interpolation that will result in different predictions
along the curve. The math expressions library currently supports the following
interpolation functions:</p>
-<div class="ulist"><ul><li><code>lerp</code>: Linear interpolation predicts points that pass through each control point and
-form straight lines between control points.</li><li><code>spline</code>: Spline interpolation predicts points that pass through each control point
-and form a smooth curve between control points.</li><li><code>akima</code>: Akima spline interpolation is similar to spline interpolation but is stable to outliers.</li><li><code>loess</code>: Loess interpolation first performs a non-linear local regression to smooth the original
-control points. Then a spline is used to interpolate the smoothed control points.</li></ul></div>
+<div class="ulist"><ul><li><p><code>lerp</code>: Linear interpolation predicts points that pass through each control point and
+form straight lines between control points.</p></li><li><p><code>spline</code>: Spline interpolation predicts points that pass through each control point
+and form a smooth curve between control points.</p></li><li><p><code>akima</code>: Akima spline interpolation is similar to spline interpolation but is stable to outliers.</p></li><li><p><code>loess</code>: Loess interpolation first performs a non-linear local regression to smooth the original
+control points. Then a spline is used to interpolate the smoothed control points.</p></li></ul></div>
<section class="sect2"><h3 id="upsampling">Upsampling</h3><p>Interpolation can be used to increase the sampling rate along a curve. One example
of this would be to take a time series with samples every minute and create a data set with
samples every second. In order to do this the data points between the minutes must be created.</p>
@@ -1990,7 +1985,7 @@ function creates that data point based o
<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>