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 [26/28] - in
/websites/production/lucene/content/solr/guide/8_6: ./ meta-docs/
Modified: websites/production/lucene/content/solr/guide/8_6/the-extended-dismax-query-parser.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-extended-dismax-query-parser.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-extended-dismax-query-parser.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Extended DisMax (eDismax) Query Parser | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Extended DisMax (eDismax) Query Parser | 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="the-extended-dismax-query-parser">
+<body class="" id="the-extended-dismax-query-parser">
<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,9 +1665,9 @@
<section class="content">
<section id="preamble" aria-label="Preamble"><p>The Extended DisMax (eDisMax) query parser is an improved version of the <a href="the-dismax-query-parser.html#the-dismax-query-parser">DisMax query parser</a>.</p>
<p>In addition to supporting all the DisMax query parser parameters, Extended Dismax:</p>
-<div class="ulist"><ul><li>supports <a href="the-standard-query-parser.html#the-standard-query-parser">Solr’s standard query parser</a> syntax such as (non-exhaustive list):<ul><li>boolean operators such as AND (+, &&), OR (||), NOT (-).</li><li>optionally treats lowercase "and" and "or" as "AND" and "OR" in Lucene syntax mode</li><li>optionally allows embedded queries using other query parsers or functions</li></ul></li><li>includes improved smart partial escaping in the case of syntax errors; fielded queries, +/-, and phrase queries are still supported in this mode.</li><li>improves proximity boosting by using word shingles; you do not need the query to match all words in the document before proximity boosting is applied.</li><li>includes advanced stopword handling: stopwords are not required in the mandatory part of the query but are still used in the proximity boosting part. If a query consists of all stopwords, such as "to be or not to be", then all words are requ
ired.</li><li>includes improved boost function: in Extended DisMax, the <code>boost</code> function is a multiplier <a href="the-dismax-query-parser.html#bq-bf-shortcomings">rather than an addend</a>, improving your boost results; the additive boost functions of DisMax (<code>bf</code> and <code>bq</code>) are also supported.</li><li>supports pure negative nested queries: queries such as <code>+foo (-foo)</code> will match all documents.</li><li>lets you specify which fields the end user is allowed to query, and to disallow direct fielded searches.</li></ul></div></section>
+<div class="ulist"><ul><li><p>supports <a href="the-standard-query-parser.html#the-standard-query-parser">Solr’s standard query parser</a> syntax such as (non-exhaustive list):<ul><li><p>boolean operators such as AND (+, &&), OR (||), NOT (-).</p></li><li><p>optionally treats lowercase "and" and "or" as "AND" and "OR" in Lucene syntax mode</p></li><li><p>optionally allows embedded queries using other query parsers or functions</p></li></ul></p></li><li><p>includes improved smart partial escaping in the case of syntax errors; fielded queries, +/-, and phrase queries are still supported in this mode.</p></li><li><p>improves proximity boosting by using word shingles; you do not need the query to match all words in the document before proximity boosting is applied.</p></li><li><p>includes advanced stopword handling: stopwords are not required in the mandatory part of the query but are still used in the proximity boosting part. If a query consists of all stopwords, such as
"to be or not to be", then all words are required.</p></li><li><p>includes improved boost function: in Extended DisMax, the <code>boost</code> function is a multiplier <a href="the-dismax-query-parser.html#bq-bf-shortcomings">rather than an addend</a>, improving your boost results; the additive boost functions of DisMax (<code>bf</code> and <code>bq</code>) are also supported.</p></li><li><p>supports pure negative nested queries: queries such as <code>+foo (-foo)</code> will match all documents.</p></li><li><p>lets you specify which fields the end user is allowed to query, and to disallow direct fielded searches.</p></li></ul></div></section>
<section class="sect1"><h2 id="extended-dismax-parameters">Extended DisMax Parameters</h2><p>In addition to all the <a href="the-dismax-query-parser.html#dismax-query-parser-parameters">DisMax parameters</a>, Extended DisMax includes these query parameters:</p>
-<div class="dlist"><dl><dt><code>sow</code></dt><dd>Split on whitespace. If set to <code>true</code>, text analysis is invoked separately for each individual whitespace-separated term. The default is <code>false</code>; whitespace-separated term sequences will be provided to text analysis in one shot, enabling proper function of analysis filters that operate over term sequences, e.g., multi-word synonyms and shingles.</dd><dt><code>mm</code></dt><dd>Minimum should match. See the <a href="the-dismax-query-parser.html#mm-minimum-should-match-parameter">DisMax mm parameter</a> for a description of <code>mm</code>. The default eDisMax <code>mm</code> value differs from that of DisMax:<ul><li>The default <code>mm</code> value is 0%:<ul><li>if the query contains an explicit operator other than "AND" ("-", "+", "OR", "NOT"); or</li><li>if <code>q.op</code> is "OR" or is not specified.</li></ul></li><li>The default <code>mm</code> value is 100% if <code>q.op</code> is "AND" and the query
does not contain any explicit operators other than "AND".</li></ul></dd><dt><code>mm.autoRelax</code></dt><dd><p>If <code>true</code>, the number of clauses required (<a href="the-dismax-query-parser.html#mm-minimum-should-match-parameter">minimum should match</a>) will automatically be relaxed if a clause is removed (by e.g., stopwords filter) from some but not all <a href="the-dismax-query-parser.html#qf-query-fields-parameter"><code>qf</code></a> fields. Use this parameter as a workaround if you experience that queries return zero hits due to uneven stopword removal between the <code>qf</code> fields.</p><p>Note that relaxing <code>mm</code> may cause undesired side effects, such as hurting the precision of the search, depending on the nature of your index content.</p></dd><dt><code>boost</code></dt><dd>A multivalued list of strings parsed as <a href="function-queries.html#available-functions">functions</a> whose results will be multiplied into the score from the main query for a
ll matching documents. This parameter is shorthand for wrapping the query produced by eDisMax using the <a href="other-parsers.html#boost-query-parser"><code>BoostQParserPlugin</code></a>.</dd></dl></div>
+<div class="dlist"><dl><dt><code>sow</code></dt><dd>Split on whitespace. If set to <code>true</code>, text analysis is invoked separately for each individual whitespace-separated term. The default is <code>false</code>; whitespace-separated term sequences will be provided to text analysis in one shot, enabling proper function of analysis filters that operate over term sequences, e.g., multi-word synonyms and shingles.</dd><dt><code>mm</code></dt><dd>Minimum should match. See the <a href="the-dismax-query-parser.html#mm-minimum-should-match-parameter">DisMax mm parameter</a> for a description of <code>mm</code>. The default eDisMax <code>mm</code> value differs from that of DisMax:<ul><li><p>The default <code>mm</code> value is 0%:<ul><li><p>if the query contains an explicit operator other than "AND" ("-", "+", "OR", "NOT"); or</p></li><li><p>if <code>q.op</code> is "OR" or is not specified.</p></li></ul></p></li><li><p>The default <code>mm</code> value is 100% if <code>q.op</code>
is "AND" and the query does not contain any explicit operators other than "AND".</p></li></ul></dd><dt><code>mm.autoRelax</code></dt><dd><p>If <code>true</code>, the number of clauses required (<a href="the-dismax-query-parser.html#mm-minimum-should-match-parameter">minimum should match</a>) will automatically be relaxed if a clause is removed (by e.g., stopwords filter) from some but not all <a href="the-dismax-query-parser.html#qf-query-fields-parameter"><code>qf</code></a> fields. Use this parameter as a workaround if you experience that queries return zero hits due to uneven stopword removal between the <code>qf</code> fields.</p><p>Note that relaxing <code>mm</code> may cause undesired side effects, such as hurting the precision of the search, depending on the nature of your index content.</p></dd><dt><code>boost</code></dt><dd>A multivalued list of strings parsed as <a href="function-queries.html#available-functions">functions</a> whose results will be multiplied into the sco
re from the main query for all matching documents. This parameter is shorthand for wrapping the query produced by eDisMax using the <a href="other-parsers.html#boost-query-parser"><code>BoostQParserPlugin</code></a>.</dd></dl></div>
<p>These two examples are equivalent:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-text" data-lang="text"><pre class="highlight"><code>q={!edismax qf=name}ipod
boost=div(1,sum(1,price))</code></pre></code></pre></div>
@@ -1681,8 +1676,8 @@ qq={!edismax qf=name}ipod</code></pre></
<div class="dlist"><dl><dt><code>lowercaseOperators</code></dt><dd>A Boolean parameter indicating if lowercase "and" and "or" should be treated the same as operators "AND" and "OR".
Defaults to <code>false</code>.</dd><dt><code>ps</code></dt><dd>Phrase Slop. The default amount of slop - distance between terms - on phrase queries built with <code>pf</code>, <code>pf2</code> and/or <code>pf3</code> fields (affects boosting). See also the section <a href="#using-slop">Using 'Slop'</a> below.</dd><dt><code>pf2</code></dt><dd>A multivalued list of fields with optional weights. Similar to <code>pf</code>, but based on word <em>pair</em> shingles.</dd><dt><code>ps2</code></dt><dd>This is similar to <code>ps</code> but overrides the slop factor used for <code>pf2</code>. If not specified, <code>ps</code> is used.</dd><dt><code>pf3</code></dt><dd>A multivalued list of fields with optional weights, based on triplets of word shingles. Similar to <code>pf</code>, except that instead of building a phrase per field out of all the words in the input, it builds a set of phrases for each field out of word <em>triplet</em> shingles.</dd><dt><code>ps3</code></dt><dd>This is simil
ar to <code>ps</code> but overrides the slop factor used for <code>pf3</code>. If not specified, <code>ps</code> is used.</dd><dt><code>stopwords</code></dt><dd>A Boolean parameter indicating if the <code>StopFilterFactory</code> configured in the query analyzer should be respected when parsing the query. If this is set to <code>false</code>, then the <code>StopFilterFactory</code> in the query analyzer is ignored.</dd><dt><code>uf</code></dt><dd><p>Specifies which schema fields the end user is allowed to explicitly query and to toggle whether embedded Solr queries are supported.
This parameter supports wildcards. Multiple fields must be separated by a space.</p><p>The default is to allow all fields and no embedded Solr queries, equivalent to <code>uf=* -_query_</code>.</p>
-<ul><li>To allow only title field, use <code>uf=title</code>.</li><li>To allow title and all fields ending with '_s', use <code>uf=title *_s</code>.</li><li>To allow all fields except title, use <code>uf=* -title</code>.</li><li>To disallow all fielded searches, use <code>uf=-*</code>.</li><li>To allow embedded Solr queries (e.g., <code>_query_:"…​"</code> or <code>_val_:"…​"</code> or <code>{!lucene …​}</code>),
-you <em>must</em> expressly enable this by referring to the magic field <code>_query_</code> in <code>uf</code>.</li></ul></dd></dl></div>
+<ul><li><p>To allow only title field, use <code>uf=title</code>.</p></li><li><p>To allow title and all fields ending with '_s', use <code>uf=title *_s</code>.</p></li><li><p>To allow all fields except title, use <code>uf=* -title</code>.</p></li><li><p>To disallow all fielded searches, use <code>uf=-*</code>.</p></li><li><p>To allow embedded Solr queries (e.g., <code>_query_:"…​"</code> or <code>_val_:"…​"</code> or <code>{!lucene …​}</code>),
+you <em>must</em> expressly enable this by referring to the magic field <code>_query_</code> in <code>uf</code>.</p></li></ul></dd></dl></div>
<section class="sect2"><h3 id="field-aliasing-using-per-field-qf-overrides">Field Aliasing using Per-Field qf Overrides</h3><p>Per-field overrides of the <code>qf</code> parameter may be specified to provide 1-to-many aliasing from field names specified in the query string, to field names used in the underlying query. By default, no aliasing is used and field names specified in the query string are treated as literal field names in the index.</p></section></section>
<section class="sect1"><h2 id="examples-of-edismax-queries">Examples of eDismax Queries</h2><p>All of the sample URLs in this section assume you are running Solr’s “<code>techproducts</code>” example:</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-bash" data-lang="bash"><pre class="highlight"><code>bin/solr -e techproducts</code></pre></code></pre></div>
@@ -1724,7 +1719,7 @@ defType=dismax</code></pre></code></pre>
<p>A document that contains "Hans Anderson" will match, but a document that contains the middle name "Christian" or where the name is written with the last name first ("Anderson, Hans") won’t. For those cases one could configure the query field <code>qs</code>, so that even if the user searches for an explicit phrase query, a slop is applied.</p>
<p>Finally, in addition to the phrase fields (<code>pf</code>) parameter, <code>edismax</code> also supports the <code>pf2</code> and <code>pf3</code> parameters, for fields over which to create bigram and trigram phrase queries. The phrase slop for these parameters' queries can be specified using the <code>ps2</code> and <code>ps3</code> parameters, respectively. If you use <code>pf2</code>/<code>pf3</code> but not <code>ps2</code>/<code>ps3</code>, then the phrase slop for these parameters' queries will be taken from the <code>ps</code> parameter, if any.</p>
<section class="sect2"><h3 id="synonyms-expansion-in-phrase-queries-with-slop">Synonyms Expansion in Phrase Queries with Slop</h3><p>When a phrase query with slop (e.g., <code>pf</code> with <code>ps</code>) triggers synonym expansions, a separate clause will be generated for each combination of synonyms. For example, with configured synonyms <code>dog,canine</code> and <code>cat,feline</code>, the query <code>"dog chased cat"</code> will generate the following phrase query clauses:</p>
-<div class="ulist"><ul><li><code>"dog chased cat"</code></li><li><code>"canine chased cat"</code></li><li><code>"dog chased feline"</code></li><li><code>"canine chased feline"</code></li></ul></div></section></section>
+<div class="ulist"><ul><li><p><code>"dog chased cat"</code></p></li><li><p><code>"canine chased cat"</code></p></li><li><p><code>"dog chased feline"</code></p></li><li><p><code>"canine chased feline"</code></p></li></ul></div></section></section>
</section>
@@ -1754,7 +1749,7 @@ defType=dismax</code></pre></code></pre>
<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/the-query-elevation-component.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-query-elevation-component.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-query-elevation-component.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Query Elevation Component | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Query Elevation Component | 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="the-query-elevation-component">
+<body class="" id="the-query-elevation-component">
<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-->
@@ -1771,7 +1766,7 @@ Subset matching is scalable, one can add
<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/the-standard-query-parser.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-standard-query-parser.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-standard-query-parser.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Standard Query Parser | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Standard Query Parser | 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="the-standard-query-parser">
+<body class="" id="the-standard-query-parser">
<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-->
@@ -1736,7 +1731,7 @@
<span style="color: #000080"></result></span>
<span style="color: #000080"></response></span></code></pre></code></pre></div></section></section>
<section class="sect1"><h2 id="specifying-terms-for-the-standard-query-parser">Specifying Terms for the Standard Query Parser</h2><p>A query to the standard query parser is broken up into terms and operators. There are two types of terms: single terms and phrases.</p>
-<div class="ulist"><ul><li>A single term is a single word such as "test" or "hello"</li><li>A phrase is a group of words surrounded by double quotes such as "hello dolly"</li></ul></div>
+<div class="ulist"><ul><li><p>A single term is a single word such as "test" or "hello"</p></li><li><p>A phrase is a group of words surrounded by double quotes such as "hello dolly"</p></li></ul></div>
<p>Multiple terms can be combined together with Boolean operators to form more complex queries (as described below).</p>
<div class="admonitionblock important">
<table>
@@ -1785,10 +1780,10 @@ To query for a field existing, simply us
<p><code>title:{Aida TO Carmen}</code></p>
<p>This will find all documents whose titles are between Aida and Carmen, but not including Aida and Carmen.</p>
<p>The brackets around a query determine its inclusiveness.</p>
-<div class="ulist"><ul><li>Square brackets <code>[</code> & <code>]</code> denote an inclusive range query that matches values including the upper and lower bound.</li><li>Curly brackets <code>{</code> & <code>}</code> denote an exclusive range query that matches values between the upper and lower bounds, but excluding the upper and lower bounds themselves.</li><li>You can mix these types so one end of the range is inclusive and the other is exclusive. Here’s an example: <code>count:{1 TO 10]</code></li></ul></div>
+<div class="ulist"><ul><li><p>Square brackets <code>[</code> & <code>]</code> denote an inclusive range query that matches values including the upper and lower bound.</p></li><li><p>Curly brackets <code>{</code> & <code>}</code> denote an exclusive range query that matches values between the upper and lower bounds, but excluding the upper and lower bounds themselves.</p></li><li><p>You can mix these types so one end of the range is inclusive and the other is exclusive. Here’s an example: <code>count:{1 TO 10]</code></p></li></ul></div>
<p>Wildcards, <code>*</code>, can also be used for either or both endpoints to specify an open-ended range query.
This is a <a href="#differences-between-lucenes-classic-query-parser-and-solrs-standard-query-parser">divergence from Lucene’s Classic Query Parser</a>.</p>
-<div class="ulist"><ul><li><code>field:[* TO 100]</code> finds all field values less than or equal to 100.</li><li><code>field:[100 TO *]</code> finds all field values greater than or equal to 100.</li><li><code>field:[* TO *]</code> finds any document with a value between the effective values of -Infinity and +Infinity for that field type.</li></ul></div>
+<div class="ulist"><ul><li><p><code>field:[* TO 100]</code> finds all field values less than or equal to 100.</p></li><li><p><code>field:[100 TO *]</code> finds all field values greater than or equal to 100.</p></li><li><p><code>field:[* TO *]</code> finds any document with a value between the effective values of -Infinity and +Infinity for that field type.</p></li></ul></div>
<div class="admonitionblock note">
<table>
<tr>
@@ -1799,7 +1794,7 @@ This is a <a href="#differences-between-
<div class="title">Matching <code>NaN</code> values with wildcards</div>
<p>For most fields, unbounded range queries, <code>field:[* TO *]</code>, are equivalent to existence queries, <code>field: *</code> .
However for float/double types that support <code>NaN</code> values, these two queries perform differently.</p>
-<div class="ulist"><ul><li><code>field:*</code> matches all existing values, including <code>NaN</code></li><li><code>field:[* TO *]</code> matches all real values, excluding <code>NaN</code></li></ul></div>
+<div class="ulist"><ul><li><p><code>field:*</code> matches all existing values, including <code>NaN</code></p></li><li><p><code>field:[* TO *]</code> matches all real values, excluding <code>NaN</code></p></li></ul></div>
</td>
</tr>
</table>
@@ -1895,13 +1890,13 @@ This operator is supported by both the s
<p><code>"jakarta apache" /* this is a comment in the middle of a normal query string */ OR jakarta</code></p>
<p>Comments may be nested.</p></section>
<section class="sect1"><h2 id="differences-between-lucenes-classic-query-parser-and-solrs-standard-query-parser">Differences between Lucene’s Classic Query Parser and Solr’s Standard Query Parser</h2><p>Solr’s standard query parser originated as a variation of Lucene’s "classic" QueryParser. It diverges in the following ways:</p>
-<div class="ulist"><ul><li>A <code>*</code> may be used for either or both endpoints to specify an open-ended range query, or by itself as an existence query.<ul><li><code>field:[* TO 100]</code> finds all field values less than or equal to 100</li><li><code>field:[100 TO *]</code> finds all field values greater than or equal to 100</li><li><code>field:[* TO *]</code> finds all documents where the field has a value between <code>-Infinity</code> and <code>Infinity</code>, excluding <code>NaN</code>.</li><li><code>field:*</code> finds all documents where the field exists (i.e., has any value).</li></ul></li><li>Pure negative queries (all clauses prohibited) are allowed (only as a top-level clause)<ul><li><code>-inStock:false</code> finds all field values where inStock is not false</li><li><code>-field:*</code> finds all documents without a value for the field.</li></ul></li><li>Support for embedded Solr queries (sub-queries) using any type of query parser as a nested clause using the
local-params syntax.<ul><li><p><code>inStock:true OR {!dismax qf='name manu' v='ipod'}</code></p><p>Gotcha: Be careful not to start your query with <code>{!</code> at the very beginning, which changes the parsing of the entire
+<div class="ulist"><ul><li><p>A <code>*</code> may be used for either or both endpoints to specify an open-ended range query, or by itself as an existence query.<ul><li><p><code>field:[* TO 100]</code> finds all field values less than or equal to 100</p></li><li><p><code>field:[100 TO *]</code> finds all field values greater than or equal to 100</p></li><li><p><code>field:[* TO *]</code> finds all documents where the field has a value between <code>-Infinity</code> and <code>Infinity</code>, excluding <code>NaN</code>.</p></li><li><p><code>field:*</code> finds all documents where the field exists (i.e., has any value).</p></li></ul></p></li><li><p>Pure negative queries (all clauses prohibited) are allowed (only as a top-level clause)<ul><li><p><code>-inStock:false</code> finds all field values where inStock is not false</p></li><li><p><code>-field:*</code> finds all documents without a value for the field.</p></li></ul></p></li><li><p>Support for embedded Solr queries (sub-queries)
using any type of query parser as a nested clause using the local-params syntax.<ul><li><p><p><code>inStock:true OR {!dismax qf='name manu' v='ipod'}</code></p><p>Gotcha: Be careful not to start your query with <code>{!</code> at the very beginning, which changes the parsing of the entire
query string, which may not be what you want if there are additional clauses. So flipping the example above so the
sub-query comes first would fail to work as expected without a leading space.</p>
<p>Sub-queries can also be done with the magic field <code>_query_</code> and for function queries with the magic field <code>_val_</code> but it
-should be considered deprecated since it is less clear. Example: <code>_val_:"recip(rord(myfield),1,2,3)"</code></p></li></ul></li><li>Support for a special <code>filter(…​)</code> syntax to indicate that some query clauses should be cached in the filter cache (as a constant score boolean query). This allows sub-queries to be cached and re-used in other queries. For example <code>inStock:true</code> will be cached and re-used in all three of the queries below:<ul><li><code>q=features:songs OR filter(inStock:true)</code></li><li><code>q=+manu:Apple +filter(inStock:true)</code></li><li><p><code>q=+manu:Apple & fq=inStock:true</code></p><p>This can even be used to cache individual clauses of complex filter queries. In the first query below, 3 items will be added to the filter cache (the top level <code>fq</code> and both <code>filter(…​)</code> clauses) and in the second query, there will be 2 cache hits, and one new cache insertion (for the new top level <
code>fq</code>):</p></li><li><code>q=features:songs & fq=+filter(inStock:true) +filter(price:[* TO 100])</code></li><li><code>q=manu:Apple & fq=-filter(inStock:true) -filter(price:[* TO 100])</code></li></ul></li><li>Range queries ("[a TO z]"), prefix queries ("a*"), and wildcard queries ("a*b") are constant-scoring (all matching documents get an equal score). The scoring factors TF, IDF, index boost, and "coord" are not used. There is no limitation on the number of terms that match (as there was in past versions of Lucene).</li><li>Constant score queries are created with <code><query_clause>^=<score></code>, which sets the entire clause to the specified score for any documents matching that clause:<ul><li><code>q=(description:blue color:blue)^=1.0 title:blue^=5.0</code></li></ul></li></ul></div>
+should be considered deprecated since it is less clear. Example: <code>_val_:"recip(rord(myfield),1,2,3)"</code></p></p></li></ul></p></li><li><p>Support for a special <code>filter(…​)</code> syntax to indicate that some query clauses should be cached in the filter cache (as a constant score boolean query). This allows sub-queries to be cached and re-used in other queries. For example <code>inStock:true</code> will be cached and re-used in all three of the queries below:<ul><li><p><code>q=features:songs OR filter(inStock:true)</code></p></li><li><p><code>q=+manu:Apple +filter(inStock:true)</code></p></li><li><p><p><code>q=+manu:Apple & fq=inStock:true</code></p><p>This can even be used to cache individual clauses of complex filter queries. In the first query below, 3 items will be added to the filter cache (the top level <code>fq</code> and both <code>filter(…​)</code> clauses) and in the second query, there will be 2 cache hits, and one new cache insert
ion (for the new top level <code>fq</code>):</p></p></li><li><p><code>q=features:songs & fq=+filter(inStock:true) +filter(price:[* TO 100])</code></p></li><li><p><code>q=manu:Apple & fq=-filter(inStock:true) -filter(price:[* TO 100])</code></p></li></ul></p></li><li><p>Range queries ("[a TO z]"), prefix queries ("a*"), and wildcard queries ("a*b") are constant-scoring (all matching documents get an equal score). The scoring factors TF, IDF, index boost, and "coord" are not used. There is no limitation on the number of terms that match (as there was in past versions of Lucene).</p></li><li><p>Constant score queries are created with <code><query_clause>^=<score></code>, which sets the entire clause to the specified score for any documents matching that clause:<ul><li><p><code>q=(description:blue color:blue)^=1.0 title:blue^=5.0</code></p></li></ul></p></li></ul></div>
<section class="sect2"><h3 id="specifying-dates-and-times">Specifying Dates and Times</h3><p>Queries against date based fields must use the <a href="working-with-dates.html#working-with-dates">appropriate date formating</a>. Queries for exact date values will require quoting or escaping since <code>:</code> is the parser syntax used to denote a field query:</p>
-<div class="ulist"><ul><li><code>createdate:1976-03-06T23\:59\:59.999Z</code></li><li><code>createdate:"1976-03-06T23:59:59.999Z"</code></li><li><code>createdate:[1976-03-06T23:59:59.999Z TO *]</code></li><li><code>createdate:[1995-12-31T23:59:59.999Z TO 2007-03-06T00:00:00Z]</code></li><li><code>timestamp:[* TO NOW]</code></li><li><code>pubdate:[NOW-1YEAR/DAY TO NOW/DAY+1DAY]</code></li><li><code>createdate:[1976-03-06T23:59:59.999Z TO 1976-03-06T23:59:59.999Z+1YEAR]</code></li><li><code>createdate:[1976-03-06T23:59:59.999Z/YEAR TO 1976-03-06T23:59:59.999Z]</code></li></ul></div></section></section>
+<div class="ulist"><ul><li><p><code>createdate:1976-03-06T23\:59\:59.999Z</code></p></li><li><p><code>createdate:"1976-03-06T23:59:59.999Z"</code></p></li><li><p><code>createdate:[1976-03-06T23:59:59.999Z TO *]</code></p></li><li><p><code>createdate:[1995-12-31T23:59:59.999Z TO 2007-03-06T00:00:00Z]</code></p></li><li><p><code>timestamp:[* TO NOW]</code></p></li><li><p><code>pubdate:[NOW-1YEAR/DAY TO NOW/DAY+1DAY]</code></p></li><li><p><code>createdate:[1976-03-06T23:59:59.999Z TO 1976-03-06T23:59:59.999Z+1YEAR]</code></p></li><li><p><code>createdate:[1976-03-06T23:59:59.999Z/YEAR TO 1976-03-06T23:59:59.999Z]</code></p></li></ul></div></section></section>
</section>
@@ -1931,7 +1926,7 @@ should be considered deprecated since it
<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/the-stats-component.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-stats-component.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-stats-component.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Stats Component | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Stats Component | 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="the-stats-component">
+<body class="" id="the-stats-component">
<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-->
@@ -1717,7 +1712,7 @@
<div class="dlist"><dl><dt><code>min</code></dt><dd>The minimum value of the field/function in all documents in the set. This statistic is computed for all field types and is computed by default.</dd><dt><code>max</code></dt><dd>The maximum value of the field/function in all documents in the set. This statistic is computed for all field types and is computed by default.</dd><dt><code>sum</code></dt><dd>The sum of all values of the field/function in all documents in the set. This statistic is computed for numeric and date field types and is computed by default.</dd><dt><code>count</code></dt><dd>The number of values found in all documents in the set for this field/function. This statistic is computed for all field types and is computed by default.</dd><dt><code>missing</code></dt><dd>The number of documents in the set which do not have a value for this field/function. This statistic is computed for all field types and is computed by default.</dd><dt><code>sumOfSquares</code></dt><dd>
Sum of all values squared (a by product of computing stddev). This statistic is computed for numeric and date field types and is computed by default.</dd><dt><code>mean</code></dt><dd>The average <code>(v1 + v2 …​. + vN)/N</code>. This statistic is computed for numeric and date field types and is computed by default.</dd><dt><code>stddev</code></dt><dd>Standard deviation, measuring how widely spread the values in the data set are. This statistic is computed for numeric and date field types and is computed by default.</dd><dt><code>percentiles</code></dt><dd>A list of percentile values based on cut-off points specified by the parameter value, such as <code>1,99,99.9</code>. These values are an approximation, using the <a href="https://github.com/tdunning/t-digest/blob/master/docs/t-digest-paper/histo.pdf">t-digest algorithm</a>. This statistic is computed for numeric field types and is not computed by default.</dd><dt><code>distinctValues</code></dt><dd>The set of all dis
tinct values for the field/function in all of the documents in the set. This calculation can be very expensive for fields that do not have a tiny cardinality. This statistic is computed for all field types but is not computed by default.</dd><dt><code>countDistinct</code></dt><dd>The exact number of distinct values in the field/function in all of the documents in the set. This calculation can be very expensive for fields that do not have a tiny cardinality. This statistic is computed for all field types but is not computed by default.</dd><dt><code>cardinality</code></dt><dd><p>A statistical approximation (currently using the <a href="https://en.wikipedia.org/wiki/HyperLogLog">HyperLogLog</a> algorithm) of the number of distinct values in the field/function in all of the documents in the set. This calculation is much more efficient then using the <code>countDistinct</code> option, but may not be 100% accurate.</p><p>Input for this option can be floating point number between <code>0.
0</code> and <code>1.0</code> indicating how aggressively the algorithm should try to be accurate: <code>0.0</code> means use as little memory as possible; <code>1.0</code> means use as much memory as needed to be as accurate as possible. <code>true</code> is supported as an alias for <code>0.3</code>.</p>
<p>This statistic is computed for all field types but is not computed by default.</p></dd></dl></div></section>
<section class="sect1"><h2 id="local-parameters-with-the-stats-component">Local Parameters with the Stats Component</h2><p>Similar to the <a href="faceting.html#faceting">Facet Component</a>, the <code>stats.field</code> parameter supports local parameters for:</p>
-<div class="ulist"><ul><li>Tagging & Excluding Filters: <code>stats.field={!ex=filterA}price</code></li><li>Changing the Output Key: <code>stats.field={!key=my_price_stats}price</code></li><li>Tagging stats for <a href="#the-stats-component-and-faceting">use with <code>facet.pivot</code></a>: <code>stats.field={!tag=my_pivot_stats}price</code></li></ul></div>
+<div class="ulist"><ul><li><p>Tagging & Excluding Filters: <code>stats.field={!ex=filterA}price</code></p></li><li><p>Changing the Output Key: <code>stats.field={!key=my_price_stats}price</code></p></li><li><p>Tagging stats for <a href="#the-stats-component-and-faceting">use with <code>facet.pivot</code></a>: <code>stats.field={!tag=my_pivot_stats}price</code></p></li></ul></div>
<p>Local parameters can also be used to specify individual statistics by name, overriding the set of statistics computed by default, e.g., <code>stats.field={!min=true max=true percentiles='99,99.9,99.99'}price</code>.</p>
<div class="admonitionblock important">
<table>
@@ -1732,7 +1727,7 @@
</table>
</div>
<p>Additional "Expert" local params are supported in some cases for affecting the behavior of some statistics:</p>
-<div class="ulist"><ul><li><code>percentiles</code><ul><li><code>tdigestCompression</code> - a positive numeric value defaulting to <code>100.0</code> controlling the compression factor of the T-Digest. Larger values means more accuracy, but also uses more memory.</li></ul></li><li><code>cardinality</code><ul><li><code>hllPreHashed</code> - a boolean option indicating that the statistics are being computed over a "long" field that has already been hashed at index time â allowing the HLL computation to skip this step.</li><li><code>hllLog2m</code> - an integer value specifying an explicit "log2m" value to use, overriding the heuristic value determined by the cardinality local param and the field type â see the <a href="https://github.com/aggregateknowledge/java-hll/">java-hll</a> documentation for more details</li><li><code>hllRegwidth</code> - an integer value specifying an explicit "regwidth" value to use, overriding the heuristic value determined by the cardinality local
param and the field type â see the <a href="https://github.com/aggregateknowledge/java-hll/">java-hll</a> documentation for more details</li></ul></li></ul></div>
+<div class="ulist"><ul><li><p><code>percentiles</code><ul><li><p><code>tdigestCompression</code> - a positive numeric value defaulting to <code>100.0</code> controlling the compression factor of the T-Digest. Larger values means more accuracy, but also uses more memory.</p></li></ul></p></li><li><p><code>cardinality</code><ul><li><p><code>hllPreHashed</code> - a boolean option indicating that the statistics are being computed over a "long" field that has already been hashed at index time â allowing the HLL computation to skip this step.</p></li><li><p><code>hllLog2m</code> - an integer value specifying an explicit "log2m" value to use, overriding the heuristic value determined by the cardinality local param and the field type â see the <a href="https://github.com/aggregateknowledge/java-hll/">java-hll</a> documentation for more details</p></li><li><p><code>hllRegwidth</code> - an integer value specifying an explicit "regwidth" value to use, overriding the heuristic value d
etermined by the cardinality local param and the field type â see the <a href="https://github.com/aggregateknowledge/java-hll/">java-hll</a> documentation for more details</p></li></ul></p></li></ul></div>
<section class="sect2"><h3 id="examples-with-local-parameters">Examples with Local Parameters</h3><p>Here we compute some statistics for the price field. The min, max, mean, 90th, and 99th percentile price values are computed against all products that are in stock (<code>q=<strong>:</strong></code> and <code>fq=inStock:true</code>), and independently all of the default statistics are computed against all products regardless of whether they are in stock or not (by excluding that filter).</p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-text" data-lang="text"><pre class="highlight"><code>http://localhost:8983/solr/techproducts/select?q=*:*&fq={!tag=stock_check}inStock:true&stats=true&stats.field={!ex=stock_check+key=instock_prices+min=true+max=true+mean=true+percentiles='90,99'}price&stats.field={!key=all_prices}price&rows=0&indent=true&wt=xml</code></pre></code></pre></div>
<div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><lst</span> <span style="color: #008080">name=</span><span style="color: #d14">"stats"</span><span style="color: #000080">></span>
@@ -1789,7 +1784,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/the-tagger-handler.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-tagger-handler.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-tagger-handler.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Tagger Handler | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Tagger 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="the-tagger-handler">
+<body class="" id="the-tagger-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-->
@@ -1682,10 +1677,10 @@ stores the tag dictionary must be a sing
Despite this limitation, tens to hundreds of millions of names (documents) can
be supported; the maximum is mostly limited only by memory.</p></section>
<section class="sect1"><h2 id="tagger-configuration">Tagger Configuration</h2><p>To configure the tagger, your Solr schema needs 2 fields:</p>
-<div class="ulist"><ul><li>A unique key field (see <a href="other-schema-elements.html#unique-key">Unique Key</a> for how to define a unique key in your schema).
-Recommended field settings: set <code>docValues=true</code>.</li><li>A tag field, which must be a <code>TextField</code>, with <code>ConcatenateGraphFilterFactory</code> at the end of the index chain (not the query chain):
+<div class="ulist"><ul><li><p>A unique key field (see <a href="other-schema-elements.html#unique-key">Unique Key</a> for how to define a unique key in your schema).
+Recommended field settings: set <code>docValues=true</code>.</p></li><li><p>A tag field, which must be a <code>TextField</code>, with <code>ConcatenateGraphFilterFactory</code> at the end of the index chain (not the query chain):
Set <code>preservePositionIncrements=false</code> on that filter.
-Recommended field settings: <code>omitNorms=true</code>, <code>omitTermFreqAndPositions=true</code> and <em>maybe</em> specify the postings format — see <a href="#tagger-performance-tips">performance tips</a>.</li></ul></div>
+Recommended field settings: <code>omitNorms=true</code>, <code>omitTermFreqAndPositions=true</code> and <em>maybe</em> specify the postings format — see <a href="#tagger-performance-tips">performance tips</a>.</p></li></ul></div>
<p>The text field’s <em>index analysis chain</em>, aside from needing <code>ConcatenateGraphFilterFactory</code> at the end,
can otherwise have whatever tokenizer and filters suit your matching preferences.
It can have multi-word synonyms and use <code>WordDelimiterGraphFilterFactory</code> for example.
@@ -1704,9 +1699,9 @@ This is required; you’ll probably
This parameter is the same one used by the <code>solr.SearchHandler</code>.</dd><dt><code>rows</code></dt><dd>The maximum number of documents to return, but defaulting to 10000 for a tag request.
This parameter is the same as is used by the <code>solr.SearchHandler</code>.</dd><dt><code>fl</code></dt><dd>Solr’s standard parameter for listing the fields to return.
This parameter is the same one used by the <code>solr.SearchHandler</code>.</dd><dt><code>overlaps</code></dt><dd>Choose the algorithm to determine which tags in an overlapping set should be retained, versus being pruned away.
-Options are:<ul><li><code>ALL</code>: Emit all tags.</li><li><code>NO_SUB</code>: Don’t emit a tag that is completely within another tag (i.e., no subtag).</li><li><code>LONGEST_DOMINANT_RIGHT</code>: Given a cluster of overlapping tags, emit the longest one (by character length).
+Options are:<ul><li><p><code>ALL</code>: Emit all tags.</p></li><li><p><code>NO_SUB</code>: Don’t emit a tag that is completely within another tag (i.e., no subtag).</p></li><li><p><code>LONGEST_DOMINANT_RIGHT</code>: Given a cluster of overlapping tags, emit the longest one (by character length).
If there is a tie, pick the right-most.
-Remove any tags overlapping with this tag then repeat the algorithm to potentially find other tags that can be emitted in the cluster.</li></ul></dd><dt><code>matchText</code></dt><dd>A boolean indicating whether to return the matched text in the tag response.
+Remove any tags overlapping with this tag then repeat the algorithm to potentially find other tags that can be emitted in the cluster.</p></li></ul></dd><dt><code>matchText</code></dt><dd>A boolean indicating whether to return the matched text in the tag response.
This will trigger the tagger to fully buffer the input before tagging.</dd><dt><code>tagsLimit</code></dt><dd>The maximum number of tags to return in the response.
Tagging effectively stops after this point.
By default this is <code>1000</code>.</dd><dt><code>skipAltTokens</code></dt><dd>A boolean flag used to suppress errors that can occur if, for example,
@@ -1822,14 +1817,14 @@ options, see the earlier documentation.<
</span><span style="color: #000080">"name"</span><span style="background-color: #f8f8f8">:[</span><span style="color: #d14">"New York City"</span><span style="background-color: #f8f8f8">],</span><span style="color: #bbbbbb">
</span><span style="color: #000080">"countrycode"</span><span style="background-color: #f8f8f8">:[</span><span style="color: #d14">"US"</span><span style="background-color: #f8f8f8">]}]</span><span style="color: #bbbbbb">
</span><span style="background-color: #f8f8f8">}}</span></code></pre></code></pre></div></section></section>
-<section class="sect1"><h2 id="tagger-performance-tips">Tagger Performance Tips</h2><div class="ulist"><ul><li>Follow the recommended configuration field settings above.
+<section class="sect1"><h2 id="tagger-performance-tips">Tagger Performance Tips</h2><div class="ulist"><ul><li><p>Follow the recommended configuration field settings above.
Additionally, for the best tagger performance, set <code>postingsFormat=FST50</code>.
However, non-default postings formats have no backwards-compatibility guarantees, and so if you upgrade Solr then you may find a nasty exception on startup as it fails to read the older index.
-If the input text to be tagged is small (e.g., you are tagging queries or tweets) then the postings format choice isn’t as important.</li><li>"optimize" after loading your dictionary down to 1 Lucene segment, or at least to as few as possible.</li><li>For bulk tagging lots of documents, there are some strategies, not mutually exclusive:<ul><li>Batch them.
+If the input text to be tagged is small (e.g., you are tagging queries or tweets) then the postings format choice isn’t as important.</p></li><li><p>"optimize" after loading your dictionary down to 1 Lucene segment, or at least to as few as possible.</p></li><li><p>For bulk tagging lots of documents, there are some strategies, not mutually exclusive:<ul><li><p>Batch them.
The tagger doesn’t directly support batching but as a hack you can send a bunch of documents concatenated with
a nonsense word that is not in the dictionary like "ZZYYXXAABBCC" between them.
- You’ll need to keep track of the character offsets of these so you can subtract them from the results.</li><li>For reducing tagging latency even further, consider embedding Solr with <code>EmbeddedSolrServer</code>.
-See <code>EmbeddedSolrNoSerializeTest</code>.</li><li>Use more than one thread — perhaps as many as there are CPU cores available to Solr.</li></ul></li></ul></div></section>
+ You’ll need to keep track of the character offsets of these so you can subtract them from the results.</p></li><li><p>For reducing tagging latency even further, consider embedding Solr with <code>EmbeddedSolrServer</code>.
+See <code>EmbeddedSolrNoSerializeTest</code>.</p></li><li><p>Use more than one thread — perhaps as many as there are CPU cores available to Solr.</p></li></ul></p></li></ul></div></section>
</section>
@@ -1859,7 +1854,7 @@ See <code>EmbeddedSolrNoSerializeTest</c
<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/the-term-vector-component.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-term-vector-component.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-term-vector-component.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Term Vector Component | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Term Vector Component | 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="the-term-vector-component">
+<body class="" id="the-term-vector-component">
<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-->
@@ -1771,7 +1766,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/the-terms-component.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-terms-component.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-terms-component.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Terms Component | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Terms Component | 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="the-terms-component">
+<body class="" id="the-terms-component">
<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-->
@@ -1683,7 +1678,7 @@
<p>Note that the defaults for this request handler set the parameter "terms" to true, which allows terms to be returned on request. The parameter "distrib" is set to false, which allows this handler to be used only on a single Solr core.</p>
<p>You could add this component to another handler if you wanted to, and pass "terms=true" in the HTTP request in order to get terms back. If it is only defined in a separate handler, you must use that handler when querying in order to get terms and not regular documents as results.</p></section>
<section class="sect2"><h3 id="terms-component-parameters">Terms Component Parameters</h3><p>The parameters below allow you to control what terms are returned. You can also configure any of these with the request handler if you’d like to set them permanently. Or, you can add them to the query request. These parameters are:</p>
-<div class="dlist"><dl><dt><code>terms</code></dt><dd><p>If set to <code>true</code>, enables the Terms Component. By default, the Terms Component is off (<code>false</code>).</p><p>Example: <code>terms=true</code></p></dd><dt><code>terms.fl</code></dt><dd><p>Specifies the field from which to retrieve terms. This parameter is required if <code>terms=true</code>.</p><p>Example: <code>terms.fl=title</code></p></dd><dt><code>terms.list</code></dt><dd><p>Fetches the document frequency for a comma delimited list of terms. Terms are always returned in index order. If <code>terms.ttf</code> is set to true, also returns their total term frequency. If multiple <code>terms.fl</code> are defined, these statistics will be returned for each term in each requested field.</p><p>Example: <code>terms.list=termA,termB,termC</code></p></dd><dt><code>terms.limit</code></dt><dd><p>Specifies the maximum number of terms to return. The default is <code>10</code>. If the limit is set to a number less than 0
, then no maximum limit is enforced. Although this is not required, either this parameter or <code>terms.upper</code> must be defined.</p><p>Example: <code>terms.limit=20</code></p></dd><dt><code>terms.lower</code></dt><dd><p>Specifies the term at which to start. If not specified, the empty string is used, causing Solr to start at the beginning of the field.</p><p>Example: <code>terms.lower=orange</code></p></dd><dt><code>terms.lower.incl</code></dt><dd><p>If set to true, includes the lower-bound term (specified with <code>terms.lower</code> in the result set.</p><p>Example: <code>terms.lower.incl=false</code></p></dd><dt><code>terms.mincount</code></dt><dd><p>Specifies the minimum document frequency to return in order for a term to be included in a query response. Results are inclusive of the mincount (that is, >= mincount).</p><p>Example: <code>terms.mincount=5</code></p></dd><dt><code>terms.maxcount</code></dt><dd><p>Specifies the maximum document frequency a term must have in
order to be included in a query response. The default setting is -1, which sets no upper bound. Results are inclusive of the maxcount (that is, <= maxcount).</p><p>Example: <code>terms.maxcount=25</code></p></dd><dt><code>terms.prefix</code></dt><dd><p>Restricts matches to terms that begin with the specified string.</p><p>Example: <code>terms.prefix=inter</code></p></dd><dt><code>terms.raw</code></dt><dd><p>If set to true, returns the raw characters of the indexed term, regardless of whether it is human-readable. For instance, the indexed form of numeric numbers is not human-readable.</p><p>Example: <code>terms.raw=true</code></p></dd><dt><code>terms.regex</code></dt><dd><p>Restricts matches to terms that match the regular expression.</p><p>Example: <code>terms.regex=.*pedist</code></p></dd><dt><code>terms.regex.flag</code></dt><dd>Defines a Java regex flag to use when evaluating the regular expression defined with <code>terms.regex</code>. See <a class="bare" href="http://docs.
oracle.com/javase/tutorial/essential/regex/pattern.html">http://docs.oracle.com/javase/tutorial/essential/regex/pattern.html</a> for details of each flag. Valid options are:<ul><li><code>case_insensitive</code></li><li><code>comments</code></li><li><code>multiline</code></li><li><code>literal</code></li><li><code>dotall</code></li><li><code>unicode_case</code></li><li><code>canon_eq</code></li><li><p><code>unix_lines</code></p><p>Example: <code>terms.regex.flag=case_insensitive</code></p></li></ul></dd><dt><code>terms.stats</code></dt><dd>Include index statistics in the results. Currently returns only the <strong>numDocs</strong> for a collection. When combined with <code>terms.list</code> it provides enough information to compute inverse document frequency (IDF) for a list of terms.</dd><dt><code>terms.sort</code></dt><dd><p>Defines how to sort the terms returned. Valid options are <code>count</code>, which sorts by the term frequency, with the highest term frequency first, or <cod
e>index</code>, which sorts in index order.</p><p>Example: <code>terms.sort=index</code></p></dd><dt><code>terms.ttf</code></dt><dd><p>If set to true, returns both <code>df</code> (docFreq) and <code>ttf</code> (totalTermFreq) statistics for each requested term in <code>terms.list</code>. In this case, the response format is:</p><div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><lst</span> <span style="color: #008080">name=</span><span style="color: #d14">"terms"</span><span style="color: #000080">></span>
+<div class="dlist"><dl><dt><code>terms</code></dt><dd><p>If set to <code>true</code>, enables the Terms Component. By default, the Terms Component is off (<code>false</code>).</p><p>Example: <code>terms=true</code></p></dd><dt><code>terms.fl</code></dt><dd><p>Specifies the field from which to retrieve terms. This parameter is required if <code>terms=true</code>.</p><p>Example: <code>terms.fl=title</code></p></dd><dt><code>terms.list</code></dt><dd><p>Fetches the document frequency for a comma delimited list of terms. Terms are always returned in index order. If <code>terms.ttf</code> is set to true, also returns their total term frequency. If multiple <code>terms.fl</code> are defined, these statistics will be returned for each term in each requested field.</p><p>Example: <code>terms.list=termA,termB,termC</code></p></dd><dt><code>terms.limit</code></dt><dd><p>Specifies the maximum number of terms to return. The default is <code>10</code>. If the limit is set to a number less than 0
, then no maximum limit is enforced. Although this is not required, either this parameter or <code>terms.upper</code> must be defined.</p><p>Example: <code>terms.limit=20</code></p></dd><dt><code>terms.lower</code></dt><dd><p>Specifies the term at which to start. If not specified, the empty string is used, causing Solr to start at the beginning of the field.</p><p>Example: <code>terms.lower=orange</code></p></dd><dt><code>terms.lower.incl</code></dt><dd><p>If set to true, includes the lower-bound term (specified with <code>terms.lower</code> in the result set.</p><p>Example: <code>terms.lower.incl=false</code></p></dd><dt><code>terms.mincount</code></dt><dd><p>Specifies the minimum document frequency to return in order for a term to be included in a query response. Results are inclusive of the mincount (that is, >= mincount).</p><p>Example: <code>terms.mincount=5</code></p></dd><dt><code>terms.maxcount</code></dt><dd><p>Specifies the maximum document frequency a term must have in
order to be included in a query response. The default setting is -1, which sets no upper bound. Results are inclusive of the maxcount (that is, <= maxcount).</p><p>Example: <code>terms.maxcount=25</code></p></dd><dt><code>terms.prefix</code></dt><dd><p>Restricts matches to terms that begin with the specified string.</p><p>Example: <code>terms.prefix=inter</code></p></dd><dt><code>terms.raw</code></dt><dd><p>If set to true, returns the raw characters of the indexed term, regardless of whether it is human-readable. For instance, the indexed form of numeric numbers is not human-readable.</p><p>Example: <code>terms.raw=true</code></p></dd><dt><code>terms.regex</code></dt><dd><p>Restricts matches to terms that match the regular expression.</p><p>Example: <code>terms.regex=.*pedist</code></p></dd><dt><code>terms.regex.flag</code></dt><dd>Defines a Java regex flag to use when evaluating the regular expression defined with <code>terms.regex</code>. See <a class="bare" href="http://docs.
oracle.com/javase/tutorial/essential/regex/pattern.html">http://docs.oracle.com/javase/tutorial/essential/regex/pattern.html</a> for details of each flag. Valid options are:<ul><li><p><code>case_insensitive</code></p></li><li><p><code>comments</code></p></li><li><p><code>multiline</code></p></li><li><p><code>literal</code></p></li><li><p><code>dotall</code></p></li><li><p><code>unicode_case</code></p></li><li><p><code>canon_eq</code></p></li><li><p><p><code>unix_lines</code></p><p>Example: <code>terms.regex.flag=case_insensitive</code></p></p></li></ul></dd><dt><code>terms.stats</code></dt><dd>Include index statistics in the results. Currently returns only the <strong>numDocs</strong> for a collection. When combined with <code>terms.list</code> it provides enough information to compute inverse document frequency (IDF) for a list of terms.</dd><dt><code>terms.sort</code></dt><dd><p>Defines how to sort the terms returned. Valid options are <code>count</code>, which sorts by the term f
requency, with the highest term frequency first, or <code>index</code>, which sorts in index order.</p><p>Example: <code>terms.sort=index</code></p></dd><dt><code>terms.ttf</code></dt><dd><p>If set to true, returns both <code>df</code> (docFreq) and <code>ttf</code> (totalTermFreq) statistics for each requested term in <code>terms.list</code>. In this case, the response format is:</p><div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><lst</span> <span style="color: #008080">name=</span><span style="color: #d14">"terms"</span><span style="color: #000080">></span>
<span style="color: #000080"><lst</span> <span style="color: #008080">name=</span><span style="color: #d14">"field"</span><span style="color: #000080">></span>
<span style="color: #000080"><lst</span> <span style="color: #008080">name=</span><span style="color: #d14">"termA"</span><span style="color: #000080">></span>
<span style="color: #000080"><long</span> <span style="color: #008080">name=</span><span style="color: #d14">"df"</span><span style="color: #000080">></span>22<span style="color: #000080"></long></span>
@@ -1812,7 +1807,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/the-well-configured-solr-instance.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/the-well-configured-solr-instance.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/the-well-configured-solr-instance.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>The Well-Configured Solr Instance | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>The Well-Configured Solr Instance | 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="the-well-configured-solr-instance">
+<body class="" id="the-well-configured-solr-instance">
<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-->
@@ -1706,7 +1701,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/thread-dump.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/thread-dump.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/thread-dump.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Thread Dump | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Thread Dump | 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="thread-dump">
+<body class="" id="thread-dump">
<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/time-series.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/time-series.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/time-series.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Time Series | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Time Series | 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="time-series">
+<body class="" id="time-series">
<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-->
@@ -2015,7 +2010,7 @@ is possible to compute.</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/tokenizers.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/tokenizers.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/tokenizers.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Tokenizers | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Tokenizers | 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="tokenizers">
+<body class="" id="tokenizers">
<div class="container-fluid">
<div class="row">
<nav id="sidebar" class="col-2 d-none d-md-block">
@@ -79,11 +79,6 @@
<div class="sidebar-header">
<div class="sidebarTitle text-center">Apache Solr Reference Guide</div>
- <p class="draft-notice">
- This is an unofficial DRAFT of the Guide for 8.6.
- <a href="https://lucene.apache.org/solr/guide/">Official releases are available from the Solr website</a>.
- </p>
-
<!--comment out this block if you want to hide search-->
<!--start search-->
@@ -1689,7 +1684,7 @@
<span style="color: #000080"></fieldType></span></code></pre></code></pre></div>
<p>The following sections describe the tokenizer factory classes included in this release of Solr.</p></section>
<section class="sect1"><h2 id="standard-tokenizer">Standard Tokenizer</h2><p>This tokenizer splits the text field into tokens, treating whitespace and punctuation as delimiters. Delimiter characters are discarded, with the following exceptions:</p>
-<div class="ulist"><ul><li>Periods (dots) that are not followed by whitespace are kept as part of the token, including Internet domain names.</li><li>The "@" character is among the set of token-splitting punctuation, so email addresses are <strong>not</strong> preserved as single tokens.</li></ul></div>
+<div class="ulist"><ul><li><p>Periods (dots) that are not followed by whitespace are kept as part of the token, including Internet domain names.</p></li><li><p>The "@" character is among the set of token-splitting punctuation, so email addresses are <strong>not</strong> preserved as single tokens.</p></li></ul></div>
<p>Note that words are split at hyphens.</p>
<p>The Standard Tokenizer supports <a href="http://unicode.org/reports/tr29/#Word_Boundaries">Unicode standard annex UAX#29</a> word boundaries with the following token types: <code><ALPHANUM></code>, <code><NUM></code>, <code><SOUTHEAST_ASIAN></code>, <code><IDEOGRAPHIC></code>, and <code><HIRAGANA></code>.</p>
<p><strong>Factory class:</strong> <code>solr.StandardTokenizerFactory</code></p>
@@ -1702,7 +1697,7 @@
<p><strong>In:</strong> "Please, email <a href="mailto:john.doe@foo.com">john.doe@foo.com</a> by 03-09, re: m37-xq."</p>
<p><strong>Out:</strong> "Please", "email", "john.doe", "foo.com", "by", "03", "09", "re", "m37", "xq"</p></section>
<section class="sect1"><h2 id="classic-tokenizer">Classic Tokenizer</h2><p>The Classic Tokenizer preserves the same behavior as the Standard Tokenizer of Solr versions 3.1 and previous. It does not use the <a href="http://unicode.org/reports/tr29/#Word_Boundaries">Unicode standard annex UAX#29</a> word boundary rules that the Standard Tokenizer uses. This tokenizer splits the text field into tokens, treating whitespace and punctuation as delimiters. Delimiter characters are discarded, with the following exceptions:</p>
-<div class="ulist"><ul><li>Periods (dots) that are not followed by whitespace are kept as part of the token.</li><li>Words are split at hyphens, unless there is a number in the word, in which case the token is not split and the numbers and hyphen(s) are preserved.</li><li>Recognizes Internet domain names and email addresses and preserves them as a single token.</li></ul></div>
+<div class="ulist"><ul><li><p>Periods (dots) that are not followed by whitespace are kept as part of the token.</p></li><li><p>Words are split at hyphens, unless there is a number in the word, in which case the token is not split and the numbers and hyphen(s) are preserved.</p></li><li><p>Recognizes Internet domain names and email addresses and preserves them as a single token.</p></li></ul></div>
<p><strong>Factory class:</strong> <code>solr.ClassicTokenizerFactory</code></p>
<p><strong>Arguments:</strong></p>
<p><code>maxTokenLength</code>: (integer, default 255) Solr ignores tokens that exceed the number of characters specified by <code>maxTokenLength</code>.</p>
@@ -1865,7 +1860,7 @@
<span style="color: #000080"><tokenizer</span> <span style="color: #008080">class=</span><span style="color: #d14">"solr.SimplePatternSplitTokenizerFactory"</span> <span style="color: #008080">pattern=</span><span style="color: #d14">"[ \t\r\n]+"</span><span style="color: #000080">/></span>
<span style="color: #000080"></analyzer></span></code></pre></code></pre></div></section>
<section class="sect1"><h2 id="uax29-url-email-tokenizer">UAX29 URL Email Tokenizer</h2><p>This tokenizer splits the text field into tokens, treating whitespace and punctuation as delimiters. Delimiter characters are discarded, with the following exceptions:</p>
-<div class="ulist"><ul><li>Periods (dots) that are not followed by whitespace are kept as part of the token.</li><li>Words are split at hyphens, unless there is a number in the word, in which case the token is not split and the numbers and hyphen(s) are preserved.</li><li>Recognizes and preserves as single tokens the following:<ul><li>Internet domain names containing top-level domains validated against the white list in the <a href="http://www.internic.net/zones/root.zone">IANA Root Zone Database</a> when the tokenizer was generated</li><li>email addresses</li><li><code>file://</code>, <code>http(s)://</code>, and <code>ftp://</code> URLs</li><li>IPv4 and IPv6 addresses</li></ul></li></ul></div>
+<div class="ulist"><ul><li><p>Periods (dots) that are not followed by whitespace are kept as part of the token.</p></li><li><p>Words are split at hyphens, unless there is a number in the word, in which case the token is not split and the numbers and hyphen(s) are preserved.</p></li><li><p>Recognizes and preserves as single tokens the following:<ul><li><p>Internet domain names containing top-level domains validated against the white list in the <a href="http://www.internic.net/zones/root.zone">IANA Root Zone Database</a> when the tokenizer was generated</p></li><li><p>email addresses</p></li><li><p><code>file://</code>, <code>http(s)://</code>, and <code>ftp://</code> URLs</p></li><li><p>IPv4 and IPv6 addresses</p></li></ul></p></li></ul></div>
<p>The UAX29 URL Email Tokenizer supports <a href="http://unicode.org/reports/tr29/#Word_Boundaries">Unicode standard annex UAX#29</a> word boundaries with the following token types: <code><ALPHANUM></code>, <code><NUM></code>, <code><URL></code>, <code><EMAIL></code>, <code><SOUTHEAST_ASIAN></code>, <code><IDEOGRAPHIC></code>, and <code><HIRAGANA></code>.</p>
<p><strong>Factory class:</strong> <code>solr.UAX29URLEmailTokenizerFactory</code></p>
<p><strong>Arguments:</strong></p>
@@ -1879,7 +1874,7 @@
<section class="sect1"><h2 id="white-space-tokenizer">White Space Tokenizer</h2><p>Simple tokenizer that splits the text stream on whitespace and returns sequences of non-whitespace characters as tokens. Note that any punctuation <em>will</em> be included in the tokens.</p>
<p><strong>Factory class:</strong> <code>solr.WhitespaceTokenizerFactory</code></p>
<p><strong>Arguments:</strong></p>
-<div class="dlist"><dl><dt><code>rule</code></dt><dd>Specifies how to define whitespace for the purpose of tokenization. Valid values:<ul><li><code>java</code>: (Default) Uses <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Character.html#isWhitespace-int-">Character.isWhitespace(int)</a></li><li><code>unicode</code>: Uses Unicode’s WHITESPACE property</li></ul></dd></dl></div>
+<div class="dlist"><dl><dt><code>rule</code></dt><dd>Specifies how to define whitespace for the purpose of tokenization. Valid values:<ul><li><p><code>java</code>: (Default) Uses <a href="https://docs.oracle.com/javase/8/docs/api/java/lang/Character.html#isWhitespace-int-">Character.isWhitespace(int)</a></p></li><li><p><code>unicode</code>: Uses Unicode’s WHITESPACE property</p></li></ul></dd></dl></div>
<p><strong>Example:</strong></p>
<div class="listingblock"><pre class="rouge highlight"><code class="language-xml" data-lang="xml"><pre class="highlight"><code><span style="color: #000080"><analyzer></span>
<span style="color: #000080"><tokenizer</span> <span style="color: #008080">class=</span><span style="color: #d14">"solr.WhitespaceTokenizerFactory"</span> <span style="color: #008080">rule=</span><span style="color: #d14">"java"</span> <span style="color: #000080">/></span>
@@ -1916,7 +1911,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/transforming-and-indexing-custom-json.html
==============================================================================
--- websites/production/lucene/content/solr/guide/8_6/transforming-and-indexing-custom-json.html (original)
+++ websites/production/lucene/content/solr/guide/8_6/transforming-and-indexing-custom-json.html Wed Jul 15 16:52:36 2020
@@ -8,7 +8,7 @@
<meta name="description" content="">
<meta name="keywords" content=" ">
-<title>Transforming and Indexing Custom JSON | Apache Solr Reference Guide 8.6-DRAFT</title>
+<title>Transforming and Indexing Custom JSON | 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-and-indexing-custom-json">
+<body class="" id="transforming-and-indexing-custom-json">
<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-->
@@ -1931,7 +1926,7 @@
<section class="sect1"><h2 id="using-wildcards-for-field-names">Using Wildcards for Field Names</h2><p>Instead of specifying all the field names explicitly, it is possible to specify wildcards to map fields automatically.</p>
<p>There are two restrictions: wildcards can only be used at the end of the <code>json-path</code>, and the split path cannot use wildcards.</p>
<p>A single asterisk <code>*</code> maps only to direct children, and a double asterisk <code>**</code> maps recursively to all descendants. The following are example wildcard path mappings:</p>
-<div class="ulist"><ul><li><code>f=$FQN:/**</code>: maps all fields to the fully qualified name (<code>$FQN</code>) of the JSON field. The fully qualified name is obtained by concatenating all the keys in the hierarchy with a period (<code>.</code>) as a delimiter. This is the default behavior if no <code>f</code> path mappings are specified.</li><li><code>f=/docs/*</code>: maps all the fields under docs and in the name as given in JSON</li><li><code>f=/docs/**</code>: maps all the fields under docs and its children in the name as given in JSON</li><li><code>f=searchField:/docs/*</code>: maps all fields under /docs to a single field called âsearchFieldâ</li><li><code>f=searchField:/docs/**</code>: maps all fields under /docs and its children to searchField</li></ul></div>
+<div class="ulist"><ul><li><p><code>f=$FQN:/**</code>: maps all fields to the fully qualified name (<code>$FQN</code>) of the JSON field. The fully qualified name is obtained by concatenating all the keys in the hierarchy with a period (<code>.</code>) as a delimiter. This is the default behavior if no <code>f</code> path mappings are specified.</p></li><li><p><code>f=/docs/*</code>: maps all the fields under docs and in the name as given in JSON</p></li><li><p><code>f=/docs/**</code>: maps all the fields under docs and its children in the name as given in JSON</p></li><li><p><code>f=searchField:/docs/*</code>: maps all fields under /docs to a single field called âsearchFieldâ</p></li><li><p><code>f=searchField:/docs/**</code>: maps all fields under /docs and its children to searchField</p></li></ul></div>
<p>With wildcards we can further simplify our previous example as follows:</p>
<div class="openblock dynamic-tabs"><div class="content d-flex flex-row"><div class="exampleblock tab-pane" id="v1wildcards"><div class="example"><p><strong class="tab-label">V1 API</strong></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/techproducts/update/json/docs'</span><span style="color: #d14">\</span>
@@ -2223,7 +2218,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>