1076 lines
43 KiB
XML
1076 lines
43 KiB
XML
<?xml version="1.0" encoding="UTF-8" ?>
|
|
<!--
|
|
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.
|
|
-->
|
|
|
|
<!--
|
|
For more details about configurations options that may appear in
|
|
this file, see https://solr.apache.org/guide/solr/latest/configuration-guide/configuring-solrconfig-xml.html.
|
|
-->
|
|
<config>
|
|
<!-- In all configuration below, a prefix of "solr." for class names
|
|
is an alias that causes solr to search appropriate packages,
|
|
including org.apache.solr.(search|update|request|core|analysis)
|
|
|
|
You may also specify a fully qualified Java classname if you
|
|
have your own custom plugins.
|
|
-->
|
|
|
|
<!-- Controls what version of Lucene various components of Solr
|
|
adhere to. Generally, you want to use the latest version to
|
|
get all bug fixes and improvements. It is highly recommended
|
|
that you fully re-index after changing this setting as it can
|
|
affect both how text is indexed and queried.
|
|
-->
|
|
<luceneMatchVersion>9.8</luceneMatchVersion>
|
|
|
|
<!-- <lib/> directives can be used to instruct Solr to load any Jars
|
|
identified and use them to resolve any "plugins" specified in
|
|
your solrconfig.xml or schema.xml (ie: Analyzers, Request
|
|
Handlers, etc...).
|
|
|
|
All directories and paths are resolved relative to the
|
|
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"
|
|
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
|
|
to the classpath, this is useful for including all jars in a
|
|
directory.
|
|
|
|
When a 'regex' is specified in addition to a 'dir', only the
|
|
files in that directory which completely match the regex
|
|
(anchored on both ends) will be included.
|
|
|
|
If a 'dir' option (with or without a regex) is used and nothing
|
|
is found that matches, a warning will be logged.
|
|
|
|
The example below can be used to load a Solr Module along
|
|
with their external dependencies.
|
|
-->
|
|
<!-- <lib dir="${solr.install.dir:../../../..}/modules/ltr/lib" regex=".*\.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
|
|
if it can't be loaded.
|
|
-->
|
|
<!--
|
|
<lib path="../a-jar-that-does-not-exist.jar" />
|
|
-->
|
|
|
|
<!-- Data Directory
|
|
|
|
Used to specify an alternate directory to hold all index data
|
|
other than the default ./data under the Solr home. If
|
|
replication is in use, this should match the replication
|
|
configuration.
|
|
-->
|
|
<dataDir>${solr.data.dir:}</dataDir>
|
|
|
|
|
|
<!-- 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,
|
|
wraps solr.StandardDirectoryFactory and caches small files in memory
|
|
for better NRT performance.
|
|
|
|
One can force a particular implementation via solr.MMapDirectoryFactory
|
|
or solr.NIOFSDirectoryFactory.
|
|
|
|
solr.RAMDirectoryFactory is memory based and not persistent.
|
|
-->
|
|
<directoryFactory name="DirectoryFactory"
|
|
class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"/>
|
|
|
|
<!-- The CodecFactory for defining the format of the inverted index.
|
|
The default implementation is SchemaCodecFactory, which is the official Lucene
|
|
index format, but hooks into the schema to provide per-field customization of
|
|
the postings lists and per-document values in the fieldType element
|
|
(postingsFormat/docValuesFormat). Note that most of the alternative implementations
|
|
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
|
|
between the existing compression modes in the default codec: "BEST_SPEED" (default)
|
|
or "BEST_COMPRESSION".
|
|
-->
|
|
<codecFactory class="solr.SchemaCodecFactory"/>
|
|
|
|
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
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.
|
|
<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.
|
|
Default in Lucene is "true". Default in Solr is "false" (since 3.6) -->
|
|
<!-- <useCompoundFile>false</useCompoundFile> -->
|
|
|
|
<!-- ramBufferSizeMB sets the amount of RAM that may be used by Lucene
|
|
indexing for buffering added documents and deletions before they are
|
|
flushed to the Directory.
|
|
maxBufferedDocs sets a limit on the number of documents buffered
|
|
before flushing.
|
|
If both ramBufferSizeMB and maxBufferedDocs is set, then
|
|
Lucene will flush based on whichever limit is hit first. -->
|
|
<!-- <ramBufferSizeMB>100</ramBufferSizeMB> -->
|
|
<!-- <maxBufferedDocs>1000</maxBufferedDocs> -->
|
|
|
|
<!-- Expert: ramPerThreadHardLimitMB sets the maximum amount of RAM that can be consumed
|
|
per thread before they are flushed. When limit is exceeded, this triggers a forced
|
|
flush even if ramBufferSizeMB has not been exceeded.
|
|
This is a safety limit to prevent Lucene's DocumentsWriterPerThread from address space
|
|
exhaustion due to its internal 32 bit signed integer based memory addressing.
|
|
The specified value should be greater than 0 and less than 2048MB. When not specified,
|
|
Solr uses Lucene's default value 1945. -->
|
|
<!-- <ramPerThreadHardLimitMB>1945</ramPerThreadHardLimitMB> -->
|
|
|
|
<!-- 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,
|
|
Even older versions of Lucene used LogDocMergePolicy.
|
|
-->
|
|
<!--
|
|
<mergePolicyFactory class="org.apache.solr.index.TieredMergePolicyFactory">
|
|
<int name="maxMergeAtOnce">10</int>
|
|
<int name="segmentsPerTier">10</int>
|
|
<double name="noCFSRatio">0.1</double>
|
|
</mergePolicyFactory>
|
|
-->
|
|
|
|
<!-- Expert: Merge Scheduler
|
|
The Merge Scheduler in Lucene controls how merges are
|
|
performed. The ConcurrentMergeScheduler (Lucene 2.3 default)
|
|
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
|
|
|
|
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.
|
|
native = NativeFSLockFactory - uses OS native file locking.
|
|
Do not use when multiple solr webapps in the same
|
|
JVM are attempting to share a single index.
|
|
simple = SimpleFSLockFactory - uses a plain file for locking
|
|
|
|
Defaults: 'native' is default for Solr3.6 and later, otherwise
|
|
'simple' is the default
|
|
|
|
More details on the nuances of each LockFactory...
|
|
https://cwiki.apache.org/confluence/display/lucene/AvailableLockFactories
|
|
-->
|
|
<lockType>${solr.lock.type:native}</lockType>
|
|
|
|
<!-- Commit Deletion Policy
|
|
Custom deletion policies can be specified here. The class must
|
|
implement org.apache.lucene.index.IndexDeletionPolicy.
|
|
|
|
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 -->
|
|
<!-- <str name="maxCommitsToKeep">1</str> -->
|
|
<!-- The number of optimized commit points to be kept -->
|
|
<!-- <str name="maxOptimizedCommitsToKeep">0</str> -->
|
|
<!--
|
|
Delete all commit points once they have reached the given age.
|
|
Supports DateMathParser syntax e.g.
|
|
-->
|
|
<!--
|
|
<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.
|
|
|
|
Setting The value to true will instruct the underlying Lucene
|
|
IndexWriter to write its debugging info the specified file
|
|
-->
|
|
<!-- <infoStream file="INFOSTREAM.txt">false</infoStream> -->
|
|
</indexConfig>
|
|
|
|
<!-- The default high-performance update handler -->
|
|
<updateHandler class="solr.DirectUpdateHandler2">
|
|
|
|
<!-- Enables a transaction log, used for real-time get, durability, and
|
|
and solr cloud replica recovery. The log can grow as big as
|
|
uncommitted changes to the index, so use of a hard autoCommit
|
|
is recommended (see below).
|
|
"dir" - the target directory for transaction logs, defaults to the
|
|
solr data directory.
|
|
"numVersionBuckets" - sets the number of buckets used to keep
|
|
track of max version values when checking for re-ordered
|
|
updates; increase this value to reduce the cost of
|
|
synchronizing access to version buckets during high-volume
|
|
indexing, this requires 8 bytes (long) * numVersionBuckets
|
|
of heap space per Solr core.
|
|
-->
|
|
<updateLog>
|
|
<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.
|
|
|
|
https://solr.apache.org/guide/solr/latest/indexing-guide/indexing-with-update-handlers.html
|
|
|
|
maxDocs - Maximum number of documents to add since the last
|
|
commit before automatically triggering a new commit.
|
|
|
|
maxTime - Maximum amount of time in ms that is allowed to pass
|
|
since a document was added before automatically
|
|
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.
|
|
|
|
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>
|
|
|
|
<!-- softAutoCommit is like autoCommit except it causes a
|
|
'soft' commit which only ensures that changes are visible
|
|
but does not ensure that data is synced to disk. This is
|
|
faster and more near-realtime friendly than a hard commit.
|
|
-->
|
|
|
|
<autoSoftCommit>
|
|
<maxTime>${solr.autoSoftCommit.maxTime:3000}</maxTime>
|
|
</autoSoftCommit>
|
|
|
|
<!-- Update Related Event Listeners
|
|
|
|
Various IndexWriter related events can trigger Listeners to
|
|
take actions.
|
|
|
|
postCommit - fired after every commit or optimize command
|
|
postOptimize - fired after every optimize command
|
|
-->
|
|
|
|
</updateHandler>
|
|
|
|
<!-- IndexReaderFactory
|
|
|
|
Use the following format to specify a custom IndexReaderFactory,
|
|
which allows for alternate IndexReader implementations.
|
|
|
|
** Experimental Feature **
|
|
|
|
Please note - Using a custom IndexReaderFactory may prevent
|
|
certain other features from working. The API to
|
|
IndexReaderFactory may change without warning or may even be
|
|
removed from future releases if the problems cannot be
|
|
resolved.
|
|
|
|
|
|
** Features that may not work with custom IndexReaderFactory **
|
|
|
|
The ReplicationHandler assumes a disk-resident index. Using a
|
|
custom IndexReader implementation may cause incompatibility
|
|
with ReplicationHandler and may cause replication to not work
|
|
correctly. See SOLR-1366 for details.
|
|
|
|
-->
|
|
<!--
|
|
<indexReaderFactory name="IndexReaderFactory" class="package.class">
|
|
<str name="someArg">Some Value</str>
|
|
</indexReaderFactory >
|
|
-->
|
|
|
|
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
Query section - these settings control query time things like caches
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
|
|
<query>
|
|
|
|
<!-- Maximum number of clauses allowed when parsing a boolean query string.
|
|
|
|
This limit only impacts boolean queries specified by a user as part of a query string,
|
|
and provides per-collection controls on how complex user specified boolean queries can
|
|
be. Query strings that specify more clauses than this will result in an error.
|
|
|
|
If this per-collection limit is greater than the global `maxBooleanClauses` limit
|
|
specified in `solr.xml`, it will have no effect, as that setting also limits the size
|
|
of user specified boolean queries.
|
|
-->
|
|
<maxBooleanClauses>${solr.max.booleanClauses:1024}</maxBooleanClauses>
|
|
|
|
<!-- Solr Internal Query Caches
|
|
Starting with Solr 9.0 the default cache implementation used is CaffeineCache.
|
|
-->
|
|
|
|
<!-- Filter Cache
|
|
|
|
Cache used by SolrIndexSearcher for filters (DocSets),
|
|
unordered sets of *all* documents that match a query. When a
|
|
new searcher is opened, its caches may be prepopulated or
|
|
"autowarmed" using data from caches in the old searcher.
|
|
autowarmCount is the number of items to prepopulate. For
|
|
CaffeineCache, the autowarmed items will be the most recently
|
|
accessed items.
|
|
|
|
Parameters:
|
|
class - the SolrCache implementation (CaffeineCache by default)
|
|
size - the maximum number of entries in the cache
|
|
initialSize - the initial capacity (number of entries) of
|
|
the cache. (see java.util.HashMap)
|
|
autowarmCount - the number of entries to prepopulate from
|
|
an old cache.
|
|
maxRamMB - the maximum amount of RAM (in MB) that this cache is allowed
|
|
to occupy. Note that when this option is specified, the size
|
|
and initialSize parameters are ignored.
|
|
-->
|
|
<filterCache size="512"
|
|
initialSize="512"
|
|
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 CaffeineCache:
|
|
maxRamMB - the maximum amount of RAM (in MB) that this cache is allowed
|
|
to occupy
|
|
-->
|
|
<queryResultCache 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.
|
|
-->
|
|
<documentCache size="512"
|
|
initialSize="512"
|
|
autowarmCount="0"/>
|
|
|
|
<!-- custom cache currently used by block join -->
|
|
<cache name="perSegFilter"
|
|
class="solr.CaffeineCache"
|
|
size="10"
|
|
initialSize="0"
|
|
autowarmCount="10"
|
|
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.
|
|
-->
|
|
<!--
|
|
<fieldValueCache size="512"
|
|
autowarmCount="128"
|
|
/>
|
|
-->
|
|
|
|
<!-- Custom Cache
|
|
|
|
Example of a generic cache. These caches may be accessed by
|
|
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.
|
|
-->
|
|
<!--
|
|
<cache name="myUserCache"
|
|
class="solr.CaffeineCache"
|
|
size="4096"
|
|
initialSize="1024"
|
|
autowarmCount="1024"
|
|
regenerator="com.mycompany.MyRegenerator"
|
|
/>
|
|
-->
|
|
|
|
|
|
<!-- Lazy Field Loading
|
|
|
|
If true, stored fields that are not requested will be loaded
|
|
lazily. This can result in a significant speed improvement
|
|
if the usual case is to not load all stored fields,
|
|
especially if the skipped fields are large compressed text
|
|
fields.
|
|
-->
|
|
<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"
|
|
-->
|
|
<!--
|
|
<useFilterForSortedQuery>true</useFilterForSortedQuery>
|
|
-->
|
|
|
|
<!-- 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.
|
|
-->
|
|
<queryResultWindowSize>20</queryResultWindowSize>
|
|
|
|
<!-- Maximum number of documents to cache for any entry in the
|
|
queryResultCache.
|
|
-->
|
|
<queryResultMaxDocsCached>200</queryResultMaxDocsCached>
|
|
|
|
<!-- 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"
|
|
-->
|
|
<!--
|
|
<useFilterForSortedQuery>true</useFilterForSortedQuery>
|
|
-->
|
|
|
|
<!-- 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.
|
|
-->
|
|
<listener event="newSearcher" class="solr.QuerySenderListener">
|
|
<arr name="queries">
|
|
<!--
|
|
<lst><str name="q">solr</str><str name="sort">price asc</str></lst>
|
|
<lst><str name="q">rocks</str><str name="sort">weight asc</str></lst>
|
|
-->
|
|
</arr>
|
|
</listener>
|
|
<listener event="firstSearcher" class="solr.QuerySenderListener">
|
|
<arr name="queries">
|
|
<!--
|
|
<lst>
|
|
<str name="q">static firstSearcher warming in solrconfig.xml</str>
|
|
</lst>
|
|
-->
|
|
</arr>
|
|
</listener>
|
|
|
|
<!-- Use Cold Searcher
|
|
|
|
If a search request comes in and there is no current
|
|
registered searcher, then immediately register the still
|
|
warming searcher and use it. If "false" then all requests
|
|
will block until the first searcher is done warming.
|
|
-->
|
|
<useColdSearcher>false</useColdSearcher>
|
|
|
|
</query>
|
|
|
|
<!-- Request Dispatcher
|
|
|
|
This section contains instructions for how the SolrDispatchFilter
|
|
should behave when processing requests for this SolrCore.
|
|
|
|
-->
|
|
<requestDispatcher>
|
|
<!-- Request Parsing
|
|
|
|
These settings indicate how Solr Requests may be parsed, and
|
|
what restrictions may be placed on the ContentStreams from
|
|
those requests
|
|
|
|
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
|
|
key "httpRequest". It will not be used by any of the existing
|
|
Solr components, but may be useful when developing custom
|
|
plugins.
|
|
|
|
<requestParsers multipartUploadLimitInKB="-1"
|
|
formdataUploadLimitInKB="-1"
|
|
addHttpRequestToContext="false"/>
|
|
-->
|
|
|
|
<!-- HTTP Caching
|
|
|
|
Set HTTP caching related parameters (for proxy caches and clients).
|
|
|
|
The options below instruct Solr not to output any HTTP Caching
|
|
related headers
|
|
-->
|
|
<httpCaching never304="true" />
|
|
<!-- 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>
|
|
</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.
|
|
|
|
The following options can also be specified to affect the
|
|
values of these headers...
|
|
|
|
lastModFrom - the default value is "openTime" which means the
|
|
Last-Modified value (and validation against If-Modified-Since
|
|
requests) will all be relative to when the current Searcher
|
|
was opened. You can change it to lastModFrom="dirLastMod" if
|
|
you want the value to exactly correspond to when the physical
|
|
index was last modified.
|
|
|
|
etagSeed="..." is an option you can change to force the ETag
|
|
header (and validation against If-None-Match requests) to be
|
|
different even if the index has not changed (ie: when making
|
|
significant changes to your config file)
|
|
|
|
(lastModifiedFrom and etagSeed are both ignored if you use
|
|
the never304="true" option)
|
|
-->
|
|
<!--
|
|
<httpCaching lastModifiedFrom="openTime"
|
|
etagSeed="Solr">
|
|
<cacheControl>max-age=30, public</cacheControl>
|
|
</httpCaching>
|
|
-->
|
|
</requestDispatcher>
|
|
|
|
<!-- Request Handlers
|
|
|
|
https://solr.apache.org/guide/solr/latest/configuration-guide/requesthandlers-searchcomponents.html
|
|
|
|
Incoming queries will be dispatched to a specific handler by name based on the path specified in the request.
|
|
|
|
All handlers (Search Handlers, Update Request Handlers, and other specialized types) can have default parameters (defaults, appends and invariants).
|
|
|
|
Search Handlers can also (append, prepend or even replace) default or defined Search Components.
|
|
|
|
Update Request Handlers can leverage Update Request Processors to pre-process documents after they are loaded
|
|
and before they are indexed/stored.
|
|
|
|
Not all Request Handlers are defined in the solrconfig.xml, many are implicit.
|
|
-->
|
|
|
|
<!-- Primary search handler, expected by most clients, examples and UI frameworks -->
|
|
<requestHandler name="/select" class="solr.SearchHandler">
|
|
<lst name="defaults">
|
|
<str name="echoParams">explicit</str>
|
|
<int name="rows">10</int>
|
|
</lst>
|
|
</requestHandler>
|
|
|
|
<!-- A request handler that returns indented JSON by default -->
|
|
<requestHandler name="/query" class="solr.SearchHandler">
|
|
<lst name="defaults">
|
|
<str name="echoParams">explicit</str>
|
|
<str name="wt">json</str>
|
|
<str name="indent">true</str>
|
|
</lst>
|
|
</requestHandler>
|
|
|
|
<!-- Shared parameters for multiple Request Handlers -->
|
|
<!--<initParams path="/update/**,/query,/select,/spell">
|
|
<lst name="defaults">
|
|
<str name="df">_text_</str>
|
|
</lst>
|
|
</initParams>-->
|
|
|
|
<!-- Spell Check
|
|
|
|
The spell check component can return a list of alternative spelling
|
|
suggestions.
|
|
|
|
https://solr.apache.org/guide/solr/latest/query-guide/spell-checking.html
|
|
-->
|
|
<searchComponent name="spellcheck" class="solr.SpellCheckComponent">
|
|
|
|
<str name="queryAnalyzerFieldType">text_general</str>
|
|
|
|
<!-- Multiple "Spell Checkers" can be declared and used by this
|
|
component
|
|
-->
|
|
|
|
<!-- a spellchecker built from a field of the main index -->
|
|
<lst name="spellchecker">
|
|
<str name="name">default</str>
|
|
<str name="field">body</str>
|
|
<str name="classname">solr.DirectSolrSpellChecker</str>
|
|
<!-- the spellcheck distance measure used, the default is the internal levenshtein -->
|
|
<str name="distanceMeasure">internal</str>
|
|
<!-- minimum accuracy needed to be considered a valid spellcheck suggestion -->
|
|
<float name="accuracy">0.5</float>
|
|
<!-- the maximum #edits we consider when enumerating terms: can be 1 or 2 -->
|
|
<int name="maxEdits">2</int>
|
|
<!-- the minimum shared prefix when enumerating terms -->
|
|
<int name="minPrefix">1</int>
|
|
<!-- maximum number of inspections per result. -->
|
|
<int name="maxInspections">5</int>
|
|
<!-- minimum length of a query term to be considered for correction -->
|
|
<int name="minQueryLength">4</int>
|
|
<!-- maximum threshold of documents a query term can appear to be considered for correction -->
|
|
<float name="maxQueryFrequency">0.01</float>
|
|
<!-- uncomment this to require suggestions to occur in 1% of the documents
|
|
<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="field">name</str>
|
|
<str name="combineWords">true</str>
|
|
<str name="breakWords">true</str>
|
|
<int name="maxChanges">10</int>
|
|
</lst>
|
|
-->
|
|
</searchComponent>
|
|
|
|
<!-- 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
|
|
handles your normal user queries so that a separate request is
|
|
not needed to get suggestions.
|
|
|
|
IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW IS
|
|
NOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!
|
|
|
|
See https://solr.apache.org/guide/solr/latest/query-guide/spell-checking.html for details
|
|
on the request parameters.
|
|
-->
|
|
<requestHandler name="/spell" class="solr.SearchHandler" startup="lazy">
|
|
<lst name="defaults">
|
|
<!-- Solr will use suggestions from both the 'default' spellchecker
|
|
and from the 'wordbreak' spellchecker and combine them.
|
|
collations (re-written queries) can include a combination of
|
|
corrections from both spellcheckers -->
|
|
<str name="spellcheck.dictionary">default</str>
|
|
<str name="spellcheck">on</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.collate">true</str>
|
|
<str name="spellcheck.collateExtendedResults">true</str>
|
|
<str name="spellcheck.maxCollationTries">10</str>
|
|
<str name="spellcheck.maxCollations">5</str>
|
|
</lst>
|
|
<arr name="last-components">
|
|
<str>spellcheck</str>
|
|
</arr>
|
|
</requestHandler>
|
|
|
|
<!-- Highlighting Component
|
|
|
|
https://solr.apache.org/guide/solr/latest/query-guide/highlighting.html
|
|
-->
|
|
<searchComponent class="solr.HighlightComponent" name="highlight">
|
|
<!-- note: the hl.method=unified highlighter is not configured here; it's completely configured
|
|
via parameters. The below configuration supports hl.method=original and fastVector. -->
|
|
<highlighting>
|
|
<!-- Configure the standard fragmenter -->
|
|
<!-- This could most likely be commented out in the "default" case -->
|
|
<fragmenter name="gap"
|
|
default="true"
|
|
class="solr.highlight.GapFragmenter">
|
|
<lst name="defaults">
|
|
<int name="hl.fragsize">100</int>
|
|
</lst>
|
|
</fragmenter>
|
|
|
|
<!-- A regular-expression-based fragmenter
|
|
(for sentence extraction)
|
|
-->
|
|
<fragmenter name="regex"
|
|
class="solr.highlight.RegexFragmenter">
|
|
<lst name="defaults">
|
|
<!-- slightly smaller fragsizes work better because of slop -->
|
|
<int name="hl.fragsize">70</int>
|
|
<!-- allow 50% slop on fragment sizes -->
|
|
<float name="hl.regex.slop">0.5</float>
|
|
<!-- a basic sentence pattern -->
|
|
<str name="hl.regex.pattern">[-\w ,/\n\"']{20,200}</str>
|
|
</lst>
|
|
</fragmenter>
|
|
|
|
<!-- Configure the standard formatter -->
|
|
<formatter name="html"
|
|
default="true"
|
|
class="solr.highlight.HtmlFormatter">
|
|
<lst name="defaults">
|
|
<str name="hl.simple.pre"><![CDATA[<em>]]></str>
|
|
<str name="hl.simple.post"><![CDATA[</em>]]></str>
|
|
</lst>
|
|
</formatter>
|
|
|
|
<!-- Configure the standard encoder -->
|
|
<encoder name="html"
|
|
class="solr.highlight.HtmlEncoder" />
|
|
|
|
<!-- Configure the standard fragListBuilder -->
|
|
<fragListBuilder name="simple"
|
|
class="solr.highlight.SimpleFragListBuilder"/>
|
|
|
|
<!-- Configure the single fragListBuilder -->
|
|
<fragListBuilder name="single"
|
|
class="solr.highlight.SingleFragListBuilder"/>
|
|
|
|
<!-- Configure the weighted fragListBuilder -->
|
|
<fragListBuilder name="weighted"
|
|
default="true"
|
|
class="solr.highlight.WeightedFragListBuilder"/>
|
|
|
|
<!-- default tag FragmentsBuilder -->
|
|
<fragmentsBuilder name="default"
|
|
default="true"
|
|
class="solr.highlight.ScoreOrderFragmentsBuilder">
|
|
<!--
|
|
<lst name="defaults">
|
|
<str name="hl.multiValuedSeparatorChar">/</str>
|
|
</lst>
|
|
-->
|
|
</fragmentsBuilder>
|
|
|
|
<!-- multi-colored tag FragmentsBuilder -->
|
|
<fragmentsBuilder name="colored"
|
|
class="solr.highlight.ScoreOrderFragmentsBuilder">
|
|
<lst name="defaults">
|
|
<str name="hl.tag.pre"><![CDATA[
|
|
<b style="background:yellow">,<b style="background:lawgreen">,
|
|
<b style="background:aquamarine">,<b style="background:magenta">,
|
|
<b style="background:palegreen">,<b style="background:coral">,
|
|
<b style="background:wheat">,<b style="background:khaki">,
|
|
<b style="background:lime">,<b style="background:deepskyblue">]]></str>
|
|
<str name="hl.tag.post"><![CDATA[</b>]]></str>
|
|
</lst>
|
|
</fragmentsBuilder>
|
|
|
|
<boundaryScanner name="default"
|
|
default="true"
|
|
class="solr.highlight.SimpleBoundaryScanner">
|
|
<lst name="defaults">
|
|
<str name="hl.bs.maxScan">10</str>
|
|
<str name="hl.bs.chars">.,!? 	 </str>
|
|
</lst>
|
|
</boundaryScanner>
|
|
|
|
<boundaryScanner name="breakIterator"
|
|
class="solr.highlight.BreakIteratorBoundaryScanner">
|
|
<lst name="defaults">
|
|
<!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE -->
|
|
<str name="hl.bs.type">WORD</str>
|
|
<!-- language and country are used when constructing Locale object. -->
|
|
<!-- And the Locale object will be used when getting instance of BreakIterator -->
|
|
<str name="hl.bs.language">en</str>
|
|
<str name="hl.bs.country">US</str>
|
|
</lst>
|
|
</boundaryScanner>
|
|
</highlighting>
|
|
</searchComponent>
|
|
|
|
<!-- Update Request Processors
|
|
https://solr.apache.org/guide/solr/latest/configuration-guide/update-request-processors.html
|
|
|
|
Chains or individual Update Request Processor Factories can be declared and referenced
|
|
to preprocess documents sent to Update Request Handlers.
|
|
-->
|
|
|
|
<!-- Add unknown fields to the schema
|
|
|
|
Field type guessing update request 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.
|
|
See the updateRequestProcessorChain defined later for the order they are executed in.
|
|
|
|
These require that the schema is both managed and mutable, by
|
|
declaring schemaFactory as ManagedIndexSchemaFactory, with
|
|
mutable specified as true.
|
|
|
|
See https://solr.apache.org/guide/solr/latest/indexing-guide/schemaless-mode.html for further explanation.
|
|
|
|
-->
|
|
|
|
<updateProcessor class="solr.UUIDUpdateProcessorFactory" name="uuid"/>
|
|
<updateProcessor class="solr.RemoveBlankFieldUpdateProcessorFactory" name="remove-blank"/>
|
|
<updateProcessor class="solr.FieldNameMutatingUpdateProcessorFactory" name="field-name-mutating">
|
|
<str name="pattern">[^\w-\.]</str>
|
|
<str name="replacement">_</str>
|
|
</updateProcessor>
|
|
<updateProcessor class="solr.ParseBooleanFieldUpdateProcessorFactory" name="parse-boolean"/>
|
|
<updateProcessor class="solr.ParseLongFieldUpdateProcessorFactory" name="parse-long"/>
|
|
<updateProcessor class="solr.ParseDoubleFieldUpdateProcessorFactory" name="parse-double"/>
|
|
<updateProcessor class="solr.ParseDateFieldUpdateProcessorFactory" name="parse-date">
|
|
<arr name="format">
|
|
<str>yyyy-MM-dd['T'[HH:mm[:ss[.SSS]][z</str>
|
|
<str>yyyy-MM-dd['T'[HH:mm[:ss[,SSS]][z</str>
|
|
<str>yyyy-MM-dd HH:mm[:ss[.SSS]][z</str>
|
|
<str>yyyy-MM-dd HH:mm[:ss[,SSS]][z</str>
|
|
<str>[EEE, ]dd MMM yyyy HH:mm[:ss] z</str>
|
|
<str>EEEE, dd-MMM-yy HH:mm:ss z</str>
|
|
<str>EEE MMM ppd HH:mm:ss [z ]yyyy</str>
|
|
</arr>
|
|
</updateProcessor>
|
|
<updateProcessor class="solr.AddSchemaFieldsUpdateProcessorFactory" name="add-schema-fields">
|
|
<lst name="typeMapping">
|
|
<str name="valueClass">java.lang.String</str>
|
|
<str name="fieldType">text_general</str>
|
|
<lst name="copyField">
|
|
<str name="dest">*_str</str>
|
|
<int name="maxChars">256</int>
|
|
</lst>
|
|
<!-- Use as default mapping instead of defaultFieldType -->
|
|
<bool name="default">true</bool>
|
|
</lst>
|
|
<lst name="typeMapping">
|
|
<str name="valueClass">java.lang.Boolean</str>
|
|
<str name="fieldType">booleans</str>
|
|
</lst>
|
|
<lst name="typeMapping">
|
|
<str name="valueClass">java.util.Date</str>
|
|
<str name="fieldType">pdates</str>
|
|
</lst>
|
|
<lst name="typeMapping">
|
|
<str name="valueClass">java.lang.Long</str>
|
|
<str name="valueClass">java.lang.Integer</str>
|
|
<str name="fieldType">plongs</str>
|
|
</lst>
|
|
<lst name="typeMapping">
|
|
<str name="valueClass">java.lang.Number</str>
|
|
<str name="fieldType">pdoubles</str>
|
|
</lst>
|
|
</updateProcessor>
|
|
|
|
<!-- The update.autoCreateFields property can be turned to false to disable schemaless mode -->
|
|
<updateRequestProcessorChain name="add-unknown-fields-to-the-schema" default="false"
|
|
processor="uuid,remove-blank,field-name-mutating,parse-boolean,parse-long,parse-double,parse-date,add-schema-fields">
|
|
<processor class="solr.LogUpdateProcessorFactory"/>
|
|
<processor class="solr.DistributedUpdateProcessorFactory"/>
|
|
<processor class="solr.RunUpdateProcessorFactory"/>
|
|
</updateRequestProcessorChain>
|
|
|
|
<!-- Deduplication
|
|
|
|
An example dedup update request processor chain 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.
|
|
|
|
-->
|
|
<!--
|
|
<updateRequestProcessorChain name="dedupe">
|
|
<processor class="solr.processor.SignatureUpdateProcessorFactory">
|
|
<bool name="enabled">true</bool>
|
|
<str name="signatureField">id</str>
|
|
<str name="fields">name,features,cat</str>
|
|
<str name="signatureClass">solr.processor.Lookup3Signature</str>
|
|
</processor>
|
|
<processor class="solr.LogUpdateProcessorFactory" />
|
|
<processor class="solr.RunUpdateProcessorFactory" />
|
|
</updateRequestProcessorChain>
|
|
-->
|
|
|
|
<!-- Response Writers
|
|
|
|
https://solr.apache.org/guide/solr/latest/query-guide/response-writers.html
|
|
|
|
Request responses will be written using the writer specified by
|
|
the 'wt' request parameter matching the name of a registered
|
|
writer.
|
|
|
|
The "default" writer is the default and will be used if 'wt' is
|
|
not specified in the request.
|
|
-->
|
|
<!-- The following response writers are implicitly configured unless
|
|
overridden...
|
|
-->
|
|
<!--
|
|
<queryResponseWriter name="xml"
|
|
default="true"
|
|
class="solr.XMLResponseWriter" />
|
|
<queryResponseWriter name="json" class="solr.JSONResponseWriter"/>
|
|
<queryResponseWriter name="python" class="solr.PythonResponseWriter"/>
|
|
<queryResponseWriter name="ruby" class="solr.RubyResponseWriter"/>
|
|
<queryResponseWriter name="php" class="solr.PHPResponseWriter"/>
|
|
<queryResponseWriter name="phps" class="solr.PHPSerializedResponseWriter"/>
|
|
<queryResponseWriter name="csv" class="solr.CSVResponseWriter"/>
|
|
<queryResponseWriter name="schema.xml" class="solr.SchemaXmlResponseWriter"/>
|
|
-->
|
|
|
|
<!-- Overriding the content-type of the response writer.
|
|
For example, Default content-type of JSON is application/json. This can be overridden to
|
|
text/plain so that response is easy to read in *any* browser.
|
|
-->
|
|
<!--
|
|
<queryResponseWriter name="json" class="solr.JSONResponseWriter">
|
|
<str name="content-type">text/plain; charset=UTF-8</str>
|
|
</queryResponseWriter>
|
|
-->
|
|
|
|
<!-- Query Parsers
|
|
|
|
https://solr.apache.org/guide/solr/latest/query-guide/query-syntax-and-parsers.html
|
|
|
|
Multiple QParserPlugins can be registered by name, and then
|
|
used in either the "defType" param for the QueryComponent (used
|
|
by SearchHandler) or in LocalParams
|
|
-->
|
|
<!-- example of registering a query parser -->
|
|
<!--
|
|
<queryParser name="myparser" class="com.mycompany.MyQParserPlugin"/>
|
|
-->
|
|
|
|
<!-- Function Parsers
|
|
|
|
https://solr.apache.org/guide/solr/latest/query-guide/function-queries.html
|
|
|
|
Multiple ValueSourceParsers can be registered by name, and then
|
|
used as function names when using the "func" QParser.
|
|
-->
|
|
<!-- example of registering a custom function parser -->
|
|
<!--
|
|
<valueSourceParser name="myfunc"
|
|
class="com.mycompany.MyValueSourceParser" />
|
|
-->
|
|
|
|
|
|
<!-- Document Transformers
|
|
https://solr.apache.org/guide/solr/latest/query-guide/document-transformers.html
|
|
-->
|
|
<!--
|
|
Could be something like:
|
|
<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>
|
|
</transformer>
|
|
|
|
If you are using the QueryElevationComponent, you may wish to mark documents that get boosted. The
|
|
EditorialMarkerFactory will do exactly that:
|
|
<transformer name="qecBooster" class="org.apache.solr.response.transform.EditorialMarkerFactory" />
|
|
-->
|
|
</config>
|