You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by is...@apache.org on 2017/07/29 21:59:52 UTC
[15/28] lucene-solr:jira/solr-6630: Merging master
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/8d00e53b/solr/server/solr/configsets/_default/conf/solrconfig.xml
----------------------------------------------------------------------
diff --git a/solr/server/solr/configsets/_default/conf/solrconfig.xml b/solr/server/solr/configsets/_default/conf/solrconfig.xml
index aa1ae69..3b11082 100644
--- a/solr/server/solr/configsets/_default/conf/solrconfig.xml
+++ b/solr/server/solr/configsets/_default/conf/solrconfig.xml
@@ -16,9 +16,9 @@
limitations under the License.
-->
-<!--
+<!--
For more details about configurations options that may appear in
- this file, see http://wiki.apache.org/solr/SolrConfigXml.
+ this file, see http://wiki.apache.org/solr/SolrConfigXml.
-->
<config>
<!-- In all configuration below, a prefix of "solr." for class names
@@ -46,19 +46,19 @@
instanceDir.
Please note that <lib/> directives are processed in the order
- that they appear in your solrconfig.xml file, and are "stacked"
- on top of each other when building a ClassLoader - so if you have
- plugin jars with dependencies on other jars, the "lower level"
+ that they appear in your solrconfig.xml file, and are "stacked"
+ on top of each other when building a ClassLoader - so if you have
+ plugin jars with dependencies on other jars, the "lower level"
dependency jars should be loaded first.
If a "./lib" directory exists in your instanceDir, all files
found in it are included as if you had used the following
syntax...
-
+
<lib dir="./lib" />
-->
- <!-- A 'dir' option by itself adds any files found in the directory
+ <!-- A 'dir' option by itself adds any files found in the directory
to the classpath, this is useful for including all jars in a
directory.
@@ -69,7 +69,7 @@
If a 'dir' option (with or without a regex) is used and nothing
is found that matches, a warning will be logged.
- The examples below can be used to load some solr-contribs along
+ The examples below can be used to load some solr-contribs along
with their external dependencies.
-->
<lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib" regex=".*\.jar" />
@@ -83,12 +83,12 @@
<lib dir="${solr.install.dir:../../../..}/contrib/velocity/lib" regex=".*\.jar" />
<lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-velocity-\d.*\.jar" />
- <!-- an exact 'path' can be used instead of a 'dir' to specify a
- specific jar file. This will cause a serious error to be logged
+ <!-- an exact 'path' can be used instead of a 'dir' to specify a
+ specific jar file. This will cause a serious error to be logged
if it can't be loaded.
-->
<!--
- <lib path="../a-jar-that-does-not-exist.jar" />
+ <lib path="../a-jar-that-does-not-exist.jar" />
-->
<!-- Data Directory
@@ -102,7 +102,7 @@
<!-- The DirectoryFactory to use for indexes.
-
+
solr.StandardDirectoryFactory is filesystem
based and tries to pick the best implementation for the current
JVM and platform. solr.NRTCachingDirectoryFactory, the default,
@@ -125,7 +125,7 @@
are experimental, so if you choose to customize the index format, it's a good
idea to convert back to the official format e.g. via IndexWriter.addIndexes(IndexReader)
before upgrading to a newer version to avoid unnecessary reindexing.
- A "compressionMode" string element can be added to <codecFactory> to choose
+ A "compressionMode" string element can be added to <codecFactory> to choose
between the existing compression modes in the default codec: "BEST_SPEED" (default)
or "BEST_COMPRESSION".
-->
@@ -135,19 +135,19 @@
Index Config - These settings control low-level behavior of indexing
Most example settings here show the default value, but are commented
out, to more easily see where customizations have been made.
-
+
Note: This replaces <indexDefaults> and <mainIndex> from older versions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<indexConfig>
- <!-- maxFieldLength was removed in 4.0. To get similar behavior, include a
- LimitTokenCountFilterFactory in your fieldType definition. E.g.
+ <!-- maxFieldLength was removed in 4.0. To get similar behavior, include a
+ LimitTokenCountFilterFactory in your fieldType definition. E.g.
<filter class="solr.LimitTokenCountFilterFactory" maxTokenCount="10000"/>
-->
<!-- Maximum time to wait for a write lock (ms) for an IndexWriter. Default: 1000 -->
<!-- <writeLockTimeout>1000</writeLockTimeout> -->
- <!-- Expert: Enabling compound file will use less files for the index,
- using fewer file descriptors on the expense of performance decrease.
+ <!-- Expert: Enabling compound file will use less files for the index,
+ using fewer file descriptors on the expense of performance decrease.
Default in Lucene is "true". Default in Solr is "false" (since 3.6) -->
<!-- <useCompoundFile>false</useCompoundFile> -->
@@ -161,7 +161,7 @@
<!-- <ramBufferSizeMB>100</ramBufferSizeMB> -->
<!-- <maxBufferedDocs>1000</maxBufferedDocs> -->
- <!-- Expert: Merge Policy
+ <!-- Expert: Merge Policy
The Merge Policy in Lucene controls how merging of segments is done.
The default since Solr/Lucene 3.3 is TieredMergePolicy.
The default since Lucene 2.3 was the LogByteSizeMergePolicy,
@@ -181,15 +181,15 @@
can perform merges in the background using separate threads.
The SerialMergeScheduler (Lucene 2.2 default) does not.
-->
- <!--
+ <!--
<mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>
-->
- <!-- LockFactory
+ <!-- LockFactory
This option specifies which Lucene LockFactory implementation
to use.
-
+
single = SingleInstanceLockFactory - suggested for a
read-only index or when there is no possibility of
another process trying to modify the index.
@@ -213,11 +213,11 @@
The default Solr IndexDeletionPolicy implementation supports
deleting index commit points on number of commits, age of
commit point and optimized status.
-
+
The latest commit point should always be preserved regardless
of the criteria.
-->
- <!--
+ <!--
<deletionPolicy class="solr.SolrDeletionPolicy">
-->
<!-- The number of commit points to be kept -->
@@ -232,12 +232,12 @@
<str name="maxCommitAge">30MINUTES</str>
<str name="maxCommitAge">1DAY</str>
-->
- <!--
+ <!--
</deletionPolicy>
-->
<!-- Lucene Infostream
-
+
To aid in advanced debugging, Lucene provides an "InfoStream"
of detailed information when indexing.
@@ -249,7 +249,7 @@
<!-- JMX
-
+
This example enables JMX if and only if an existing MBeanServer
is found, use this if you want to configure JMX through JVM
parameters. Remove this to disable exposing Solr configuration
@@ -259,7 +259,7 @@
-->
<jmx />
<!-- If you want to connect to a particular server, specify the
- agentId
+ agentId
-->
<!-- <jmx agentId="myAgent" /> -->
<!-- If you want to start a new MBeanServer, specify the serviceUrl -->
@@ -291,7 +291,7 @@
Perform a hard commit automatically under certain conditions.
Instead of enabling autoCommit, consider using "commitWithin"
- when adding documents.
+ when adding documents.
http://wiki.apache.org/solr/UpdateXmlMessages
@@ -300,7 +300,7 @@
maxTime - Maximum amount of time in ms that is allowed to pass
since a document was added before automatically
- triggering a new commit.
+ triggering a new commit.
openSearcher - if false, the commit causes recent index changes
to be flushed to stable storage, but does not cause a new
searcher to be opened to make those changes visible.
@@ -324,7 +324,7 @@
</autoSoftCommit>
<!-- Update Related Event Listeners
-
+
Various IndexWriter related events can trigger Listeners to
take actions.
@@ -333,10 +333,10 @@
-->
<!-- The RunExecutableListener executes an external command from a
hook such as postCommit or postOptimize.
-
+
exe - the name of the executable to run
dir - dir to use as the current working directory. (default=".")
- wait - the calling thread waits until the executable returns.
+ wait - the calling thread waits until the executable returns.
(default="true")
args - the arguments to pass to the program. (default is none)
env - environment variables to set. (default is none)
@@ -401,7 +401,7 @@
There are two implementations of cache available for Solr,
LRUCache, based on a synchronized LinkedHashMap, and
- FastLRUCache, based on a ConcurrentHashMap.
+ FastLRUCache, based on a ConcurrentHashMap.
FastLRUCache has faster gets and slower puts in single
threaded operation and thus is generally faster than LRUCache
@@ -437,7 +437,7 @@
autowarmCount="0"/>
<!-- Query Result Cache
-
+
Caches results of searches - ordered lists of document ids
(DocList) based on a query, a sort, and the range of documents requested.
Additional supported parameter by LRUCache:
@@ -469,7 +469,7 @@
regenerator="solr.NoOpRegenerator" />
<!-- Field Value Cache
-
+
Cache used to hold field values that are quickly accessible
by document id. The fieldValueCache is created by default
even if not configured here.
@@ -487,8 +487,8 @@
name through SolrIndexSearcher.getCache(),cacheLookup(), and
cacheInsert(). The purpose is to enable easy caching of
user/application level data. The regenerator argument should
- be specified as an implementation of solr.CacheRegenerator
- if autowarming is desired.
+ be specified as an implementation of solr.CacheRegenerator
+ if autowarming is desired.
-->
<!--
<cache name="myUserCache"
@@ -512,14 +512,14 @@
<enableLazyFieldLoading>true</enableLazyFieldLoading>
<!-- Use Filter For Sorted Query
-
+
A possible optimization that attempts to use a filter to
satisfy a search. If the requested sort does not include
score, then the filterCache will be checked for a filter
matching the query. If found, the filter will be used as the
source of document ids, and then the sort will be applied to
that.
-
+
For most situations, this will not be useful unless you
frequently get the same search repeatedly with different sort
options, and none of them ever use "score"
@@ -529,39 +529,39 @@
-->
<!-- Result Window Size
-
+
An optimization for use with the queryResultCache. When a search
is requested, a superset of the requested number of document ids
are collected. For example, if a search for a particular query
requests matching documents 10 through 19, and queryWindowSize is 50,
then documents 0 through 49 will be collected and cached. Any further
- requests in that range can be satisfied via the cache.
+ requests in that range can be satisfied via the cache.
-->
<queryResultWindowSize>20</queryResultWindowSize>
<!-- Maximum number of documents to cache for any entry in the
- queryResultCache.
+ queryResultCache.
-->
<queryResultMaxDocsCached>200</queryResultMaxDocsCached>
<!-- Query Related Event Listeners
-
+
Various IndexSearcher related events can trigger Listeners to
take actions.
-
+
newSearcher - fired whenever a new searcher is being prepared
and there is a current searcher handling requests (aka
registered). It can be used to prime certain caches to
prevent long request times for certain requests.
-
+
firstSearcher - fired whenever a new searcher is being
prepared but there is no current registered searcher to handle
requests or to gain autowarming data from.
-
-
+
+
-->
<!-- QuerySenderListener takes an array of NamedList and executes a
- local query request for each NamedList in sequence.
+ local query request for each NamedList in sequence.
-->
<listener event="newSearcher" class="solr.QuerySenderListener">
<arr name="queries">
@@ -611,19 +611,19 @@
multipartUploadLimitInKB - specifies the max size (in KiB) of
Multipart File Uploads that Solr will allow in a Request.
-
+
formdataUploadLimitInKB - specifies the max size (in KiB) of
form data (application/x-www-form-urlencoded) sent via
POST. You can use POST to pass request parameters not
fitting into the URL.
-
+
addHttpRequestToContext - if set to true, it will instruct
the requestParsers to include the original HttpServletRequest
- object in the context map of the SolrQueryRequest under the
+ object in the context map of the SolrQueryRequest under the
key "httpRequest". It will not be used by any of the existing
- Solr components, but may be useful when developing custom
+ Solr components, but may be useful when developing custom
plugins.
-
+
*** WARNING ***
Before enabling remote streaming, you should make sure your
system has authentication enabled.
@@ -645,21 +645,21 @@
<!-- If you include a <cacheControl> directive, it will be used to
generate a Cache-Control header (as well as an Expires header
if the value contains "max-age=")
-
+
By default, no Cache-Control header is generated.
-
+
You can use the <cacheControl> option even if you have set
never304="true"
-->
<!--
<httpCaching never304="true" >
- <cacheControl>max-age=30, public</cacheControl>
+ <cacheControl>max-age=30, public</cacheControl>
</httpCaching>
-->
<!-- To enable Solr to respond with automatically generated HTTP
Caching headers, and to response to Cache Validation requests
correctly, set the value of never304="false"
-
+
This will cause Solr to generate Last-Modified and ETag
headers based on the properties of the Index.
@@ -684,12 +684,12 @@
<!--
<httpCaching lastModifiedFrom="openTime"
etagSeed="Solr">
- <cacheControl>max-age=30, public</cacheControl>
+ <cacheControl>max-age=30, public</cacheControl>
</httpCaching>
-->
</requestDispatcher>
- <!-- Request Handlers
+ <!-- Request Handlers
http://wiki.apache.org/solr/SolrRequestHandler
@@ -716,7 +716,12 @@
<lst name="defaults">
<str name="echoParams">explicit</str>
<int name="rows">10</int>
- <!-- <str name="df">text</str> -->
+ <!-- Default search field
+ <str name="df">text</str>
+ -->
+ <!-- Change from JSON to XML format (the default prior to Solr 7.0)
+ <str name="wt">xml</str>
+ -->
</lst>
<!-- In addition to defaults, "appends" params can be specified
to identify values which should be appended to the list of
@@ -783,7 +788,7 @@
<!-- A Robust Example
-
+
This example SearchHandler declaration shows off usage of the
SearchHandler with many defaults declared
@@ -805,7 +810,7 @@
<!-- Solr Cell Update Request Handler
- http://wiki.apache.org/solr/ExtractingRequestHandler
+ http://wiki.apache.org/solr/ExtractingRequestHandler
-->
<requestHandler name="/update/extract"
@@ -820,18 +825,18 @@
<!-- Search Components
- Search components are registered to SolrCore and used by
+ Search components are registered to SolrCore and used by
instances of SearchHandler (which can access them by name)
-
+
By default, the following components are available:
-
+
<searchComponent name="query" class="solr.QueryComponent" />
<searchComponent name="facet" class="solr.FacetComponent" />
<searchComponent name="mlt" class="solr.MoreLikeThisComponent" />
<searchComponent name="highlight" class="solr.HighlightComponent" />
<searchComponent name="stats" class="solr.StatsComponent" />
<searchComponent name="debug" class="solr.DebugComponent" />
-
+
Default configuration in a requestHandler would look like:
<arr name="components">
@@ -843,28 +848,28 @@
<str>debug</str>
</arr>
- If you register a searchComponent to one of the standard names,
+ If you register a searchComponent to one of the standard names,
that will be used instead of the default.
To insert components before or after the 'standard' components, use:
-
+
<arr name="first-components">
<str>myFirstComponentName</str>
</arr>
-
+
<arr name="last-components">
<str>myLastComponentName</str>
</arr>
NOTE: The component registered with the name "debug" will
- always be executed after the "last-components"
-
+ always be executed after the "last-components"
+
-->
<!-- Spell Check
The spell check component can return a list of alternative spelling
- suggestions.
+ suggestions.
http://wiki.apache.org/solr/SpellCheckComponent
-->
@@ -913,7 +918,7 @@
-->
</searchComponent>
- <!-- A request handler for demonstrating the spellcheck component.
+ <!-- A request handler for demonstrating the spellcheck component.
NOTE: This is purely as an example. The whole purpose of the
SpellCheckComponent is to hook it into the request handler that
@@ -922,7 +927,7 @@
IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW IS
NOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!
-
+
See http://wiki.apache.org/solr/SpellCheckComponent for details
on the request parameters.
-->
@@ -958,8 +963,8 @@
This is purely as an example.
- In reality you will likely want to add the component to your
- already specified request handlers.
+ In reality you will likely want to add the component to your
+ already specified request handlers.
-->
<requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy">
<lst name="defaults">
@@ -1032,8 +1037,8 @@
</lst>
</fragmenter>
- <!-- A regular-expression-based fragmenter
- (for sentence extraction)
+ <!-- A regular-expression-based fragmenter
+ (for sentence extraction)
-->
<fragmenter name="regex"
class="solr.highlight.RegexFragmenter">
@@ -1078,7 +1083,7 @@
<fragmentsBuilder name="default"
default="true"
class="solr.highlight.ScoreOrderFragmentsBuilder">
- <!--
+ <!--
<lst name="defaults">
<str name="hl.multiValuedSeparatorChar">/</str>
</lst>
@@ -1131,19 +1136,19 @@
http://wiki.apache.org/solr/UpdateRequestProcessor
-->
-
- <!-- Add unknown fields to the schema
-
+
+ <!-- Add unknown fields to the schema
+
Field type guessing update processors that will
attempt to parse string-typed field values as Booleans, Longs,
Doubles, or Dates, and then add schema fields with the guessed
field types. Text content will be indexed as "text_general" as
- well as a copy to a plain string version in *_str.
-
+ well as a copy to a plain string version in *_str.
+
These require that the schema is both managed and mutable, by
declaring schemaFactory as ManagedIndexSchemaFactory, with
- mutable specified as true.
-
+ mutable specified as true.
+
See http://wiki.apache.org/solr/GuessingFieldTypes
-->
<updateProcessor class="solr.UUIDUpdateProcessorFactory" name="uuid"/>
@@ -1220,8 +1225,8 @@
on the fly based on the hash code of some other fields. This
example has overwriteDupes set to false since we are using the
id field as the signatureField and Solr will maintain
- uniqueness based on that anyway.
-
+ uniqueness based on that anyway.
+
-->
<!--
<updateRequestProcessorChain name="dedupe">
@@ -1292,7 +1297,7 @@
overridden...
-->
<!--
- <queryResponseWriter name="xml"
+ <queryResponseWriter name="xml"
default="true"
class="solr.XMLResponseWriter" />
<queryResponseWriter name="json" class="solr.JSONResponseWriter"/>
@@ -1323,7 +1328,7 @@
<!-- XSLT response writer transforms the XML output by any xslt file found
in Solr's conf/xslt directory. Changes to xslt files are checked for
- every xsltCacheLifetimeSeconds.
+ every xsltCacheLifetimeSeconds.
-->
<queryResponseWriter name="xslt" class="solr.XSLTResponseWriter">
<int name="xsltCacheLifetimeSeconds">5</int>
@@ -1331,7 +1336,7 @@
<!-- Query Parsers
- https://cwiki.apache.org/confluence/display/solr/Query+Syntax+and+Parsing
+ https://lucene.apache.org/solr/guide/query-syntax-and-parsing.html
Multiple QParserPlugins can be registered by name, and then
used in either the "defType" param for the QueryComponent (used
@@ -1351,7 +1356,7 @@
-->
<!-- example of registering a custom function parser -->
<!--
- <valueSourceParser name="myfunc"
+ <valueSourceParser name="myfunc"
class="com.mycompany.MyValueSourceParser" />
-->
@@ -1364,12 +1369,12 @@
<transformer name="db" class="com.mycompany.LoadFromDatabaseTransformer" >
<int name="connection">jdbc://....</int>
</transformer>
-
+
To add a constant value to all docs, use:
<transformer name="mytrans2" class="org.apache.solr.response.transform.ValueAugmenterFactory" >
<int name="value">5</int>
</transformer>
-
+
If you want the user to still be able to change it with _value:something_ use this:
<transformer name="mytrans3" class="org.apache.solr.response.transform.ValueAugmenterFactory" >
<double name="defaultValue">5</double>
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/8d00e53b/solr/server/solr/configsets/sample_techproducts_configs/conf/managed-schema
----------------------------------------------------------------------
diff --git a/solr/server/solr/configsets/sample_techproducts_configs/conf/managed-schema b/solr/server/solr/configsets/sample_techproducts_configs/conf/managed-schema
index cd33c4f..5d1986c 100644
--- a/solr/server/solr/configsets/sample_techproducts_configs/conf/managed-schema
+++ b/solr/server/solr/configsets/sample_techproducts_configs/conf/managed-schema
@@ -76,10 +76,10 @@
grouping, sorting and function queries. Doc values will make the index
faster to load, more NRT-friendly and more memory-efficient.
They however come with some limitations: they are currently only
- supported by StrField, UUIDField, all Trie*Fields and *PointFields,
- and depending on the field type, they might require the field to be
- single-valued, be required or have a default value (check the
- documentation of the field type you're interested in for more information)
+ supported by StrField, UUIDField, all *PointFields, and depending
+ on the field type, they might require the field to be single-valued,
+ be required or have a default value (check the documentation
+ of the field type you're interested in for more information)
multiValued: true if this field may contain multiple values per document
omitNorms: (expert) set to true to omit the norms associated with
this field (this disables length normalization and index-time
@@ -113,7 +113,7 @@
or Solr won't start. _version_ and update log are required for SolrCloud
-->
<!-- doc values are enabled by default for primitive types such as long so we don't index the version field -->
- <field name="_version_" type="long" indexed="false" stored="false"/>
+ <field name="_version_" type="plong" indexed="false" stored="false"/>
<!-- points to the root document of a block of nested documents. Required for nested
document support, may be removed otherwise
@@ -196,47 +196,28 @@
RESTRICTION: the glob-like pattern in the name attribute must have
a "*" only at the start or the end. -->
- <dynamicField name="*_i" type="int" indexed="true" stored="true"/>
- <dynamicField name="*_is" type="int" indexed="true" stored="true" multiValued="true"/>
+ <dynamicField name="*_i" type="pint" indexed="true" stored="true"/>
+ <dynamicField name="*_is" type="pint" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="*_s" type="string" indexed="true" stored="true" />
<dynamicField name="*_s_ns" type="string" indexed="true" stored="false" />
<dynamicField name="*_ss" type="string" indexed="true" stored="true" multiValued="true"/>
- <dynamicField name="*_l" type="long" indexed="true" stored="true"/>
- <dynamicField name="*_l_ns" type="long" indexed="true" stored="false"/>
- <dynamicField name="*_ls" type="long" indexed="true" stored="true" multiValued="true"/>
+ <dynamicField name="*_l" type="plong" indexed="true" stored="true"/>
+ <dynamicField name="*_l_ns" type="plong" indexed="true" stored="false"/>
+ <dynamicField name="*_ls" type="plong" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="*_t" type="text_general" indexed="true" stored="true"/>
<dynamicField name="*_txt" type="text_general" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="*_en" type="text_en" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="*_b" type="boolean" indexed="true" stored="true"/>
<dynamicField name="*_bs" type="boolean" indexed="true" stored="true" multiValued="true"/>
- <dynamicField name="*_f" type="float" indexed="true" stored="true"/>
- <dynamicField name="*_fs" type="float" indexed="true" stored="true" multiValued="true"/>
- <dynamicField name="*_d" type="double" indexed="true" stored="true"/>
- <dynamicField name="*_ds" type="double" indexed="true" stored="true" multiValued="true"/>
+ <dynamicField name="*_f" type="pfloat" indexed="true" stored="true"/>
+ <dynamicField name="*_fs" type="pfloat" indexed="true" stored="true" multiValued="true"/>
+ <dynamicField name="*_d" type="pdouble" indexed="true" stored="true"/>
+ <dynamicField name="*_ds" type="pdouble" indexed="true" stored="true" multiValued="true"/>
- <dynamicField name="*_dt" type="date" indexed="true" stored="true"/>
- <dynamicField name="*_dts" type="date" indexed="true" stored="true" multiValued="true"/>
+ <dynamicField name="*_dt" type="pdate" indexed="true" stored="true"/>
+ <dynamicField name="*_dts" type="pdate" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="*_p" type="location" indexed="true" stored="true"/>
- <!-- KD-tree (point) numerics -->
- <dynamicField name="*_pi" type="pint" indexed="true" stored="true"/>
- <dynamicField name="*_pis" type="pints" indexed="true" stored="true"/>
- <dynamicField name="*_pl" type="plong" indexed="true" stored="true"/>
- <dynamicField name="*_pls" type="plongs" indexed="true" stored="true"/>
- <dynamicField name="*_pf" type="pfloat" indexed="true" stored="true"/>
- <dynamicField name="*_pfs" type="pfloats" indexed="true" stored="true"/>
- <dynamicField name="*_pd" type="pdouble" indexed="true" stored="true"/>
- <dynamicField name="*_pds" type="pdoubles" indexed="true" stored="true"/>
- <dynamicField name="*_pdt" type="pdate" indexed="true" stored="true"/>
- <dynamicField name="*_pdts" type="pdates" indexed="true" stored="true"/>
-
- <!-- some trie-coded dynamic fields -->
- <dynamicField name="*_ti" type="tint" indexed="true" stored="true"/>
- <dynamicField name="*_tl" type="tlong" indexed="true" stored="true"/>
- <dynamicField name="*_tf" type="tfloat" indexed="true" stored="true"/>
- <dynamicField name="*_td" type="tdouble" indexed="true" stored="true"/>
- <dynamicField name="*_tdt" type="tdate" indexed="true" stored="true"/>
-
<dynamicField name="*_c" type="currency" indexed="true" stored="true"/>
<dynamicField name="ignored_*" type="ignored" multiValued="true"/>
@@ -249,8 +230,6 @@
alternately, change the type="ignored" to some other type e.g. "text" if you want
unknown fields indexed and/or stored by default -->
<!--dynamicField name="*" type="ignored" multiValued="true" /-->
-
-
<!-- Field to use to determine and enforce document uniqueness.
@@ -282,18 +261,6 @@
<copyField source="resourcename" dest="text"/>
<copyField source="url" dest="text"/>
- <!-- Copy numeric fields to *PointFields implementation -->
- <copyField source="*_i" dest="*_pi"/>
- <copyField source="*_l" dest="*_pl"/>
- <copyField source="*_f" dest="*_pf"/>
- <copyField source="*_d" dest="*_pd"/>
- <copyField source="*_dt" dest="*_pdt"/>
- <copyField source="*_is" dest="*_pis"/>
- <copyField source="*_ls" dest="*_pds"/>
- <copyField source="*_fs" dest="*_pfs"/>
- <copyField source="*_ds" dest="*_pds"/>
- <copyField source="*_dts" dest="*_pdts"/>
-
<!-- Create a string version of author for faceting -->
<copyField source="author" dest="author_s"/>
@@ -328,8 +295,7 @@
<!-- sortMissingLast and sortMissingFirst attributes are optional attributes are
currently supported on types that are sorted internally as strings
and on numeric types.
- This includes "string","boolean", "int", "float", "long", "date", "double",
- including the "Trie" and "Point" variants.
+ This includes "string", "boolean", "pint", "pfloat", "plong", "pdate", "pdouble".
- If sortMissingLast="true", then a sort on this field will cause documents
without the field to come after documents with the field,
regardless of the requested sort order (asc or desc).
@@ -342,8 +308,7 @@
-->
<!--
- Numeric field types that index values using KD-trees. *Point fields are faster and more efficient than Trie* fields both, at
- search time and at index time, but some features are still not supported.
+ Numeric field types that index values using KD-trees.
Point fields don't support FieldCache, so they must have docValues="true" if needed for sorting, faceting, functions, etc.
-->
<fieldType name="pint" class="solr.IntPointField" docValues="true"/>
@@ -356,32 +321,6 @@
<fieldType name="plongs" class="solr.LongPointField" docValues="true" multiValued="true"/>
<fieldType name="pdoubles" class="solr.DoublePointField" docValues="true" multiValued="true"/>
- <!--
- Default numeric field types. For faster range queries, consider *PointFields (pint/pfloat/plong/pdouble), or the
- tint/tfloat/tlong/tdouble types.
- -->
- <fieldType name="int" class="solr.TrieIntField" docValues="true" precisionStep="0" positionIncrementGap="0"/>
- <fieldType name="float" class="solr.TrieFloatField" docValues="true" precisionStep="0" positionIncrementGap="0"/>
- <fieldType name="long" class="solr.TrieLongField" docValues="true" precisionStep="0" positionIncrementGap="0"/>
- <fieldType name="double" class="solr.TrieDoubleField" docValues="true" precisionStep="0" positionIncrementGap="0"/>
-
- <!--
- Numeric field types that index each value at various levels of precision
- to accelerate range queries when the number of values between the range
- endpoints is large. See the javadoc for NumericRangeQuery for internal
- implementation details.
-
- Smaller precisionStep values (specified in bits) will lead to more tokens
- indexed per value, slightly larger index size, and faster range queries.
- A precisionStep of 0 disables indexing at different precision levels.
-
- Consider using pint/pfloat/plong/pdouble instead of Trie* fields if possible
- -->
- <fieldType name="tint" class="solr.TrieIntField" docValues="true" precisionStep="8" positionIncrementGap="0"/>
- <fieldType name="tfloat" class="solr.TrieFloatField" docValues="true" precisionStep="8" positionIncrementGap="0"/>
- <fieldType name="tlong" class="solr.TrieLongField" docValues="true" precisionStep="8" positionIncrementGap="0"/>
- <fieldType name="tdouble" class="solr.TrieDoubleField" docValues="true" precisionStep="8" positionIncrementGap="0"/>
-
<!-- The format for this date field is of the form 1995-12-31T23:59:59Z, and
is a more restricted form of the canonical representation of dateTime
http://www.w3.org/TR/xmlschema-2/#dateTime
@@ -400,18 +339,13 @@
... 6 months and 3 days in the future from the start of
the current day
- Consult the TrieDateField javadocs for more information.
+ Consult the DatePointField javadocs for more information.
-->
<!-- KD-tree versions of date fields -->
<fieldType name="pdate" class="solr.DatePointField" docValues="true"/>
<fieldType name="pdates" class="solr.DatePointField" docValues="true" multiValued="true"/>
-
- <fieldType name="date" class="solr.TrieDateField" docValues="true" precisionStep="0" positionIncrementGap="0"/>
- <fieldType name="tdate" class="solr.TrieDateField" docValues="true" precisionStep="6" positionIncrementGap="0"/>
-
-
<!--Binary data type. The data should be sent/retrieved in as Base64 encoded Strings -->
<fieldType name="binary" class="solr.BinaryField"/>
@@ -757,8 +691,7 @@
special relevancy modes: score=overlapRatio|area|area2D (local-param to the query). DocValues is recommended for
relevancy. -->
<fieldType name="bbox" class="solr.BBoxField"
- geo="true" distanceUnits="kilometers" numberType="_bbox_coord" />
- <fieldType name="_bbox_coord" class="solr.TrieDoubleField" precisionStep="8" docValues="true" useDocValuesAsStored="false" stored="false" />
+ geo="true" distanceUnits="kilometers" numberType="pdouble" />
<!-- Money/currency field type. See http://wiki.apache.org/solr/MoneyFieldType
Parameters:
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/8d00e53b/solr/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml
----------------------------------------------------------------------
diff --git a/solr/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml b/solr/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml
index 8adf13e..42b12cf 100644
--- a/solr/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml
+++ b/solr/server/solr/configsets/sample_techproducts_configs/conf/solrconfig.xml
@@ -16,9 +16,9 @@
limitations under the License.
-->
-<!--
+<!--
For more details about configurations options that may appear in
- this file, see http://wiki.apache.org/solr/SolrConfigXml.
+ this file, see http://wiki.apache.org/solr/SolrConfigXml.
-->
<config>
<!-- In all configuration below, a prefix of "solr." for class names
@@ -46,19 +46,19 @@
instanceDir.
Please note that <lib/> directives are processed in the order
- that they appear in your solrconfig.xml file, and are "stacked"
- on top of each other when building a ClassLoader - so if you have
- plugin jars with dependencies on other jars, the "lower level"
+ that they appear in your solrconfig.xml file, and are "stacked"
+ on top of each other when building a ClassLoader - so if you have
+ plugin jars with dependencies on other jars, the "lower level"
dependency jars should be loaded first.
If a "./lib" directory exists in your instanceDir, all files
found in it are included as if you had used the following
syntax...
-
+
<lib dir="./lib" />
-->
- <!-- A 'dir' option by itself adds any files found in the directory
+ <!-- A 'dir' option by itself adds any files found in the directory
to the classpath, this is useful for including all jars in a
directory.
@@ -69,7 +69,7 @@
If a 'dir' option (with or without a regex) is used and nothing
is found that matches, a warning will be logged.
- The examples below can be used to load some solr-contribs along
+ The examples below can be used to load some solr-contribs along
with their external dependencies.
-->
<lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib" regex=".*\.jar" />
@@ -87,14 +87,14 @@
<lib dir="${solr.install.dir:../../../..}/contrib/velocity/lib" regex=".*\.jar" />
<lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-velocity-\d.*\.jar" />
- <!-- an exact 'path' can be used instead of a 'dir' to specify a
- specific jar file. This will cause a serious error to be logged
+ <!-- an exact 'path' can be used instead of a 'dir' to specify a
+ specific jar file. This will cause a serious error to be logged
if it can't be loaded.
-->
<!--
- <lib path="../a-jar-that-does-not-exist.jar" />
+ <lib path="../a-jar-that-does-not-exist.jar" />
-->
-
+
<!-- Data Directory
Used to specify an alternate directory to hold all index data
@@ -106,7 +106,7 @@
<!-- The DirectoryFactory to use for indexes.
-
+
solr.StandardDirectoryFactory is filesystem
based and tries to pick the best implementation for the current
JVM and platform. solr.NRTCachingDirectoryFactory, the default,
@@ -118,7 +118,7 @@
solr.RAMDirectoryFactory is memory based and not persistent.
-->
- <directoryFactory name="DirectoryFactory"
+ <directoryFactory name="DirectoryFactory"
class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"/>
<!-- The CodecFactory for defining the format of the inverted index.
@@ -129,7 +129,7 @@
are experimental, so if you choose to customize the index format, it's a good
idea to convert back to the official format e.g. via IndexWriter.addIndexes(IndexReader)
before upgrading to a newer version to avoid unnecessary reindexing.
- A "compressionMode" string element can be added to <codecFactory> to choose
+ A "compressionMode" string element can be added to <codecFactory> to choose
between the existing compression modes in the default codec: "BEST_SPEED" (default)
or "BEST_COMPRESSION".
-->
@@ -139,19 +139,19 @@
Index Config - These settings control low-level behavior of indexing
Most example settings here show the default value, but are commented
out, to more easily see where customizations have been made.
-
+
Note: This replaces <indexDefaults> and <mainIndex> from older versions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<indexConfig>
- <!-- maxFieldLength was removed in 4.0. To get similar behavior, include a
- LimitTokenCountFilterFactory in your fieldType definition. E.g.
+ <!-- maxFieldLength was removed in 4.0. To get similar behavior, include a
+ LimitTokenCountFilterFactory in your fieldType definition. E.g.
<filter class="solr.LimitTokenCountFilterFactory" maxTokenCount="10000"/>
-->
<!-- Maximum time to wait for a write lock (ms) for an IndexWriter. Default: 1000 -->
<!-- <writeLockTimeout>1000</writeLockTimeout> -->
- <!-- Expert: Enabling compound file will use less files for the index,
- using fewer file descriptors on the expense of performance decrease.
+ <!-- Expert: Enabling compound file will use less files for the index,
+ using fewer file descriptors on the expense of performance decrease.
Default in Lucene is "true". Default in Solr is "false" (since 3.6) -->
<!-- <useCompoundFile>false</useCompoundFile> -->
@@ -166,7 +166,7 @@
<!-- <ramBufferSizeMB>100</ramBufferSizeMB> -->
<!-- <maxBufferedDocs>1000</maxBufferedDocs> -->
- <!-- Expert: Merge Policy
+ <!-- Expert: Merge Policy
The Merge Policy in Lucene controls how merging of segments is done.
The default since Solr/Lucene 3.3 is TieredMergePolicy.
The default since Lucene 2.3 was the LogByteSizeMergePolicy,
@@ -186,15 +186,15 @@
can perform merges in the background using separate threads.
The SerialMergeScheduler (Lucene 2.2 default) does not.
-->
- <!--
+ <!--
<mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>
-->
- <!-- LockFactory
+ <!-- LockFactory
This option specifies which Lucene LockFactory implementation
to use.
-
+
single = SingleInstanceLockFactory - suggested for a
read-only index or when there is no possibility of
another process trying to modify the index.
@@ -218,11 +218,11 @@
The default Solr IndexDeletionPolicy implementation supports
deleting index commit points on number of commits, age of
commit point and optimized status.
-
+
The latest commit point should always be preserved regardless
of the criteria.
-->
- <!--
+ <!--
<deletionPolicy class="solr.SolrDeletionPolicy">
-->
<!-- The number of commit points to be kept -->
@@ -237,12 +237,12 @@
<str name="maxCommitAge">30MINUTES</str>
<str name="maxCommitAge">1DAY</str>
-->
- <!--
+ <!--
</deletionPolicy>
-->
<!-- Lucene Infostream
-
+
To aid in advanced debugging, Lucene provides an "InfoStream"
of detailed information when indexing.
@@ -255,7 +255,7 @@
<!-- JMX
-
+
This example enables JMX if and only if an existing MBeanServer
is found, use this if you want to configure JMX through JVM
parameters. Remove this to disable exposing Solr configuration
@@ -265,7 +265,7 @@
-->
<jmx />
<!-- If you want to connect to a particular server, specify the
- agentId
+ agentId
-->
<!-- <jmx agentId="myAgent" /> -->
<!-- If you want to start a new MBeanServer, specify the serviceUrl -->
@@ -292,12 +292,12 @@
<str name="dir">${solr.ulog.dir:}</str>
<int name="numVersionBuckets">${solr.ulog.numVersionBuckets:65536}</int>
</updateLog>
-
+
<!-- AutoCommit
Perform a hard commit automatically under certain conditions.
Instead of enabling autoCommit, consider using "commitWithin"
- when adding documents.
+ when adding documents.
http://wiki.apache.org/solr/UpdateXmlMessages
@@ -306,7 +306,7 @@
maxTime - Maximum amount of time in ms that is allowed to pass
since a document was added before automatically
- triggering a new commit.
+ triggering a new commit.
openSearcher - if false, the commit causes recent index changes
to be flushed to stable storage, but does not cause a new
searcher to be opened to make those changes visible.
@@ -314,9 +314,9 @@
If the updateLog is enabled, then it's highly recommended to
have some sort of hard autoCommit to limit the log size.
-->
- <autoCommit>
- <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
- <openSearcher>false</openSearcher>
+ <autoCommit>
+ <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
+ <openSearcher>false</openSearcher>
</autoCommit>
<!-- softAutoCommit is like autoCommit except it causes a
@@ -325,12 +325,12 @@
faster and more near-realtime friendly than a hard commit.
-->
- <autoSoftCommit>
- <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
+ <autoSoftCommit>
+ <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
</autoSoftCommit>
<!-- Update Related Event Listeners
-
+
Various IndexWriter related events can trigger Listeners to
take actions.
@@ -339,10 +339,10 @@
-->
<!-- The RunExecutableListener executes an external command from a
hook such as postCommit or postOptimize.
-
+
exe - the name of the executable to run
dir - dir to use as the current working directory. (default=".")
- wait - the calling thread waits until the executable returns.
+ wait - the calling thread waits until the executable returns.
(default="true")
args - the arguments to pass to the program. (default is none)
env - environment variables to set. (default is none)
@@ -362,7 +362,7 @@
-->
</updateHandler>
-
+
<!-- IndexReaderFactory
Use the following format to specify a custom IndexReaderFactory,
@@ -403,15 +403,15 @@
-->
<maxBooleanClauses>1024</maxBooleanClauses>
-
+
<!-- Slow Query Threshold (in millis)
-
- At high request rates, logging all requests can become a bottleneck
+
+ At high request rates, logging all requests can become a bottleneck
and therefore INFO logging is often turned off. However, it is still
useful to be able to set a latency threshold above which a request
is considered "slow" and log that request at WARN level so we can
easily identify slow queries.
- -->
+ -->
<slowQueryThresholdMillis>-1</slowQueryThresholdMillis>
@@ -419,7 +419,7 @@
There are two implementations of cache available for Solr,
LRUCache, based on a synchronized LinkedHashMap, and
- FastLRUCache, based on a ConcurrentHashMap.
+ FastLRUCache, based on a ConcurrentHashMap.
FastLRUCache has faster gets and slower puts in single
threaded operation and thus is generally faster than LRUCache
@@ -466,19 +466,19 @@
size="512"
initialSize="512"
autowarmCount="0"/>
-
+
<!-- Document Cache
Caches Lucene Document objects (the stored fields for each
document). Since Lucene internal document ids are transient,
- this cache will not be autowarmed.
+ this cache will not be autowarmed.
-->
<documentCache class="solr.LRUCache"
size="512"
initialSize="512"
autowarmCount="0"/>
-
- <!-- custom cache currently used by block join -->
+
+ <!-- custom cache currently used by block join -->
<cache name="perSegFilter"
class="solr.search.LRUCache"
size="10"
@@ -487,7 +487,7 @@
regenerator="solr.NoOpRegenerator" />
<!-- Field Value Cache
-
+
Cache used to hold field values that are quickly accessible
by document id. The fieldValueCache is created by default
even if not configured here.
@@ -507,7 +507,7 @@
when running solr to run with ltr enabled:
-Dsolr.ltr.enabled=true
- https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank
+ https://lucene.apache.org/solr/guide/learning-to-rank.html
-->
<cache enable="${solr.ltr.enabled:false}" name="QUERY_DOC_FV"
class="solr.search.LRUCache"
@@ -522,8 +522,8 @@
name through SolrIndexSearcher.getCache(),cacheLookup(), and
cacheInsert(). The purpose is to enable easy caching of
user/application level data. The regenerator argument should
- be specified as an implementation of solr.CacheRegenerator
- if autowarming is desired.
+ be specified as an implementation of solr.CacheRegenerator
+ if autowarming is desired.
-->
<!--
<cache name="myUserCache"
@@ -570,12 +570,12 @@
are collected. For example, if a search for a particular query
requests matching documents 10 through 19, and queryWindowSize is 50,
then documents 0 through 49 will be collected and cached. Any further
- requests in that range can be satisfied via the cache.
+ requests in that range can be satisfied via the cache.
-->
<queryResultWindowSize>20</queryResultWindowSize>
<!-- Maximum number of documents to cache for any entry in the
- queryResultCache.
+ queryResultCache.
-->
<queryResultMaxDocsCached>200</queryResultMaxDocsCached>
@@ -593,10 +593,10 @@
prepared but there is no current registered searcher to handle
requests or to gain autowarming data from.
-
+
-->
<!-- QuerySenderListener takes an array of NamedList and executes a
- local query request for each NamedList in sequence.
+ local query request for each NamedList in sequence.
-->
<listener event="newSearcher" class="solr.QuerySenderListener">
<arr name="queries">
@@ -644,19 +644,19 @@
multipartUploadLimitInKB - specifies the max size (in KiB) of
Multipart File Uploads that Solr will allow in a Request.
-
+
formdataUploadLimitInKB - specifies the max size (in KiB) of
form data (application/x-www-form-urlencoded) sent via
POST. You can use POST to pass request parameters not
fitting into the URL.
-
+
addHttpRequestToContext - if set to true, it will instruct
the requestParsers to include the original HttpServletRequest
- object in the context map of the SolrQueryRequest under the
+ object in the context map of the SolrQueryRequest under the
key "httpRequest". It will not be used by any of the existing
- Solr components, but may be useful when developing custom
+ Solr components, but may be useful when developing custom
plugins.
-
+
*** WARNING ***
Before enabling remote streaming, you should make sure your
system has authentication enabled.
@@ -678,21 +678,21 @@
<!-- If you include a <cacheControl> directive, it will be used to
generate a Cache-Control header (as well as an Expires header
if the value contains "max-age=")
-
+
By default, no Cache-Control header is generated.
-
+
You can use the <cacheControl> option even if you have set
never304="true"
-->
<!--
<httpCaching never304="true" >
- <cacheControl>max-age=30, public</cacheControl>
+ <cacheControl>max-age=30, public</cacheControl>
</httpCaching>
-->
<!-- To enable Solr to respond with automatically generated HTTP
Caching headers, and to response to Cache Validation requests
correctly, set the value of never304="false"
-
+
This will cause Solr to generate Last-Modified and ETag
headers based on the properties of the Index.
@@ -717,12 +717,12 @@
<!--
<httpCaching lastModifiedFrom="openTime"
etagSeed="Solr">
- <cacheControl>max-age=30, public</cacheControl>
+ <cacheControl>max-age=30, public</cacheControl>
</httpCaching>
-->
</requestDispatcher>
- <!-- Request Handlers
+ <!-- Request Handlers
http://wiki.apache.org/solr/SolrRequestHandler
@@ -749,6 +749,12 @@
<lst name="defaults">
<str name="echoParams">explicit</str>
<int name="rows">10</int>
+ <!-- Default search field
+ <str name="df">text</str>
+ -->
+ <!-- Change from JSON to XML format (the default prior to Solr 7.0)
+ <str name="wt">xml</str>
+ -->
<!-- Controls the distribution of a query to shards other than itself.
Consider making 'preferLocalShards' true when:
1) maxShardsPerNode > 1
@@ -830,7 +836,7 @@
</requestHandler>
<!-- A Robust Example
-
+
This example SearchHandler declaration shows off usage of the
SearchHandler with many defaults declared
@@ -911,14 +917,14 @@
<!-- Spell checking defaults -->
<str name="spellcheck">on</str>
- <str name="spellcheck.extendedResults">false</str>
+ <str name="spellcheck.extendedResults">false</str>
<str name="spellcheck.count">5</str>
<str name="spellcheck.alternativeTermCount">2</str>
- <str name="spellcheck.maxResultsForSuggest">5</str>
+ <str name="spellcheck.maxResultsForSuggest">5</str>
<str name="spellcheck.collate">true</str>
- <str name="spellcheck.collateExtendedResults">true</str>
+ <str name="spellcheck.collateExtendedResults">true</str>
<str name="spellcheck.maxCollationTries">5</str>
- <str name="spellcheck.maxCollations">3</str>
+ <str name="spellcheck.maxCollations">3</str>
</lst>
<!-- append spellchecking to our list of components -->
@@ -949,10 +955,10 @@
<!-- Solr Cell Update Request Handler
- http://wiki.apache.org/solr/ExtractingRequestHandler
+ http://wiki.apache.org/solr/ExtractingRequestHandler
-->
- <requestHandler name="/update/extract"
+ <requestHandler name="/update/extract"
startup="lazy"
class="solr.extraction.ExtractingRequestHandler" >
<lst name="defaults">
@@ -968,18 +974,18 @@
<!-- Search Components
- Search components are registered to SolrCore and used by
+ Search components are registered to SolrCore and used by
instances of SearchHandler (which can access them by name)
-
+
By default, the following components are available:
-
+
<searchComponent name="query" class="solr.QueryComponent" />
<searchComponent name="facet" class="solr.FacetComponent" />
<searchComponent name="mlt" class="solr.MoreLikeThisComponent" />
<searchComponent name="highlight" class="solr.HighlightComponent" />
<searchComponent name="stats" class="solr.StatsComponent" />
<searchComponent name="debug" class="solr.DebugComponent" />
-
+
Default configuration in a requestHandler would look like:
<arr name="components">
@@ -991,28 +997,28 @@
<str>debug</str>
</arr>
- If you register a searchComponent to one of the standard names,
+ If you register a searchComponent to one of the standard names,
that will be used instead of the default.
To insert components before or after the 'standard' components, use:
-
+
<arr name="first-components">
<str>myFirstComponentName</str>
</arr>
-
+
<arr name="last-components">
<str>myLastComponentName</str>
</arr>
NOTE: The component registered with the name "debug" will
- always be executed after the "last-components"
-
+ always be executed after the "last-components"
+
-->
-
+
<!-- Spell Check
The spell check component can return a list of alternative spelling
- suggestions.
+ suggestions.
http://wiki.apache.org/solr/SpellCheckComponent
-->
@@ -1047,11 +1053,11 @@
<float name="thresholdTokenFrequency">.01</float>
-->
</lst>
-
+
<!-- a spellchecker that can break or combine words. See "/spell" handler below for usage -->
<lst name="spellchecker">
<str name="name">wordbreak</str>
- <str name="classname">solr.WordBreakSolrSpellChecker</str>
+ <str name="classname">solr.WordBreakSolrSpellChecker</str>
<str name="field">name</str>
<str name="combineWords">true</str>
<str name="breakWords">true</str>
@@ -1070,7 +1076,7 @@
</lst>
-->
- <!-- a spellchecker that use an alternate comparator
+ <!-- a spellchecker that use an alternate comparator
comparatorClass be one of:
1. score (default)
@@ -1096,8 +1102,8 @@
</lst>
-->
</searchComponent>
-
- <!-- A request handler for demonstrating the spellcheck component.
+
+ <!-- A request handler for demonstrating the spellcheck component.
NOTE: This is purely as an example. The whole purpose of the
SpellCheckComponent is to hook it into the request handler that
@@ -1106,7 +1112,7 @@
IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW IS
NOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!
-
+
See http://wiki.apache.org/solr/SpellCheckComponent for details
on the request parameters.
-->
@@ -1119,33 +1125,33 @@
<str name="spellcheck.dictionary">default</str>
<str name="spellcheck.dictionary">wordbreak</str>
<str name="spellcheck">on</str>
- <str name="spellcheck.extendedResults">true</str>
+ <str name="spellcheck.extendedResults">true</str>
<str name="spellcheck.count">10</str>
<str name="spellcheck.alternativeTermCount">5</str>
- <str name="spellcheck.maxResultsForSuggest">5</str>
+ <str name="spellcheck.maxResultsForSuggest">5</str>
<str name="spellcheck.collate">true</str>
- <str name="spellcheck.collateExtendedResults">true</str>
+ <str name="spellcheck.collateExtendedResults">true</str>
<str name="spellcheck.maxCollationTries">10</str>
- <str name="spellcheck.maxCollations">5</str>
+ <str name="spellcheck.maxCollations">5</str>
</lst>
<arr name="last-components">
<str>spellcheck</str>
</arr>
</requestHandler>
- <!-- The SuggestComponent in Solr provides users with automatic suggestions for query terms.
+ <!-- The SuggestComponent in Solr provides users with automatic suggestions for query terms.
You can use this to implement a powerful auto-suggest feature in your search application.
As with the rest of this solrconfig.xml file, the configuration of this component is purely
- an example that applies specifically to this configset and example documents.
-
+ an example that applies specifically to this configset and example documents.
+
More information about this component and other configuration options are described in the
- "Suggester" section of the reference guide available at
+ "Suggester" section of the reference guide available at
http://archive.apache.org/dist/lucene/solr/ref-guide
-->
<searchComponent name="suggest" class="solr.SuggestComponent">
<lst name="suggester">
<str name="name">mySuggester</str>
- <str name="lookupImpl">FuzzyLookupFactory</str>
+ <str name="lookupImpl">FuzzyLookupFactory</str>
<str name="dictionaryImpl">DocumentDictionaryFactory</str>
<str name="field">cat</str>
<str name="weightField">price</str>
@@ -1154,7 +1160,7 @@
</lst>
</searchComponent>
- <requestHandler name="/suggest" class="solr.SearchHandler"
+ <requestHandler name="/suggest" class="solr.SearchHandler"
startup="lazy" >
<lst name="defaults">
<str name="suggest">true</str>
@@ -1176,8 +1182,8 @@
This is purely as an example.
- In reality you will likely want to add the component to your
- already specified request handlers.
+ In reality you will likely want to add the component to your
+ already specified request handlers.
-->
<requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy">
<lst name="defaults">
@@ -1194,7 +1200,7 @@
when running solr to run with clustering enabled:
-Dsolr.clustering.enabled=true
- https://cwiki.apache.org/confluence/display/solr/Result+Clustering
+ https://lucene.apache.org/solr/guide/result-clustering.html
-->
<searchComponent name="clustering"
enable="${solr.clustering.enabled:false}"
@@ -1240,8 +1246,8 @@
<!-- A request handler for demonstrating the clustering component.
This is meant as an example.
- In reality you will likely want to add the component to your
- already specified request handlers.
+ In reality you will likely want to add the component to your
+ already specified request handlers.
-->
<requestHandler name="/clustering"
startup="lazy"
@@ -1291,7 +1297,7 @@
<lst name="defaults">
<bool name="terms">true</bool>
<bool name="distrib">false</bool>
- </lst>
+ </lst>
<arr name="components">
<str>terms</str>
</arr>
@@ -1330,7 +1336,7 @@
<highlighting>
<!-- Configure the standard fragmenter -->
<!-- This could most likely be commented out in the "default" case -->
- <fragmenter name="gap"
+ <fragmenter name="gap"
default="true"
class="solr.highlight.GapFragmenter">
<lst name="defaults">
@@ -1338,10 +1344,10 @@
</lst>
</fragmenter>
- <!-- A regular-expression-based fragmenter
- (for sentence extraction)
+ <!-- A regular-expression-based fragmenter
+ (for sentence extraction)
-->
- <fragmenter name="regex"
+ <fragmenter name="regex"
class="solr.highlight.RegexFragmenter">
<lst name="defaults">
<!-- slightly smaller fragsizes work better because of slop -->
@@ -1354,7 +1360,7 @@
</fragmenter>
<!-- Configure the standard formatter -->
- <formatter name="html"
+ <formatter name="html"
default="true"
class="solr.highlight.HtmlFormatter">
<lst name="defaults">
@@ -1364,27 +1370,27 @@
</formatter>
<!-- Configure the standard encoder -->
- <encoder name="html"
+ <encoder name="html"
class="solr.highlight.HtmlEncoder" />
<!-- Configure the standard fragListBuilder -->
- <fragListBuilder name="simple"
+ <fragListBuilder name="simple"
class="solr.highlight.SimpleFragListBuilder"/>
-
+
<!-- Configure the single fragListBuilder -->
- <fragListBuilder name="single"
+ <fragListBuilder name="single"
class="solr.highlight.SingleFragListBuilder"/>
-
+
<!-- Configure the weighted fragListBuilder -->
- <fragListBuilder name="weighted"
+ <fragListBuilder name="weighted"
default="true"
class="solr.highlight.WeightedFragListBuilder"/>
-
+
<!-- default tag FragmentsBuilder -->
- <fragmentsBuilder name="default"
+ <fragmentsBuilder name="default"
default="true"
class="solr.highlight.ScoreOrderFragmentsBuilder">
- <!--
+ <!--
<lst name="defaults">
<str name="hl.multiValuedSeparatorChar">/</str>
</lst>
@@ -1392,7 +1398,7 @@
</fragmentsBuilder>
<!-- multi-colored tag FragmentsBuilder -->
- <fragmentsBuilder name="colored"
+ <fragmentsBuilder name="colored"
class="solr.highlight.ScoreOrderFragmentsBuilder">
<lst name="defaults">
<str name="hl.tag.pre"><![CDATA[
@@ -1404,8 +1410,8 @@
<str name="hl.tag.post"><![CDATA[</b>]]></str>
</lst>
</fragmentsBuilder>
-
- <boundaryScanner name="default"
+
+ <boundaryScanner name="default"
default="true"
class="solr.highlight.SimpleBoundaryScanner">
<lst name="defaults">
@@ -1413,8 +1419,8 @@
<str name="hl.bs.chars">.,!? 	 </str>
</lst>
</boundaryScanner>
-
- <boundaryScanner name="breakIterator"
+
+ <boundaryScanner name="breakIterator"
class="solr.highlight.BreakIteratorBoundaryScanner">
<lst name="defaults">
<!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE -->
@@ -1436,15 +1442,15 @@
http://wiki.apache.org/solr/UpdateRequestProcessor
- -->
+ -->
<!-- Deduplication
An example dedup update processor that creates the "id" field
on the fly based on the hash code of some other fields. This
example has overwriteDupes set to false since we are using the
id field as the signatureField and Solr will maintain
- uniqueness based on that anyway.
-
+ uniqueness based on that anyway.
+
-->
<!--
<updateRequestProcessorChain name="dedupe">
@@ -1459,7 +1465,7 @@
<processor class="solr.RunUpdateProcessorFactory" />
</updateRequestProcessorChain>
-->
-
+
<!-- Language identification
This example update chain identifies the language of the incoming
@@ -1499,7 +1505,7 @@
<processor class="solr.RunUpdateProcessorFactory" />
</updateRequestProcessorChain>
-->
-
+
<!-- Response Writers
http://wiki.apache.org/solr/QueryResponseWriter
@@ -1515,7 +1521,7 @@
overridden...
-->
<!--
- <queryResponseWriter name="xml"
+ <queryResponseWriter name="xml"
default="true"
class="solr.XMLResponseWriter" />
<queryResponseWriter name="json" class="solr.JSONResponseWriter"/>
@@ -1534,18 +1540,18 @@
-->
<str name="content-type">text/plain; charset=UTF-8</str>
</queryResponseWriter>
-
+
<!--
Custom response writers can be declared as needed...
-->
<queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" startup="lazy">
<str name="template.base.dir">${velocity.template.base.dir:}</str>
</queryResponseWriter>
-
+
<!-- XSLT response writer transforms the XML output by any xslt file found
in Solr's conf/xslt directory. Changes to xslt files are checked for
- every xsltCacheLifetimeSeconds.
+ every xsltCacheLifetimeSeconds.
-->
<queryResponseWriter name="xslt" class="solr.XSLTResponseWriter">
<int name="xsltCacheLifetimeSeconds">5</int>
@@ -1553,7 +1559,7 @@
<!-- Query Parsers
- https://cwiki.apache.org/confluence/display/solr/Query+Syntax+and+Parsing
+ https://lucene.apache.org/solr/guide/query-syntax-and-parsing.html
Multiple QParserPlugins can be registered by name, and then
used in either the "defType" param for the QueryComponent (used
@@ -1573,7 +1579,7 @@
-->
<!-- example of registering a custom function parser -->
<!--
- <valueSourceParser name="myfunc"
+ <valueSourceParser name="myfunc"
class="com.mycompany.MyValueSourceParser" />
-->
@@ -1583,7 +1589,7 @@
when running solr to run with ltr enabled:
-Dsolr.ltr.enabled=true
- https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank
+ https://lucene.apache.org/solr/guide/learning-to-rank.html
Query parser is used to rerank top docs with a provided model
-->
@@ -1597,12 +1603,12 @@
<transformer name="db" class="com.mycompany.LoadFromDatabaseTransformer" >
<int name="connection">jdbc://....</int>
</transformer>
-
+
To add a constant value to all docs, use:
<transformer name="mytrans2" class="org.apache.solr.response.transform.ValueAugmenterFactory" >
<int name="value">5</int>
</transformer>
-
+
If you want the user to still be able to change it with _value:something_ use this:
<transformer name="mytrans3" class="org.apache.solr.response.transform.ValueAugmenterFactory" >
<double name="defaultValue">5</double>
@@ -1624,7 +1630,7 @@
when running solr to run with ltr enabled:
-Dsolr.ltr.enabled=true
- https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank
+ https://lucene.apache.org/solr/guide/learning-to-rank.html
-->
<transformer enable="${solr.ltr.enabled:false}" name="features" class="org.apache.solr.ltr.response.transform.LTRFeatureLoggerTransformerFactory">
<str name="fvCacheName">QUERY_DOC_FV</str>
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/8d00e53b/solr/site/quickstart.mdtext
----------------------------------------------------------------------
diff --git a/solr/site/quickstart.mdtext b/solr/site/quickstart.mdtext
index 3c82adb..fcd9be0 100644
--- a/solr/site/quickstart.mdtext
+++ b/solr/site/quickstart.mdtext
@@ -22,13 +22,15 @@ Note that the base directory name may vary with the version of Solr downloaded.
Cygwin, or MacOS:
/:$ ls solr*
- solr-6.2.0.zip
- /:$ unzip -q solr-6.2.0.zip
- /:$ cd solr-6.2.0/
+ solr-X.Y.Z.zip
+ /:$ unzip -q solr-X.Y.Z.zip
+ /:$ cd solr-X.Y.Z/
+
+Note that "X.Y.Z" will be replaced by an official Solr version (i.e. 6.4.3, 7.0.0, etc.)
To launch Solr, run: `bin/solr start -e cloud -noprompt`
- /solr-6.2.0:$ bin/solr start -e cloud -noprompt
+ /solr-X.Y.Z:$ bin/solr start -e cloud -noprompt
Welcome to the SolrCloud example!
@@ -43,7 +45,7 @@ To launch Solr, run: `bin/solr start -e cloud -noprompt`
SolrCloud example running, please visit http://localhost:8983/solr
- /solr-6.2.0:$ _
+ /solr-X.Y.Z:$ _
You can see that the Solr is running by loading the Solr Admin UI in your web browser: <http://localhost:8983/solr/>.
This is the main starting point for administering Solr.
@@ -79,8 +81,8 @@ subdirectory, so that makes a convenient set of (mostly) HTML files built-in to
Here's what it'll look like:
- /solr-6.2.0:$ bin/post -c gettingstarted docs/
- java -classpath /solr-6.2.0/dist/solr-core-6.2.0.jar -Dauto=yes -Dc=gettingstarted -Ddata=files -Drecursive=yes org.apache.solr.util.SimplePostTool docs/
+ /solr-X.Y.Z:$ bin/post -c gettingstarted docs/
+ java -classpath /solr-X.Y.Z/dist/solr-core-X.Y.Z.jar -Dauto=yes -Dc=gettingstarted -Ddata=files -Drecursive=yes org.apache.solr.util.SimplePostTool docs/
SimplePostTool version 5.0.0
Posting files to [base] url http://localhost:8983/solr/gettingstarted/update...
Entering auto mode. File endings considered are xml,json,jsonl,csv,pdf,doc,docx,ppt,pptx,xls,xlsx,odt,odp,ods,ott,otp,ots,rtf,htm,html,txt,log
@@ -133,8 +135,8 @@ Using `bin/post`, index the example Solr XML files in `example/exampledocs/`:
Here's what you'll see:
- /solr-6.2.0:$ bin/post -c gettingstarted example/exampledocs/*.xml
- java -classpath /solr-6.2.0/dist/solr-core-6.2.0.jar -Dauto=yes -Dc=gettingstarted -Ddata=files org.apache.solr.util.SimplePostTool example/exampledocs/gb18030-example.xml ...
+ /solr-X.Y.Z:$ bin/post -c gettingstarted example/exampledocs/*.xml
+ java -classpath /solr-X.Y.Z/dist/solr-core-X.Y.Z.jar -Dauto=yes -Dc=gettingstarted -Ddata=files org.apache.solr.util.SimplePostTool example/exampledocs/gb18030-example.xml ...
SimplePostTool version 5.0.0
Posting files to [base] url http://localhost:8983/solr/gettingstarted/update...
Entering auto mode. File endings considered are xml,json,jsonl,csv,pdf,doc,docx,ppt,pptx,xls,xlsx,odt,odp,ods,ott,otp,ots,rtf,htm,html,txt,log
@@ -178,8 +180,8 @@ sample JSON file:
You'll see:
- /solr-6.2.0:$ bin/post -c gettingstarted example/exampledocs/books.json
- java -classpath /solr-6.2.0/dist/solr-core-6.2.0.jar -Dauto=yes -Dc=gettingstarted -Ddata=files org.apache.solr.util.SimplePostTool example/exampledocs/books.json
+ /solr-X.Y.Z:$ bin/post -c gettingstarted example/exampledocs/books.json
+ java -classpath /solr-X.Y.Z/dist/solr-core-X.Y.Z.jar -Dauto=yes -Dc=gettingstarted -Ddata=files org.apache.solr.util.SimplePostTool example/exampledocs/books.json
SimplePostTool version 5.0.0
Posting files to [base] url http://localhost:8983/solr/gettingstarted/update...
Entering auto mode. File endings considered are xml,json,jsonl,csv,pdf,doc,docx,ppt,pptx,xls,xlsx,odt,odp,ods,ott,otp,ots,rtf,htm,html,txt,log
@@ -207,8 +209,8 @@ Using `bin/post` index the included example CSV file:
In your terminal you'll see:
- /solr-6.2.0:$ bin/post -c gettingstarted example/exampledocs/books.csv
- java -classpath /solr-6.2.0/dist/solr-core-6.2.0.jar -Dauto=yes -Dc=gettingstarted -Ddata=files org.apache.solr.util.SimplePostTool example/exampledocs/books.csv
+ /solr-X.Y.Z:$ bin/post -c gettingstarted example/exampledocs/books.csv
+ java -classpath /solr-X.Y.Z/dist/solr-core-X.Y.Z.jar -Dauto=yes -Dc=gettingstarted -Ddata=files org.apache.solr.util.SimplePostTool example/exampledocs/books.csv
SimplePostTool version 5.0.0
Posting files to [base] url http://localhost:8983/solr/gettingstarted/update...
Entering auto mode. File endings considered are xml,json,jsonl,csv,pdf,doc,docx,ppt,pptx,xls,xlsx,odt,odp,ods,ott,otp,ots,rtf,htm,html,txt,log
@@ -277,7 +279,7 @@ in the form, you'll get 10 documents in JSON format (`*:*` in the `q` param matc
The URL sent by the Admin UI to Solr is shown in light grey near the top right of the above screenshot - if you click on
it, your browser will show you the raw response. To use cURL, give the same URL in quotes on the `curl` command line:
- curl "http://localhost:8983/solr/gettingstarted/select?indent=on&q=*:*&wt=json"
+ curl "http://localhost:8983/solr/gettingstarted/select?q=*:*"
### Basics
@@ -287,11 +289,11 @@ it, your browser will show you the raw response. To use cURL, give the same URL
To search for a term, give it as the `q` param value in the core-specific Solr Admin UI Query section, replace `*:*`
with the term you want to find. To search for "foundation":
- curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation"
+ curl "http://localhost:8983/solr/gettingstarted/select?q=foundation"
You'll see:
- /solr-6.2.0$ curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation"
+ $ curl "http://localhost:8983/solr/gettingstarted/select?q=foundation"
{
"responseHeader":{
"zkConnected":true,
@@ -315,13 +317,13 @@ default `start=0` and `rows=10`. You can specify these params to page through r
To restrict fields returned in the response, use the `fl` param, which takes a comma-separated list of field names.
E.g. to only return the `id` field:
- curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=foundation&fl=id"
+ curl "http://localhost:8983/solr/gettingstarted/select?q=foundation&fl=id"
`q=foundation` matches nearly all of the docs we've indexed, since most of the files under `docs/` contain
"The Apache Software Foundation". To restrict search to a particular field, use the syntax "`q=field:value`",
e.g. to search for `Foundation` only in the `name` field:
- curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=name:Foundation"
+ curl "http://localhost:8983/solr/gettingstarted/select?q=name:Foundation"
The above request returns only one document (`"numFound":1`) - from the response:
@@ -339,7 +341,7 @@ To search for a multi-term phrase, enclose it in double quotes: `q="multiple ter
"CAS latency" - note that the space between terms must be converted to "`+`" in a URL (the Admin UI will handle URL
encoding for you automatically):
- curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=\"CAS+latency\""
+ curl "http://localhost:8983/solr/gettingstarted/select?indent=true&q=\"CAS+latency\""
You'll get back:
@@ -374,12 +376,12 @@ To find documents that contain both terms "`one`" and "`three`", enter `+one +th
Admin UI Query tab. Because the "`+`" character has a reserved purpose in URLs (encoding the space character),
you must URL encode it for `curl` as "`%2B`":
- curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=%2Bone+%2Bthree"
+ curl "http://localhost:8983/solr/gettingstarted/select?q=%2Bone+%2Bthree"
To search for documents that contain the term "`two`" but **don't** contain the term "`one`", enter `+two -one` in the
`q` param in the Admin UI. Again, URL encode "`+`" as "`%2B`":
- curl "http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=%2Btwo+-one"
+ curl "http://localhost:8983/solr/gettingstarted/select?q=%2Btwo+-one"
#### In depth
@@ -407,7 +409,7 @@ To see facet counts from all documents (`q=*:*`): turn on faceting (`facet=true`
the `facet.field` param. If you only want facets, and no document contents, specify `rows=0`. The `curl` command below
will return facet counts for the `manu_id_s` field:
- curl 'http://localhost:8983/solr/gettingstarted/select?wt=json&indent=true&q=*:*&rows=0'\
+ curl 'http://localhost:8983/solr/gettingstarted/select?q=*:*&rows=0'\
'&facet=true&facet.field=manu_id_s'
In your terminal, you'll see:
@@ -458,7 +460,7 @@ like this:
The data for these price range facets can be seen in JSON format with this command:
- curl 'http://localhost:8983/solr/gettingstarted/select?q=*:*&wt=json&indent=on&rows=0'\
+ curl 'http://localhost:8983/solr/gettingstarted/select?q=*:*&rows=0'\
'&facet=true'\
'&facet.range=price'\
'&f.price.facet.range.start=0'\
@@ -518,8 +520,7 @@ the various possible combinations. Using the example technical product data, pi
of the products in the "book" category (the `cat` field) are in stock or not in stock. Here's how to get at the raw
data for this scenario:
- curl 'http://localhost:8983/solr/gettingstarted/select?q=*:*&rows=0&wt=json&indent=on'\
- '&facet=on&facet.pivot=cat,inStock'
+ curl 'http://localhost:8983/solr/gettingstarted/select?q=*:*&rows=0&facet=on&facet.pivot=cat,inStock'
This results in the following response (trimmed to just the book category output), which says out of 14 items in the
"book" category, 12 are in stock and 2 are not in stock:
http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/8d00e53b/solr/solr-ref-guide/meta-docs/asciidoc-syntax.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/meta-docs/asciidoc-syntax.adoc b/solr/solr-ref-guide/meta-docs/asciidoc-syntax.adoc
deleted file mode 100644
index f8ff2c4..0000000
--- a/solr/solr-ref-guide/meta-docs/asciidoc-syntax.adoc
+++ /dev/null
@@ -1,239 +0,0 @@
-= Asciidoc syntax
-:toc:
-// Licensed to the Apache Software Foundation (ASF) under one
-// or more contributor license agreements. See the NOTICE file
-// distributed with this work for additional information
-// regarding copyright ownership. The ASF licenses this file
-// to you under the Apache License, Version 2.0 (the
-// "License"); you may not use this file except in compliance
-// with the License. You may obtain a copy of the License at
-//
-// http://www.apache.org/licenses/LICENSE-2.0
-//
-// Unless required by applicable law or agreed to in writing,
-// software distributed under the License is distributed on an
-// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-// KIND, either express or implied. See the License for the
-// specific language governing permissions and limitations
-// under the License.
-
-The definitive manual on Asciidoc syntax is in the http://asciidoctor.org/docs/user-manual/[Asciidoctor User Manual]. To help people get started, however, here is a simpler cheat sheet.
-
-== Basic syntax
-
-=== Bold
-
-Put asterisks around text to make it *bold*.
-
-More info: http://asciidoctor.org/docs/user-manual/#bold-and-italic
-
-=== Italics
-
-Use underlines on either side of a string to put text into _italics_.
-
-More info: http://asciidoctor.org/docs/user-manual/#bold-and-italic
-
-=== Headings
-
-Equal signs (`=`) are used for heading levels. Each equal sign is a level. Each page can *only* have one top level. Levels should be appropriately nested.
-
-Validation occurs to ensure that level 3s are preceded by level 2s, level 4s are preceded by level 3s, etc. Including out-of-sequence heading levels (such as a level 3 then a level 5) will not fail the build, but will produce an error.
-
-More info: http://asciidoctor.org/docs/user-manual/#sections
-
-=== Code Examples
-
-Use backticks ``` for text that should be monospaced, such as a code or class name in the body of a paragraph.
-
-More info: http://asciidoctor.org/docs/user-manual/#mono
-
-Longer code examples can be separated from text with `source` blocks. These allow defining the syntax being used so the code is properly highlighted.
-
-[source]
-.Example Source Block
-----
-[source,xml]
- <field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />
-----
-
-If your code block will include line breaks, put 4 hyphens (`----`) before and after the entire block.
-
-More info: http://asciidoctor.org/docs/user-manual/#source-code-blocks
-
-=== Block Titles
-
-Titles can be added to most blocks (images, source blocks, tables, etc.) by simply prefacing the title with a period (`.`). For example, to add a title to the source block example above:
-
-[source]
-----
-[source,xml]
-.Example ID field
- <field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />
-----
-
-== Links
-
-=== Link to Sites on the Internet
-When converting content to HTML or PDF, Asciidoctor will automatically render many link types (such as `http:` and `mailto:`) without any additional syntax.
-
-However, you can add a name to a link by adding the URI followed by square brackets:
-
-[source]
-http://lucene.apache.org/solr[Solr Website]
-
-=== Link to Other Pages/Sections of the Guide
-A warning up front, linking to other pages can be a little bit painful.
-
-To link to an anchor (or heading) on the _same page_, you can simply use double angle brackets (`<< >>`) around the anchor/heading/section name. Note that any heading (aka section title) that starts with equal signs is automatically an anchor.
-
-More info: http://asciidoctor.org/docs/user-manual/#internal-cross-references
-
-To link to another page or even a heading on _another page_, you use a similar syntax, but you must refer to the full filename and refer to the section title you want to link to by changing it to lower case and including hyphens between each word.
-
-For example, if I want to link from one page to the Schema API page's section "Modify the Schema", I need to create a link that looks like this:
-
-[source]
-For more information about modifying the schema with the API, see the section <<schema-api.adoc#modify-the-schema>>.
-
-You can add text to appear by adding it after the file name and section reference, as in:
-
-[source]
-<<schema-api.adoc#modify-the-schema,Modify the Schema>>
-
-More info: http://asciidoctor.org/docs/user-manual/#inter-document-cross-references
-
-== Item Lists
-
-Asciidoc supports three types of lists:
-
-* Unordered lists
-* Ordered lists
-* Labeled lists
-
-Each type of list can be mixed with the other types. So, you could have an ordered list inside a labeled list if necessary.
-
-=== Unordered Lists
-Simple bulleted lists need each line to start with an asterisk (`*`). It should be the first character of the line, and be followed by a space.
-
-More info: http://asciidoctor.org/docs/user-manual/#unordered-lists
-
-=== Ordered Lists
-Numbered lists need each line to start with a period (`.`). It should be the first character of the line, and be followed by a space.
-
-More info: http://asciidoctor.org/docs/user-manual/#ordered-lists
-
-=== Labeled Lists
-These are like question & answer lists or glossary definitions. Each line should start with the list item followed by double colons (`::`), then a space or new line.
-
-Labeled lists can be nested by adding an additional colon (such as `:::`, etc.).
-
-More info: http://asciidoctor.org/docs/user-manual/#labeled-list
-
-== Images
-
-There are two ways to include an image: inline or as a block.
-
-Inline images are those where text will flow around the image. Block images are those that appear on their own line, set off from any other text on the page.
-
-Both approaches use the `image` tag before the image filename, but the number of colons after `image` define if it is inline or a block. Inline images use one colon (`image:`), while block images use two colons (`image::`).
-
-Block images automatically include a caption label and a number (such as `Figure 1`). If a block image includes a title, it will be included as the text of the caption.
-
-Optional attributes allow you to set the alt text, the size of the image, if it should be a link, float and alignment.
-
-More info: http://asciidoctor.org/docs/user-manual/#images
-
-== Tables
-
-Tables can be complex, but it is pretty easy to make a basic table that fits most needs.
-
-=== Basic Tables
-The basic structure of a table is similar to Markdown, with pipes (`|`) delimiting columns between rows:
-
-[source]
-----
-|===
-| col 1 row 1 | col 2 row 1|
-| col 1 row 2 | col 2 row 2|
-|===
-----
-
-Note the use of `|===` at the start and end. For basic tables that's not exactly required, but it does help to delimit the start and end of the table in case you accidentally introduce (or maybe prefer) spaces between the rows.
-
-=== Header Rows
-To add a header to a table, you need only set the `header` attribute at the start of the table:
-
-[source]
-----
-[options="header"]
-|===
-| header col 1 | header col 2|
-| col 1 row 1 | col 2 row 1|
-| col 1 row 2 | col 2 row 2|
-|===
-----
-
-=== Defining Column Styles
-If you need to define specific styles to all rows in a column, you can do so with the attributes.
-
-This example will center all content in all rows:
-
-[source]
-----
-[cols="2*^" options="header"]
-|===
-| header col 1 | header col 2|
-| col 1 row 1 | col 2 row 1|
-| col 1 row 2 | col 2 row 2|
-|===
-----
-
-Alignments or any other styles can be applied only to a specific column. For example, this would only center the last column of the table:
-
-[source]
-----
-[cols="2*,^" options="header"]
-|===
-| header col 1 | header col 2|
-| col 1 row 1 | col 2 row 1|
-| col 1 row 2 | col 2 row 2|
-|===
-----
-
-Many more examples of formatting:
-
-* Columns: http://asciidoctor.org/docs/user-manual/#cols-format
-* Cells: http://asciidoctor.org/docs/user-manual/#cell
-
-=== More Options
-
-Tables can also be given footer rows, borders, and captions. CSV or DSV can be used instead of formatting the data in pipes.
-
-More info: http://asciidoctor.org/docs/user-manual/#tables
-
-== Admonitions (Notes, Warnings)
-
-Asciidoc supports several types of callout boxes, called "admonitions":
-
-* NOTE
-* TIP
-* IMPORTANT
-* CAUTION
-* WARNING
-
-It is enough to start a paragraph with one of these words followed by a colon (such as `NOTE:`). When it is converted to HTML or PDF, those sections will be formatted properly - indented from the main text and showing an icon inline.
-
-You can add titles to admonitions by making it an admonition block. The structure of an admonition block is like this:
-
-[source]
-----
-[NOTE]
-.Title of Note
-====
-Text of note
-====
-----
-
-In this example, the type of admonition is included in square brackets (`[NOTE]`), and the title is prefixed with a period. Four equal signs give the start and end points of the note text (which can include new lines, lists, etc.).
-
-More info: http://asciidoctor.org/docs/user-manual/#admonition