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 [27/28] - in
/websites/production/lucene/content/solr/guide/8_6: ./ meta-docs/
Modified: websites/production/lucene/content/solr/guide/8_6/transforming-result-documents.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/transforming-result-documents.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/transforming-result-documents.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Transforming Result Documents | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Transforming Result Documents | 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="transforming-result-documents">
+<body class="" id="transforming-result-documents">
<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-->
@@ -1725,7 +1720,7 @@
<section class="sect2"><h3 id="docid-docidaugmenterfactory">[docid] - DocIdAugmenterFactory</h3><p>This transformer adds the internal Lucene document id to each document â this is primarily only useful for debugging purposes.</p>
<p>DocIdAugmenterFactory does not support any request parameters, or configuration options.</p></section>
<section class="sect2"><h3 id="elevated-and-excluded">[elevated] and [excluded]</h3><p>These transformers are available only when using the <a href="the-query-elevation-component.html#the-query-elevation-component">Query Elevation Component</a>.</p>
-<div class="ulist"><ul><li><code>[elevated]</code> annotates each document to indicate if it was elevated or not.</li><li><code>[excluded]</code> annotates each document to indicate if it would have been excluded - this is only supported if you also use the <code>markExcludes</code> parameter.</li></ul></div>
+<div class="ulist"><ul><li><p><code>[elevated]</code> annotates each document to indicate if it was elevated or not.</p></li><li><p><code>[excluded]</code> annotates each document to indicate if it would have been excluded - this is only supported if you also use the <code>markExcludes</code> parameter.</p></li></ul></div>
<div class="listingblock"><pre class="rouge highlight"><code class="language-plain" data-lang="plain"><pre class="highlight"><code>fl=id,[elevated],[excluded]&excludeIds=GB18030TEST&elevateIds=6H500F0&markExcludes=true</code></pre></code></pre></div>
<div class="listingblock"><pre class="rouge highlight"><code class="language-json" data-lang="json"><pre class="highlight"><code><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb"> </span><span style="color: #000080">"response"</span><span style="background-color: #f8f8f8">:{</span><span style="color: #000080">"numFound"</span><span style="background-color: #f8f8f8">:</span><span style="color: #009999">32</span><span style="background-color: #f8f8f8">,</span><span style="color: #000080">"start"</span><span style="background-color: #f8f8f8">:</span><span style="color: #009999">0</span><span style="background-color: #f8f8f8">,</span><span style="color: #000080">"docs"</span><span style="background-color: #f8f8f8">:[</span><span style="color: #bbbbbb">
</span><span style="background-color: #f8f8f8">{</span><span style="color: #bbbbbb">
@@ -1744,7 +1739,7 @@
<section class="sect2"><h3 id="json-xml">[json] / [xml]</h3><p>These transformers replace a field value containing a string representation of a valid XML or JSON structure with the actual raw XML or JSON structure instead of just the string value. Each applies only to the specific writer, such that <code>[json]</code> only applies to <code>wt=json</code> and <code>[xml]</code> only applies to <code>wt=xml</code>.</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-plain" data-lang="plain"><pre class="highlight"><code>fl=id,source_s:[json]&wt=json</code></pre></code></pre></div></section>
<section class="sect2"><h3 id="subquery">[subquery]</h3><p>This transformer executes a separate query per transforming document passing document fields as an input for subquery parameters. It’s usually used with <code>{!join}</code> and <code>{!parent}</code> query parsers, and is intended to be an improvement for <code>[child]</code>.</p>
-<div class="ulist"><ul><li>It must be given an unique name: <code>fl=*,children:[subquery]</code></li><li>There might be a few of them, e.g., <code>fl=*,sons:[subquery],daughters:[subquery]</code>.</li><li>Every <code>[subquery]</code> occurrence adds a field into a result document with the given name, the value of this field is a document list, which is a result of executing subquery using document fields as an input.</li><li>Subquery will use the <code>/select</code> search handler by default, and will return an error if <code>/select</code> is not configured. This can be changed by supplying <code>foo.qt</code> parameter.</li></ul></div>
+<div class="ulist"><ul><li><p>It must be given an unique name: <code>fl=*,children:[subquery]</code></p></li><li><p>There might be a few of them, e.g., <code>fl=*,sons:[subquery],daughters:[subquery]</code>.</p></li><li><p>Every <code>[subquery]</code> occurrence adds a field into a result document with the given name, the value of this field is a document list, which is a result of executing subquery using document fields as an input.</p></li><li><p>Subquery will use the <code>/select</code> search handler by default, and will return an error if <code>/select</code> is not configured. This can be changed by supplying <code>foo.qt</code> parameter.</p></li></ul></div>
<p>Here is how it looks like using various formats:</p>
<figure class="listingblock"><figcaption>XML</figcaption>
<pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code> <span style="color: #000080"><result</span> <span style="color: #008080">name=</span><span style="color: #d14">"response"</span> <span style="color: #008080">numFound=</span><span style="color: #d14">"2"</span> <span style="color: #008080">start=</span><span style="color: #d14">"0"</span><span style="color: #000080">></span>
@@ -1847,7 +1842,7 @@ fl=...*,categories:[subquery]&catego
<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/understanding-analyzers-tokenizers-and-filters.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/understanding-analyzers-tokenizers-and-filters.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/understanding-analyzers-tokenizers-and-filters.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Understanding Analyzers, Tokenizers, and Filters | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Understanding Analyzers, Tokenizers, and Filters | 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="understanding-analyzers-tokenizers-and-filters">
+<body class="" id="understanding-analyzers-tokenizers-and-filters">
<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-->
@@ -1663,18 +1658,18 @@
<section class="content">
<section id="preamble" aria-label="Preamble"><p>The following sections describe how Solr breaks down and works with textual data. There are three main concepts to understand: analyzers, tokenizers, and filters.</p>
-<div class="ulist"><ul><li><a href="analyzers.html#analyzers">Field analyzers</a> are used both during ingestion, when a document is indexed, and at query time. An analyzer examines the text of fields and generates a token stream. Analyzers may be a single class or they may be composed of a series of tokenizer and filter classes.</li><li><a href="about-tokenizers.html#about-tokenizers">Tokenizers</a> break field data into lexical units, or <em>tokens</em>.</li><li><a href="about-filters.html#about-filters">Filters</a> examine a stream of tokens and keep them, transform or discard them, or create new ones. Tokenizers and filters may be combined to form pipelines, or <em>chains</em>, where the output of one is input to the next. Such a sequence of tokenizers and filters is called an <em>analyzer</em> and the resulting output of an analyzer is used to match query results or build indices.</li></ul></div></section>
+<div class="ulist"><ul><li><p><a href="analyzers.html#analyzers">Field analyzers</a> are used both during ingestion, when a document is indexed, and at query time. An analyzer examines the text of fields and generates a token stream. Analyzers may be a single class or they may be composed of a series of tokenizer and filter classes.</p></li><li><p><a href="about-tokenizers.html#about-tokenizers">Tokenizers</a> break field data into lexical units, or <em>tokens</em>.</p></li><li><p><a href="about-filters.html#about-filters">Filters</a> examine a stream of tokens and keep them, transform or discard them, or create new ones. Tokenizers and filters may be combined to form pipelines, or <em>chains</em>, where the output of one is input to the next. Such a sequence of tokenizers and filters is called an <em>analyzer</em> and the resulting output of an analyzer is used to match query results or build indices.</p></li></ul></div></section>
<section class="sect1"><h2 id="using-analyzers-tokenizers-and-filters">Using Analyzers, Tokenizers, and Filters</h2><p>Although the analysis process is used for both indexing and querying, the same analysis process need not be used for both operations. For indexing, you often want to simplify, or normalize, words. For example, setting all letters to lowercase, eliminating punctuation and accents, mapping words to their stems, and so on. Doing so can increase recall because, for example, "ram", "Ram" and "RAM" would all match a query for "ram". To increase query-time precision, a filter could be employed to narrow the matches by, for example, ignoring all-cap acronyms if you’re interested in male sheep, but not Random Access Memory.</p>
<p>The tokens output by the analysis process define the values, or <em>terms</em>, of that field and are used either to build an index of those terms when a new document is added, or to identify which documents contain the terms you are querying for.</p>
<section class="sect2"><h3 id="for-more-information">For More Information</h3><p>These sections will show you how to configure field analyzers and also serves as a reference for the details of configuring each of the available tokenizer and filter classes. It also serves as a guide so that you can configure your own analysis classes if you have special needs that cannot be met with the included filters or tokenizers.</p>
<p><strong>For Analyzers, see:</strong></p>
-<div class="ulist"><ul><li><a href="analyzers.html#analyzers">Analyzers</a>: Detailed conceptual information about Solr analyzers.</li><li><a href="running-your-analyzer.html#running-your-analyzer">Running Your Analyzer</a>: Detailed information about testing and running your Solr analyzer.</li></ul></div>
+<div class="ulist"><ul><li><p><a href="analyzers.html#analyzers">Analyzers</a>: Detailed conceptual information about Solr analyzers.</p></li><li><p><a href="running-your-analyzer.html#running-your-analyzer">Running Your Analyzer</a>: Detailed information about testing and running your Solr analyzer.</p></li></ul></div>
<p><strong>For Tokenizers, see:</strong></p>
-<div class="ulist"><ul><li><a href="about-tokenizers.html#about-tokenizers">About Tokenizers</a>: Detailed conceptual information about Solr tokenizers.</li><li><a href="tokenizers.html#tokenizers">Tokenizers</a>: Information about configuring tokenizers, and about the tokenizer factory classes included in this distribution of Solr.</li></ul></div>
+<div class="ulist"><ul><li><p><a href="about-tokenizers.html#about-tokenizers">About Tokenizers</a>: Detailed conceptual information about Solr tokenizers.</p></li><li><p><a href="tokenizers.html#tokenizers">Tokenizers</a>: Information about configuring tokenizers, and about the tokenizer factory classes included in this distribution of Solr.</p></li></ul></div>
<p><strong>For Filters, see:</strong></p>
-<div class="ulist"><ul><li><a href="about-filters.html#about-filters">About Filters</a>: Detailed conceptual information about Solr filters.</li><li><a href="filter-descriptions.html#filter-descriptions">Filter Descriptions</a>: Information about configuring filters, and about the filter factory classes included in this distribution of Solr.</li><li><a href="charfilterfactories.html#charfilterfactories">CharFilterFactories</a>: Information about filters for pre-processing input characters.</li></ul></div>
+<div class="ulist"><ul><li><p><a href="about-filters.html#about-filters">About Filters</a>: Detailed conceptual information about Solr filters.</p></li><li><p><a href="filter-descriptions.html#filter-descriptions">Filter Descriptions</a>: Information about configuring filters, and about the filter factory classes included in this distribution of Solr.</p></li><li><p><a href="charfilterfactories.html#charfilterfactories">CharFilterFactories</a>: Information about filters for pre-processing input characters.</p></li></ul></div>
<p><strong>To find out how to use Tokenizers and Filters with various languages, see:</strong></p>
-<div class="ulist"><ul><li><a href="language-analysis.html#language-analysis">Language Analysis</a>: Information about tokenizers and filters for character set conversion or for use with specific languages.</li></ul></div></section></section>
+<div class="ulist"><ul><li><p><a href="language-analysis.html#language-analysis">Language Analysis</a>: Information about tokenizers and filters for character set conversion or for use with specific languages.</p></li></ul></div></section></section>
</section>
@@ -1704,7 +1699,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/update-request-processors.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/update-request-processors.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/update-request-processors.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Update Request Processors | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Update Request Processors | 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="update-request-processors">
+<body class="" id="update-request-processors">
<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-->
@@ -1756,7 +1751,7 @@ A single update request may contain a ba
<p>A critical SolrCloud functionality is the routing and distributing of requests. For update requests this routing is implemented by the <code>DistributedUpdateRequestProcessor</code>, and this processor is given a special status by Solr due to its important function.</p>
<p>In SolrCloud mode, all processors in the chain <em>before</em> the <code>DistributedUpdateProcessor</code> are run on the first node that receives an update from the client, regardless of this node’s status as a leader or replica. The <code>DistributedUpdateProcessor</code> then forwards the update to the appropriate shard leader for the update (or to multiple leaders in the event of an update that affects multiple documents, such as a delete by query or commit). The shard leader uses a transaction log to apply <a href="updating-parts-of-documents.html#updating-parts-of-documents">Atomic Updates & Optimistic Concurrency</a> and then forwards the update to all of the shard replicas. The leader and each replica run all of the processors in the chain that are listed <em>after</em> the <code>DistributedUpdateProcessor</code>.</p>
<p>For example, consider the "dedupe" chain which we saw in a section above. Assume that a 3-node SolrCloud cluster exists where node A hosts the leader of shard1, node B hosts the leader of shard2 and node C hosts the replica of shard2. Assume that an update request is sent to node A which forwards the update to node B (because the update belongs to shard2) which then distributes the update to its replica node C. Let’s see what happens at each node:</p>
-<div class="ulist"><ul><li><strong>Node A</strong>: Runs the update through the <code>SignatureUpdateProcessor</code> (which computes the signature and puts it in the "id" field), then <code>LogUpdateProcessor</code> and then <code>DistributedUpdateProcessor</code>. This processor determines that the update actually belongs to node B and is forwarded to node B. The update is not processed further. This is required because the next processor, <code>RunUpdateProcessor</code>, will execute the update against the local shard1 index which would lead to duplicate data on shard1 and shard2.</li><li><strong>Node B</strong>: Receives the update and sees that it was forwarded by another node. The update is directly sent to <code>DistributedUpdateProcessor</code> because it has already been through the <code>SignatureUpdateProcessor</code> on node A and doing the same signature computation again would be redundant. The <code>DistributedUpdateProcessor</code> determines that the update indeed b
elongs to this node, distributes it to its replica on Node C and then forwards the update further in the chain to <code>RunUpdateProcessor</code>.</li><li><strong>Node C</strong>: Receives the update and sees that it was distributed by its leader. The update is directly sent to <code>DistributedUpdateProcessor</code> which performs some consistency checks and forwards the update further in the chain to <code>RunUpdateProcessor</code>.</li></ul></div>
+<div class="ulist"><ul><li><p><strong>Node A</strong>: Runs the update through the <code>SignatureUpdateProcessor</code> (which computes the signature and puts it in the "id" field), then <code>LogUpdateProcessor</code> and then <code>DistributedUpdateProcessor</code>. This processor determines that the update actually belongs to node B and is forwarded to node B. The update is not processed further. This is required because the next processor, <code>RunUpdateProcessor</code>, will execute the update against the local shard1 index which would lead to duplicate data on shard1 and shard2.</p></li><li><p><strong>Node B</strong>: Receives the update and sees that it was forwarded by another node. The update is directly sent to <code>DistributedUpdateProcessor</code> because it has already been through the <code>SignatureUpdateProcessor</code> on node A and doing the same signature computation again would be redundant. The <code>DistributedUpdateProcessor</code> determines that the updat
e indeed belongs to this node, distributes it to its replica on Node C and then forwards the update further in the chain to <code>RunUpdateProcessor</code>.</p></li><li><p><strong>Node C</strong>: Receives the update and sees that it was distributed by its leader. The update is directly sent to <code>DistributedUpdateProcessor</code> which performs some consistency checks and forwards the update further in the chain to <code>RunUpdateProcessor</code>.</p></li></ul></div>
<p>In summary:</p>
<div class="olist arabic"><ol class="arabic"><li>All processors before <code>DistributedUpdateProcessor</code> are only run on the first node that receives an update request whether it be a forwarding node (e.g., node A in the above example) or a leader (e.g., node B). We call these "pre-processors" or just "processors".</li><li>All processors after <code>DistributedUpdateProcessor</code> run only on the leader and the replica nodes. They are not executed on forwarding nodes. Such processors are called "post-processors".</li></ol></div>
<p>In the previous section, we saw that the <code>updateRequestProcessorChain</code> was configured with <code>processor="remove_blanks, signature"</code>. This means that such processors are of the #1 kind and are run only on the forwarding nodes. Similarly, we can configure them as the #2 kind by specifying with the attribute "post-processor" as follows:</p>
@@ -1858,7 +1853,7 @@ curl <span style="color: #d14">"http://l
<p>For example:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code><span style="color: #008080">processor</span><span style="color: #000000;font-weight: bold">=</span>atomic&atomic.field1<span style="color: #000000;font-weight: bold">=</span>add&atomic.field2<span style="color: #000000;font-weight: bold">=</span><span style="color: #0086B3">set</span>&atomic.field3<span style="color: #000000;font-weight: bold">=</span>inc&atomic.field4<span style="color: #000000;font-weight: bold">=</span>remove&atomic.field4<span style="color: #000000;font-weight: bold">=</span>remove</code></pre></code></pre></div>
<p>The above parameters convert a normal <code>update</code> operation in the following ways:</p>
-<div class="ulist"><ul><li><code>field1</code> to an atomic <code>add</code> operation</li><li><code>field2</code> to an atomic <code>set</code> operation</li><li><code>field3</code> to an atomic <code>inc</code> operation</li><li><code>field4</code> to an atomic <code>remove</code> operation</li></ul></div></section>
+<div class="ulist"><ul><li><p><code>field1</code> to an atomic <code>add</code> operation</p></li><li><p><code>field2</code> to an atomic <code>set</code> operation</p></li><li><p><code>field3</code> to an atomic <code>inc</code> operation</p></li><li><p><code>field4</code> to an atomic <code>remove</code> operation</p></li></ul></div></section>
<section class="sect3"><h4 id="templateupdateprocessorfactory">TemplateUpdateProcessorFactory</h4><p>The <code>TemplateUpdateProcessorFactory</code> can be used to add new fields to documents based on a template pattern.</p>
<p>Use the parameter <code>processor=template</code> to use it. The template parameter <code>template.field</code> (multivalued) defines the field to add and the pattern. Templates may contain placeholders which refer to other fields in the document. You can have multiple <code>Template.field</code> parameters in a single request.</p>
<p>For example:</p>
@@ -1897,7 +1892,7 @@ curl <span style="color: #d14">"http://l
<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/updatehandlers-in-solrconfig.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/updatehandlers-in-solrconfig.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/updatehandlers-in-solrconfig.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>UpdateHandlers in SolrConfig | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>UpdateHandlers in SolrConfig | 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="updatehandlers-in-solrconfig">
+<body class="" id="updatehandlers-in-solrconfig">
<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-->
@@ -1755,7 +1750,7 @@ from ~1.5MB to ~6.8MB per Solr core.</p>
<div class="row">
<div class="col-lg-12 footer">
©2020 Apache Software Foundation. All rights reserved. <br />
- Site Version: 8.6-DRAFT <br />Site last generated: 2020-07-08 <br />
+ Site Version: 8.6 <br />Site last generated: 2020-07-15 <br />
<p><img src="images/solr-sunOnly-small.png" alt="Apache Solr"/></p>
</div>
</div>
Modified: websites/production/lucene/content/solr/guide/8_6/updating-parts-of-documents.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/updating-parts-of-documents.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/updating-parts-of-documents.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Updating Parts of Documents | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Updating Parts of Documents | 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="updating-parts-of-documents">
+<body class="" id="updating-parts-of-documents">
<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-->
@@ -1790,7 +1785,7 @@ These type of updates require setting th
</span><span style="background-color: #f8f8f8">}</span></code></pre></code></pre></div></section></section>
<section class="sect1"><h2 id="in-place-updates">In-Place Updates</h2><p>In-place updates are very similar to atomic updates; in some sense, this is a subset of atomic updates. In regular atomic updates, the entire document is reindexed internally during the application of the update. However, in this approach, only the fields to be updated are affected and the rest of the documents are not reindexed internally. Hence, the efficiency of updating in-place is unaffected by the size of the documents that are updated (i.e., number of fields, size of fields, etc.). Apart from these internal differences, there is no functional difference between atomic updates and in-place updates.</p>
<p>An atomic update operation is performed using this approach only when the fields to be updated meet these three conditions:</p>
-<div class="ulist"><ul><li>are non-indexed (<code>indexed="false"</code>), non-stored (<code>stored="false"</code>), single valued (<code>multiValued="false"</code>) numeric docValues (<code>docValues="true"</code>) fields;</li><li>the <code>_version_</code> field is also a non-indexed, non-stored single valued docValues field; and,</li><li>copy targets of updated fields, if any, are also non-indexed, non-stored single valued numeric docValues fields.</li></ul></div>
+<div class="ulist"><ul><li><p>are non-indexed (<code>indexed="false"</code>), non-stored (<code>stored="false"</code>), single valued (<code>multiValued="false"</code>) numeric docValues (<code>docValues="true"</code>) fields;</p></li><li><p>the <code>_version_</code> field is also a non-indexed, non-stored single valued docValues field; and,</p></li><li><p>copy targets of updated fields, if any, are also non-indexed, non-stored single valued numeric docValues fields.</p></li></ul></div>
<p>To use in-place updates, add a modifier to the field that needs to be updated. The content can be updated or incrementally increased.</p>
<div class="dlist"><dl><dt><code>set</code></dt><dd>Set or replace the field value(s) with the specified value(s). May be specified as a single value.</dd><dt><code>inc</code></dt><dd>Increments a numeric value by a specific amount. Must be specified as a single numeric value.</dd></dl></div>
<section class="sect2"><h3 id="in-place-update-example">In-Place Update Example</h3><p>If the price and popularity fields are defined in the schema as:</p>
@@ -1824,7 +1819,7 @@ These type of updates require setting th
<p>In general, using optimistic concurrency involves the following work flow:</p>
<div class="olist arabic"><ol class="arabic"><li>A client reads a document. In Solr, one might retrieve the document with the <code>/get</code> handler to be sure to have the latest version.</li><li>A client changes the document locally.</li><li>The client resubmits the changed document to Solr, for example, perhaps with the <code>/update</code> handler.</li><li>If there is a version conflict (HTTP error code 409), the client starts the process over.</li></ol></div>
<p>When the client resubmits a changed document to Solr, the <code>_version_</code> can be included with the update to invoke optimistic concurrency control. Specific semantics are used to define when the document should be updated or when to report a conflict.</p>
-<div class="ulist"><ul><li>If the content in the <code>_version_</code> field is greater than '1' (i.e., '12345'), then the <code>_version_</code> in the document must match the <code>_version_</code> in the index.</li><li>If the content in the <code>_version_</code> field is equal to '1', then the document must simply exist. In this case, no version matching occurs, but if the document does not exist, the updates will be rejected.</li><li>If the content in the <code>_version_</code> field is less than '0' (i.e., '-1'), then the document must <strong>not</strong> exist. In this case, no version matching occurs, but if the document exists, the updates will be rejected.</li><li>If the content in the <code>_version_</code> field is equal to '0', then it doesn’t matter if the versions match or if the document exists or not. If it exists, it will be overwritten; if it does not exist, it will be added.</li></ul></div>
+<div class="ulist"><ul><li><p>If the content in the <code>_version_</code> field is greater than '1' (i.e., '12345'), then the <code>_version_</code> in the document must match the <code>_version_</code> in the index.</p></li><li><p>If the content in the <code>_version_</code> field is equal to '1', then the document must simply exist. In this case, no version matching occurs, but if the document does not exist, the updates will be rejected.</p></li><li><p>If the content in the <code>_version_</code> field is less than '0' (i.e., '-1'), then the document must <strong>not</strong> exist. In this case, no version matching occurs, but if the document exists, the updates will be rejected.</p></li><li><p>If the content in the <code>_version_</code> field is equal to '0', then it doesn’t matter if the versions match or if the document exists or not. If it exists, it will be overwritten; if it does not exist, it will be added.</p></li></ul></div>
<p>When documents are added/updated in batches even a single version conflict may lead to rejecting the entire batch. Use the parameter <code>failOnVersionConflicts=false</code> to avoid failure of the entire batch when version constraints fail for one or more documents in a batch.</p>
<p>If the document being updated does not include the <code>_version_</code> field, and atomic updates are not being used, the document will be treated by normal Solr rules, which is usually to discard the previous version.</p>
<p>When using Optimistic Concurrency, clients can include an optional <code>versions=true</code> request parameter to indicate that the <em>new</em> versions of the documents being added should be included in the response. This allows clients to immediately know what the <code>_version_</code> is of every document added without needing to make a redundant <a href="realtime-get.html#realtime-get"><code>/get</code> request</a>.</p>
@@ -1947,7 +1942,7 @@ Once configured, this update processor w
<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/upgrading-a-solr-cluster.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/upgrading-a-solr-cluster.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/upgrading-a-solr-cluster.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Upgrading a Solr Cluster | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Upgrading a Solr Cluster | 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="upgrading-a-solr-cluster">
+<body class="" id="upgrading-a-solr-cluster">
<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-->
@@ -1681,7 +1676,7 @@ The steps outlined on this page assume y
</table>
</div></section>
<section class="sect1"><h2 id="planning-your-upgrade">Planning Your Upgrade</h2><p>Here is a checklist of things you need to prepare before starting the upgrade process:</p>
-<div class="olist arabic"><ol class="arabic"><li>Examine the <a href="solr-upgrade-notes.html#solr-upgrade-notes">Solr Upgrade Notes</a> to determine if any behavior changes in the new version of Solr will affect your installation.</li><li>If not using replication (i.e., collections with <code>replicationFactor</code> less than 1), then you should make a backup of each collection. If all of your collections use replication, then you don’t technically need to make a backup since you will be upgrading and verifying each node individually.</li><li>Determine which Solr node is currently hosting the Overseer leader process in SolrCloud, as you should upgrade this node last. To determine the Overseer, use the Overseer Status API, see: <a href="collections-api.html#collections-api">Collections API</a>.</li><li>Plan to perform your upgrade during a system maintenance window if possible. You’ll be doing a rolling restart of your cluster (each node, one-by-one), but we still recom
mend doing the upgrade when system usage is minimal.</li><li>Verify the cluster is currently healthy and all replicas are active, as you should not perform an upgrade on a degraded cluster.</li><li>Re-build and test all custom server-side components against the new Solr JAR files.</li><li>Determine the values of the following variables that are used by the Solr Control Scripts:<ul><li><code>ZK_HOST</code>: The ZooKeeper connection string your current SolrCloud nodes use to connect to ZooKeeper; this value will be the same for all nodes in the cluster.</li><li><code>SOLR_HOST</code>: The hostname each Solr node used to register with ZooKeeper when joining the SolrCloud cluster; this value will be used to set the <strong>host</strong> Java system property when starting the new Solr process.</li><li><code>SOLR_PORT</code>: The port each Solr node is listening on, such as 8983.</li><li><p><code>SOLR_HOME</code>: The absolute path to the Solr home directory for each Solr node; this direc
tory must contain a <code>solr.xml</code> file. This value will be passed to the new Solr process using the <code>solr.solr.home</code> system property, see: <a href="solr-cores-and-solr-xml.html#solr-cores-and-solr-xml">Solr Cores and solr.xml</a>.</p><p>If you are upgrading from an installation of Solr 5.x or later, these values can typically be found in either <code>/var/solr/solr.in.sh</code> or <code>/etc/default/solr.in.sh</code>.</p></li></ul></li></ol></div>
+<div class="olist arabic"><ol class="arabic"><li>Examine the <a href="solr-upgrade-notes.html#solr-upgrade-notes">Solr Upgrade Notes</a> to determine if any behavior changes in the new version of Solr will affect your installation.</li><li>If not using replication (i.e., collections with <code>replicationFactor</code> less than 1), then you should make a backup of each collection. If all of your collections use replication, then you don’t technically need to make a backup since you will be upgrading and verifying each node individually.</li><li>Determine which Solr node is currently hosting the Overseer leader process in SolrCloud, as you should upgrade this node last. To determine the Overseer, use the Overseer Status API, see: <a href="collections-api.html#collections-api">Collections API</a>.</li><li>Plan to perform your upgrade during a system maintenance window if possible. You’ll be doing a rolling restart of your cluster (each node, one-by-one), but we still recom
mend doing the upgrade when system usage is minimal.</li><li>Verify the cluster is currently healthy and all replicas are active, as you should not perform an upgrade on a degraded cluster.</li><li>Re-build and test all custom server-side components against the new Solr JAR files.</li><li>Determine the values of the following variables that are used by the Solr Control Scripts:<ul><li><p><code>ZK_HOST</code>: The ZooKeeper connection string your current SolrCloud nodes use to connect to ZooKeeper; this value will be the same for all nodes in the cluster.</p></li><li><p><code>SOLR_HOST</code>: The hostname each Solr node used to register with ZooKeeper when joining the SolrCloud cluster; this value will be used to set the <strong>host</strong> Java system property when starting the new Solr process.</p></li><li><p><code>SOLR_PORT</code>: The port each Solr node is listening on, such as 8983.</p></li><li><p><p><code>SOLR_HOME</code>: The absolute path to the Solr home directory for ea
ch Solr node; this directory must contain a <code>solr.xml</code> file. This value will be passed to the new Solr process using the <code>solr.solr.home</code> system property, see: <a href="solr-cores-and-solr-xml.html#solr-cores-and-solr-xml">Solr Cores and solr.xml</a>.</p><p>If you are upgrading from an installation of Solr 5.x or later, these values can typically be found in either <code>/var/solr/solr.in.sh</code> or <code>/etc/default/solr.in.sh</code>.</p></p></li></ul></li></ol></div>
<p>You should now be ready to upgrade your cluster. Please verify this process in a test or staging cluster before doing it in production.</p></section>
<section class="sect1"><h2 id="upgrade-process">Upgrade Process</h2><p>The approach we recommend is to perform the upgrade of each Solr node, one-by-one. In other words, you will need to stop a node, upgrade it to the new version of Solr, and restart it before moving on to the next node. This means that for a short period of time, there will be a mix of "Old Solr" and "New Solr" nodes running in your cluster. We also assume that you will point the new Solr node to your existing Solr home directory where the Lucene index files are managed for each collection on the node. This means that you won’t need to move any index files around to perform the upgrade.</p>
<section class="sect2"><h3 id="step-1-stop-solr">Step 1: Stop Solr</h3><p>Begin by stopping the Solr node you want to upgrade. After stopping the node, if using a replication (i.e., collections with <code>replicationFactor</code> less than 1), verify that all leaders hosted on the downed node have successfully migrated to other replicas; you can do this by visiting the <a href="cloud-screens.html#cloud-screens">Cloud panel in the Solr Admin UI</a>. If not using replication, then any collections with shards hosted on the downed node will be temporarily off-line.</p></section>
@@ -1738,7 +1733,7 @@ The steps outlined on this page assume y
<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/uploading-data-with-index-handlers.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/uploading-data-with-index-handlers.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/uploading-data-with-index-handlers.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Uploading Data with Index Handlers | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Uploading Data with Index Handlers | 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="uploading-data-with-index-handlers">
+<body class="" id="uploading-data-with-index-handlers">
<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 @@
<div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><requestHandler</span> <span style="color: #008080">name=</span><span style="color: #d14">"/update"</span> <span style="color: #008080">class=</span><span style="color: #d14">"solr.UpdateRequestHandler"</span> <span style="color: #000080">/></span></code></pre></code></pre></div></section>
<section class="sect1"><h2 id="xml-formatted-index-updates">XML Formatted Index Updates</h2><p>Index update commands can be sent as XML message to the update handler using <code>Content-type: application/xml</code> or <code>Content-type: text/xml</code>.</p>
<section class="sect2"><h3 id="adding-documents">Adding Documents</h3><p>The XML schema recognized by the update handler for adding documents is very straightforward:</p>
-<div class="ulist"><ul><li>The <code><add></code> element introduces one more documents to be added.</li><li>The <code><doc></code> element introduces the fields making up a document.</li><li>The <code><field></code> element presents the content for a specific field.</li></ul></div>
+<div class="ulist"><ul><li><p>The <code><add></code> element introduces one more documents to be added.</p></li><li><p>The <code><doc></code> element introduces the fields making up a document.</p></li><li><p>The <code><field></code> element presents the content for a specific field.</p></li></ul></div>
<p>For example:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><add></span>
<span style="color: #000080"><doc></span>
@@ -1848,7 +1843,7 @@ It doesn’t work for child/nested d
<section class="sect1"><h2 id="json-formatted-index-updates">JSON Formatted Index Updates</h2><p>Solr can accept JSON that conforms to a defined structure, or can accept arbitrary JSON-formatted documents. If sending arbitrarily formatted JSON, there are some additional parameters that need to be sent with the update request, described below in the section <a href="transforming-and-indexing-custom-json.html#transforming-and-indexing-custom-json">Transforming and Indexing Custom JSON</a>.</p>
<section class="sect2"><h3 id="solr-style-json">Solr-Style JSON</h3><p>JSON formatted update requests may be sent to Solr’s <code>/update</code> handler using <code>Content-Type: application/json</code> or <code>Content-Type: text/json</code>.</p>
<p>JSON formatted updates can take 3 basic forms, described in depth below:</p>
-<div class="ulist"><ul><li><a href="#adding-a-single-json-document">A single document to add</a>, expressed as a top level JSON Object. To differentiate this from a set of commands, the <code>json.command=false</code> request parameter is required.</li><li><a href="#adding-multiple-json-documents">A list of documents to add</a>, expressed as a top level JSON Array containing a JSON Object per document.</li><li><a href="#sending-json-update-commands">A sequence of update commands</a>, expressed as a top level JSON Object (aka: Map).</li></ul></div>
+<div class="ulist"><ul><li><p><a href="#adding-a-single-json-document">A single document to add</a>, expressed as a top level JSON Object. To differentiate this from a set of commands, the <code>json.command=false</code> request parameter is required.</p></li><li><p><a href="#adding-multiple-json-documents">A list of documents to add</a>, expressed as a top level JSON Array containing a JSON Object per document.</p></li><li><p><a href="#sending-json-update-commands">A sequence of update commands</a>, expressed as a top level JSON Object (aka: Map).</p></li></ul></div>
<section class="sect3"><h4 id="adding-a-single-json-document">Adding a Single JSON Document</h4><p>The simplest way to add Documents via JSON is to send each document individually as a JSON Object, using the <code>/update/json/docs</code> path:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code>curl -X POST -H <span style="color: #d14">'Content-Type: application/json'</span> <span style="color: #d14">'http://localhost:8983/solr/my_collection/update/json/docs'</span> --data-binary <span style="color: #d14">'
{
@@ -1956,7 +1951,7 @@ It doesn’t work for child/nested d
<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/uploading-data-with-solr-cell-using-apache-tika.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/uploading-data-with-solr-cell-using-apache-tika.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/uploading-data-with-solr-cell-using-apache-tika.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Uploading Data with Solr Cell using Apache Tika | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Uploading Data with Solr Cell using Apache Tika | 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="uploading-data-with-solr-cell-using-apache-tika">
+<body class="" id="uploading-data-with-solr-cell-using-apache-tika">
<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-->
@@ -1697,16 +1692,16 @@ for data extraction and indexing. Downlo
<p>When this framework was under development, it was called the Solr <em>Content Extraction Library</em>, or <em>CEL</em>; from that abbreviation came this framework’s name: Solr Cell. The names Solr Cell and <code>ExtractingRequestHandler</code> are used
interchangeably for this feature.</p></section>
<section class="sect1"><h2 id="key-solr-cell-concepts">Key Solr Cell Concepts</h2><p>When using the Solr Cell framework, it is helpful to keep the following in mind:</p>
-<div class="ulist"><ul><li>Tika will automatically attempt to determine the input document type (e.g., Word, PDF, HTML) and extract the content appropriately.
+<div class="ulist"><ul><li><p>Tika will automatically attempt to determine the input document type (e.g., Word, PDF, HTML) and extract the content appropriately.
If you like, you can explicitly specify a MIME type for Tika with the <code>stream.type</code> parameter.
-See <a class="bare" href="http://tika.apache.org/1.24/formats.html">http://tika.apache.org/1.24/formats.html</a> for the file types supported.</li><li>Briefly, Tika internally works by synthesizing an XHTML document from the core content of the parsed document which is passed to a configured <a href="http://www.saxproject.org/quickstart.html">SAX</a> ContentHandler provided by Solr Cell.
+See <a class="bare" href="http://tika.apache.org/1.24/formats.html">http://tika.apache.org/1.24/formats.html</a> for the file types supported.</p></li><li><p>Briefly, Tika internally works by synthesizing an XHTML document from the core content of the parsed document which is passed to a configured <a href="http://www.saxproject.org/quickstart.html">SAX</a> ContentHandler provided by Solr Cell.
Solr responds to Tika’s SAX events to create one or more text fields from the content.
-Tika exposes document metadata as well (apart from the XHTML).</li><li>Tika produces metadata such as Title, Subject, and Author according to specifications such as the DublinCore.
+Tika exposes document metadata as well (apart from the XHTML).</p></li><li><p>Tika produces metadata such as Title, Subject, and Author according to specifications such as the DublinCore.
The metadata available is highly dependent on the file types and what they in turn contain. Some of the general metadata created is described in the section <a href="#metadata-created-by-tika">Metadata Created by Tika</a> below.
-Solr Cell supplies some metadata of its own too.</li><li>Solr Cell concatenates text from the internal XHTML into a <code>content</code> field.
-You can configure which elements should be included/ignored, and which should map to another field.</li><li>Solr Cell maps each piece of metadata onto a field.
-By default it maps to the same name but several parameters control how this is done.</li><li>When Solr Cell finishes creating the internal <code>SolrInputDocument</code>, the rest of the Lucene/Solr indexing stack takes over.
-The next step after any update handler is the <a href="update-request-processors.html#update-request-processors">Update Request Processor</a> chain.</li></ul></div>
+Solr Cell supplies some metadata of its own too.</p></li><li><p>Solr Cell concatenates text from the internal XHTML into a <code>content</code> field.
+You can configure which elements should be included/ignored, and which should map to another field.</p></li><li><p>Solr Cell maps each piece of metadata onto a field.
+By default it maps to the same name but several parameters control how this is done.</p></li><li><p>When Solr Cell finishes creating the internal <code>SolrInputDocument</code>, the rest of the Lucene/Solr indexing stack takes over.
+The next step after any update handler is the <a href="update-request-processors.html#update-request-processors">Update Request Processor</a> chain.</p></li></ul></div>
<p>Solr Cell is a contrib, which means it’s not automatically included with Solr but must be configured.
The example configsets have Solr Cell configured, but if you are not using those,
you will want to pay attention to the section <a href="#configuring-the-extractingrequesthandler-in-solrconfig-xml">Configuring the ExtractingRequestHandler in solrconfig.xml</a> below.</p>
@@ -1731,8 +1726,8 @@ This way, any extraction failures that o
<p>Once Solr is started, you can use curl to send a sample PDF included with Solr via HTTP POST:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code>curl <span style="color: #d14">'http://localhost:8983/solr/gettingstarted/update/extract?literal.id=doc1&commit=true'</span> -F <span style="color: #d14">"myfile=@example/exampledocs/solr-word.pdf"</span></code></pre></code></pre></div>
<p>The URL above calls the <code>ExtractingRequestHandler</code>, uploads the file <code>solr-word.pdf</code>, and assigns it the unique ID <code>doc1</code>. Here’s a closer look at the components of this command:</p>
-<div class="ulist"><ul><li><p>The <code>literal.id=doc1</code> parameter provides a unique ID for the document being indexed.
-Without this, the ID would be set to the absolute path to the file.</p><p>There are alternatives to this, such as mapping a metadata field to the ID, generating a new UUID, or generating an ID from a signature (hash) of the content.</p></li><li>The <code>commit=true parameter</code> causes Solr to perform a commit after indexing the document, making it immediately searchable. For optimum performance when loading many documents, don’t call the commit command until you are done.</li><li>The <code>-F</code> flag instructs curl to POST data using the Content-Type <code>multipart/form-data</code> and supports the uploading of binary files. The <code>@</code> symbol instructs curl to upload the attached file.</li><li>The argument <code>myfile=@example/exampledocs/solr-word.pdf</code> uploads the sample file. Note this includes the path, so if you upload a different file, always be sure to include either the relative or absolute path to the file.</li></ul></div>
+<div class="ulist"><ul><li><p><p>The <code>literal.id=doc1</code> parameter provides a unique ID for the document being indexed.
+Without this, the ID would be set to the absolute path to the file.</p><p>There are alternatives to this, such as mapping a metadata field to the ID, generating a new UUID, or generating an ID from a signature (hash) of the content.</p></p></li><li><p>The <code>commit=true parameter</code> causes Solr to perform a commit after indexing the document, making it immediately searchable. For optimum performance when loading many documents, don’t call the commit command until you are done.</p></li><li><p>The <code>-F</code> flag instructs curl to POST data using the Content-Type <code>multipart/form-data</code> and supports the uploading of binary files. The <code>@</code> symbol instructs curl to upload the attached file.</p></li><li><p>The argument <code>myfile=@example/exampledocs/solr-word.pdf</code> uploads the sample file. Note this includes the path, so if you upload a different file, always be sure to include either the relative or absolute path to the file.</p></li></ul></d
iv>
<p>You can also use <code>bin/post</code> to do the same thing:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code>bin/post -c gettingstarted example/exampledocs/solr-word.pdf -params <span style="color: #d14">"literal.id=doc1"</span></code></pre></code></pre></div>
<p>Now you can execute a query and find that document with a request like <code>http://localhost:8983/solr/gettingstarted/select?q=pdf</code>. The document will look something like this:</p>
@@ -1921,7 +1916,7 @@ Every instance of the text will be "Bah"
<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/uploading-structured-data-store-data-with-the-data-import-handler.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/uploading-structured-data-store-data-with-the-data-import-handler.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/uploading-structured-data-store-data-with-the-data-import-handler.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Uploading Structured Data Store Data with the Data Import Handler | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Uploading Structured Data Store Data with the Data Import Handler | Apache Solr Reference Guide 8.6</title>
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css" integrity="sha384-MCw98/SFnGE8fJT3GXwEOngsV7Zt27NXFoaoApmYm81iuXoPkFOJwJ8ERdknLPMO" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css">
@@ -71,7 +71,7 @@
</script>
</head>
-<body class="DRAFT" id="uploading-structured-data-store-data-with-the-data-import-handler">
+<body class="" id="uploading-structured-data-store-data-with-the-data-import-handler">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1673,7 +1668,7 @@
<i class="fa icon-warning" title="Warning"></i>
</td>
<td class="content">
-The Data Import Handler is deprecated as of v8.6 and is scheduled to be removed in 9.0.
+The Data Import Handler is deprecated is scheduled to be removed in 9.0. This functionality will likely migrate to a 3rd-party plugin in the near future.
</td>
</tr>
</table>
@@ -1913,7 +1908,7 @@ The default value is false, meaning that
<section class="sect2"><h3 id="the-tikaentityprocessor">The TikaEntityProcessor</h3><p>The TikaEntityProcessor uses Apache Tika to process incoming documents. This is similar to <a href="uploading-data-with-solr-cell-using-apache-tika.html#uploading-data-with-solr-cell-using-apache-tika">Uploading Data with Solr Cell using Apache Tika</a>, but using DataImportHandler options instead.</p>
<p>The parameters for this processor are described in the table below. These are in addition to the attributes common to all entity processors described above.</p>
<div class="dlist"><dl><dt>dataSource</dt><dd><p>This parameter defines the data source and an optional name which can be referred to in later parts of the configuration if needed. This is the same <code>dataSource</code> explained in the description of general entity processor attributes above.</p><p>The available data source types for this processor are:</p>
-<ul><li>BinURLDataSource: used for HTTP resources, but can also be used for files.</li><li>BinContentStreamDataSource: used for uploading content as a stream.</li><li>BinFileDataSource: used for content on the local filesystem.</li></ul></dd><dt>url</dt><dd>Required. The path to the source file(s), as a file path or a traditional internet URL.</dd><dt>htmlMapper</dt><dd><p>Optional. Allows control of how Tika parses HTML. If this parameter is defined, it must be either <strong>default</strong> or <strong>identity</strong>; if it is absent, "default" is assumed.</p><p>The "default" mapper strips much of the HTML from documents while the "identity" mapper passes all HTML as-is with no modifications.</p></dd><dt>format</dt><dd>The output format. The options are <strong>text</strong>, <strong>xml</strong>, <strong>html</strong> or <strong>none</strong>. The default is "text" if not defined. The format "none" can be used if metadata only should be indexed and not the body of the document
s.</dd><dt>parser</dt><dd>Optional. The default parser is <code>org.apache.tika.parser.AutoDetectParser</code>. If a custom or other parser should be used, it should be entered as a fully-qualified name of the class and path.</dd><dt>fields</dt><dd>The list of fields from the input documents and how they should be mapped to Solr fields. If the attribute <code>meta</code> is defined as "true", the field will be obtained from the metadata of the document and not parsed from the body of the main text.</dd><dt>extractEmbedded</dt><dd>Instructs the TikaEntityProcessor to extract embedded documents or attachments when <strong>true</strong>. If false, embedded documents and attachments will be ignored.</dd><dt>onError</dt><dd>By default, the TikaEntityProcessor will stop processing documents if it finds one that generates an error. If you define <code>onError</code> to "skip", the TikaEntityProcessor will instead skip documents that fail processing and log a message that the document was s
kipped.</dd></dl></div>
+<ul><li><p>BinURLDataSource: used for HTTP resources, but can also be used for files.</p></li><li><p>BinContentStreamDataSource: used for uploading content as a stream.</p></li><li><p>BinFileDataSource: used for content on the local filesystem.</p></li></ul></dd><dt>url</dt><dd>Required. The path to the source file(s), as a file path or a traditional internet URL.</dd><dt>htmlMapper</dt><dd><p>Optional. Allows control of how Tika parses HTML. If this parameter is defined, it must be either <strong>default</strong> or <strong>identity</strong>; if it is absent, "default" is assumed.</p><p>The "default" mapper strips much of the HTML from documents while the "identity" mapper passes all HTML as-is with no modifications.</p></dd><dt>format</dt><dd>The output format. The options are <strong>text</strong>, <strong>xml</strong>, <strong>html</strong> or <strong>none</strong>. The default is "text" if not defined. The format "none" can be used if metadata only should be indexed and not the
body of the documents.</dd><dt>parser</dt><dd>Optional. The default parser is <code>org.apache.tika.parser.AutoDetectParser</code>. If a custom or other parser should be used, it should be entered as a fully-qualified name of the class and path.</dd><dt>fields</dt><dd>The list of fields from the input documents and how they should be mapped to Solr fields. If the attribute <code>meta</code> is defined as "true", the field will be obtained from the metadata of the document and not parsed from the body of the main text.</dd><dt>extractEmbedded</dt><dd>Instructs the TikaEntityProcessor to extract embedded documents or attachments when <strong>true</strong>. If false, embedded documents and attachments will be ignored.</dd><dt>onError</dt><dd>By default, the TikaEntityProcessor will stop processing documents if it finds one that generates an error. If you define <code>onError</code> to "skip", the TikaEntityProcessor will instead skip documents that fail processing and log a message th
at the document was skipped.</dd></dl></div>
<p>Here is an example from the <code>tika</code> collection of the <code>dih</code> example (data-config file found in <code>example/example-DIH/tika/conf/tika-data-config.xml</code>):</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><dataConfig></span>
<span style="color: #000080"><dataSource</span> <span style="color: #008080">type=</span><span style="color: #d14">"BinFileDataSource"</span><span style="color: #000080">/></span>
@@ -2136,7 +2131,7 @@ The ScriptTransformer described below of
<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/using-javascript.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/using-javascript.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/using-javascript.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Using JavaScript | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Using JavaScript | 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="using-javascript">
+<body class="" id="using-javascript">
<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-->
@@ -1690,7 +1685,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/using-jmx-with-solr.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/using-jmx-with-solr.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/using-jmx-with-solr.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Using JMX with Solr | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Using JMX 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="using-jmx-with-solr">
+<body class="" id="using-jmx-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-->
@@ -1723,7 +1718,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/using-python.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/using-python.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/using-python.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Using Python | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Using Python | 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="using-python">
+<body class="" id="using-python">
<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-->
@@ -1713,7 +1708,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/using-solr-from-ruby.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/using-solr-from-ruby.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/using-solr-from-ruby.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Using Solr From Ruby | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Using Solr From Ruby | 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="using-solr-from-ruby">
+<body class="" id="using-solr-from-ruby">
<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-->
@@ -1658,7 +1653,7 @@
<section class="content">
<p>Solr has an optional Ruby response format that extends the <a href="response-writers.html#json-response-writer">JSON output</a> to allow the response to be safely eval’d by Ruby’s interpreter</p>
<p>This Ruby response format differs from JSON in the following ways:</p>
-<div class="ulist"><ul><li>Ruby’s single quoted strings are used to prevent possible string exploits<ul><li><code>\</code> and <code>'</code> are the only two characters escaped…​</li><li>unicode escapes not used…​ data is written as raw UTF-8</li></ul></li><li>nil used for null</li><li><code>=></code> used as the key/value separator in maps</li></ul></div>
+<div class="ulist"><ul><li><p>Ruby’s single quoted strings are used to prevent possible string exploits<ul><li><p><code>\</code> and <code>'</code> are the only two characters escaped…​</p></li><li><p>unicode escapes not used…​ data is written as raw UTF-8</p></li></ul></p></li><li><p>nil used for null</p></li><li><p><code>=></code> used as the key/value separator in maps</p></li></ul></div>
<p>Here’s an example Ruby response from Solr, for a request like <code>http://localhost:8983/solr/techproducts/select?q=iPod&wt=ruby&indent=on</code> (with Solr launching using <code>bin/solr start -e techproducts</code>):</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-ruby" data-lang="ruby"><pre class="highlight"><code><span style="background-color: #f8f8f8">{</span>
<span style="color: #d14">'responseHeader'</span><span style="color: #000000;font-weight: bold">=></span><span style="background-color: #f8f8f8">{</span>
@@ -1764,7 +1759,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/using-solrj.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/using-solrj.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/using-solrj.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Using SolrJ | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Using SolrJ | 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="using-solrj">
+<body class="" id="using-solrj">
<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-->
@@ -1697,7 +1692,7 @@
<p>All requests to Solr are sent by a <a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/SolrClient.html"><code>SolrClient</code></a>. SolrClient’s are the main workhorses at the core of SolrJ. They handle the work of connecting to and communicating with Solr, and are where most of the user configuration happens.</p>
<p>Requests are sent in the form of <a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/SolrRequest.html"><code>SolrRequests</code></a>, and are returned as <a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/SolrResponse.html"><code>SolrResponses</code></a>.</p>
<section class="sect2"><h3 id="types-of-solrclients">Types of SolrClients</h3><p><code>SolrClient</code> has a few concrete implementations, each geared towards a different usage-pattern or resiliency model:</p>
-<div class="ulist"><ul><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/HttpSolrClient.html"><code>HttpSolrClient</code></a> - geared towards query-centric workloads, though also a good general-purpose client. Communicates directly with a single Solr node.</li><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/Http2SolrClient.html"><code>Http2SolrClient</code></a> - async, non-blocking and general-purpose client that leverage HTTP/2. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.</li><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/LBHttpSolrClient.html"><code>LBHttpSolrClient</code></a> - balances request load across a list of Solr nodes. Adjusts the list of "in-service" nodes based on node health.</li><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/clien
t/solrj/impl/LBHttp2SolrClient.html"><code>LBHttp2SolrClient</code></a> - just like <code>LBHttpSolrClient</code> but using <code>Http2SolrClient</code> instead. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.</li><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrClient.html"><code>CloudSolrClient</code></a> - geared towards communicating with SolrCloud deployments. Uses already-recorded ZooKeeper state to discover and route requests to healthy Solr nodes.</li><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/ConcurrentUpdateSolrClient.html"><code>ConcurrentUpdateSolrClient</code></a> - geared towards indexing-centric workloads. Buffers documents internally before sending larger batches to Solr.</li><li><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/ConcurrentUpdateHttp2SolrClien
t.html"><code>ConcurrentUpdateHttp2SolrClient</code></a> - just like <code>ConcurrentUpdateSolrClient</code> but using <code>Http2SolrClient</code> instead. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.</li></ul></div></section>
+<div class="ulist"><ul><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/HttpSolrClient.html"><code>HttpSolrClient</code></a> - geared towards query-centric workloads, though also a good general-purpose client. Communicates directly with a single Solr node.</p></li><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/Http2SolrClient.html"><code>Http2SolrClient</code></a> - async, non-blocking and general-purpose client that leverage HTTP/2. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.</p></li><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/LBHttpSolrClient.html"><code>LBHttpSolrClient</code></a> - balances request load across a list of Solr nodes. Adjusts the list of "in-service" nodes based on node health.</p></li><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-sol
rj/org/apache/solr/client/solrj/impl/LBHttp2SolrClient.html"><code>LBHttp2SolrClient</code></a> - just like <code>LBHttpSolrClient</code> but using <code>Http2SolrClient</code> instead. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.</p></li><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/CloudSolrClient.html"><code>CloudSolrClient</code></a> - geared towards communicating with SolrCloud deployments. Uses already-recorded ZooKeeper state to discover and route requests to healthy Solr nodes.</p></li><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/client/solrj/impl/ConcurrentUpdateSolrClient.html"><code>ConcurrentUpdateSolrClient</code></a> - geared towards indexing-centric workloads. Buffers documents internally before sending larger batches to Solr.</p></li><li><p><a href="https://lucene.apache.org/solr/8_6_0//solr-solrj/org/apache/solr/cli
ent/solrj/impl/ConcurrentUpdateHttp2SolrClient.html"><code>ConcurrentUpdateHttp2SolrClient</code></a> - just like <code>ConcurrentUpdateSolrClient</code> but using <code>Http2SolrClient</code> instead. This class is experimental therefore its API’s might change or be removed in minor versions of SolrJ.</p></li></ul></div></section>
<section class="sect2"><h3 id="common-configuration-options">Common Configuration Options</h3><p>Most SolrJ configuration happens at the <code>SolrClient</code> level. The most common/important of these are discussed below. For comprehensive information on how to tweak your <code>SolrClient</code>, see the Javadocs for the involved client, and its corresponding builder object.</p>
<section class="sect3"><h4 id="base-urls">Base URLs</h4><p>Most <code>SolrClient</code> implementations (except for <code>CloudSolrClient</code> and <code>Http2SolrClient</code>) require users to specify one or more Solr base URLs, which the client then uses to send HTTP requests to Solr. The path users include on the base URL they provide has an effect on the behavior of the created client from that point on.</p>
<div class="olist arabic"><ol class="arabic"><li>A URL with a path pointing to a specific core or collection (e.g., <code>http://hostname:8983/solr/core1</code>). When a core or collection is specified in the base URL, subsequent requests made with that client are not required to re-specify the affected collection. However, the client is limited to sending requests to that core/collection, and can not send requests to any others.</li><li>A URL pointing to the root Solr path (e.g., <code>http://hostname:8983/solr</code>). When no core or collection is specified in the base URL, requests can be made to any core/collection, but the affected core/collection must be specified on all requests.</li></ol></div>
@@ -1843,7 +1838,7 @@ The indexing examples above are intended
<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>