"Fossies" - the Fresh Open Source Software Archive

Member "solr-8.4.1/solr/example/example-DIH/solr/solr/conf/solrconfig.xml" (10 Jan 2020, 51927 Bytes) of package /linux/www/solr-8.4.1-src.tgz:


As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) XML source code syntax highlighting (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "solrconfig.xml": 8.4.0_vs_8.4.1.

    1 <?xml version="1.0" encoding="UTF-8" ?>
    2 <!--
    3  Licensed to the Apache Software Foundation (ASF) under one or more
    4  contributor license agreements.  See the NOTICE file distributed with
    5  this work for additional information regarding copyright ownership.
    6  The ASF licenses this file to You under the Apache License, Version 2.0
    7  (the "License"); you may not use this file except in compliance with
    8  the License.  You may obtain a copy of the License at
    9 
   10      http://www.apache.org/licenses/LICENSE-2.0
   11 
   12  Unless required by applicable law or agreed to in writing, software
   13  distributed under the License is distributed on an "AS IS" BASIS,
   14  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   15  See the License for the specific language governing permissions and
   16  limitations under the License.
   17 -->
   18 
   19 <!--
   20      For more details about configurations options that may appear in
   21      this file, see http://wiki.apache.org/solr/SolrConfigXml.
   22 -->
   23 <config>
   24   <!-- In all configuration below, a prefix of "solr." for class names
   25        is an alias that causes solr to search appropriate packages,
   26        including org.apache.solr.(search|update|request|core|analysis)
   27 
   28        You may also specify a fully qualified Java classname if you
   29        have your own custom plugins.
   30     -->
   31 
   32   <!-- Controls what version of Lucene various components of Solr
   33        adhere to.  Generally, you want to use the latest version to
   34        get all bug fixes and improvements. It is highly recommended
   35        that you fully re-index after changing this setting as it can
   36        affect both how text is indexed and queried.
   37   -->
   38   <luceneMatchVersion>8.4.1</luceneMatchVersion>
   39 
   40   <!-- <lib/> directives can be used to instruct Solr to load any Jars
   41        identified and use them to resolve any "plugins" specified in
   42        your solrconfig.xml or schema.xml (ie: Analyzers, Request
   43        Handlers, etc...).
   44 
   45        All directories and paths are resolved relative to the
   46        instanceDir.
   47 
   48        Please note that <lib/> directives are processed in the order
   49        that they appear in your solrconfig.xml file, and are "stacked"
   50        on top of each other when building a ClassLoader - so if you have
   51        plugin jars with dependencies on other jars, the "lower level"
   52        dependency jars should be loaded first.
   53 
   54        If a "./lib" directory exists in your instanceDir, all files
   55        found in it are included as if you had used the following
   56        syntax...
   57 
   58               <lib dir="./lib" />
   59     -->
   60 
   61   <!-- A 'dir' option by itself adds any files found in the directory
   62        to the classpath, this is useful for including all jars in a
   63        directory.
   64 
   65        When a 'regex' is specified in addition to a 'dir', only the
   66        files in that directory which completely match the regex
   67        (anchored on both ends) will be included.
   68 
   69        If a 'dir' option (with or without a regex) is used and nothing
   70        is found that matches, a warning will be logged.
   71 
   72        The examples below can be used to load some solr-contribs along
   73        with their external dependencies.
   74     -->
   75   <lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-dataimporthandler-.*\.jar" />
   76 
   77   <lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib" regex=".*\.jar" />
   78   <lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-cell-\d.*\.jar" />
   79 
   80   <lib dir="${solr.install.dir:../../../..}/contrib/langid/lib/" regex=".*\.jar" />
   81   <lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-langid-\d.*\.jar" />
   82 
   83   <lib dir="${solr.install.dir:../../../..}/contrib/velocity/lib" regex=".*\.jar" />
   84   <lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-velocity-\d.*\.jar" />
   85 
   86   <!-- an exact 'path' can be used instead of a 'dir' to specify a
   87        specific jar file.  This will cause a serious error to be logged
   88        if it can't be loaded.
   89     -->
   90   <!--
   91      <lib path="../a-jar-that-does-not-exist.jar" />
   92   -->
   93 
   94   <!-- Data Directory
   95 
   96        Used to specify an alternate directory to hold all index data
   97        other than the default ./data under the Solr home.  If
   98        replication is in use, this should match the replication
   99        configuration.
  100     -->
  101   <dataDir>${solr.data.dir:}</dataDir>
  102 
  103 
  104   <!-- The DirectoryFactory to use for indexes.
  105 
  106        solr.StandardDirectoryFactory is filesystem
  107        based and tries to pick the best implementation for the current
  108        JVM and platform.  solr.NRTCachingDirectoryFactory, the default,
  109        wraps solr.StandardDirectoryFactory and caches small files in memory
  110        for better NRT performance.
  111 
  112        One can force a particular implementation via solr.MMapDirectoryFactory,
  113        solr.NIOFSDirectoryFactory, or solr.SimpleFSDirectoryFactory.
  114 
  115        solr.RAMDirectoryFactory is memory based and not persistent.
  116     -->
  117   <directoryFactory name="DirectoryFactory"
  118                     class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"/>
  119 
  120   <!-- The CodecFactory for defining the format of the inverted index.
  121        The default implementation is SchemaCodecFactory, which is the official Lucene
  122        index format, but hooks into the schema to provide per-field customization of
  123        the postings lists and per-document values in the fieldType element
  124        (postingsFormat/docValuesFormat). Note that most of the alternative implementations
  125        are experimental, so if you choose to customize the index format, it's a good
  126        idea to convert back to the official format e.g. via IndexWriter.addIndexes(IndexReader)
  127        before upgrading to a newer version to avoid unnecessary reindexing.
  128   -->
  129   <codecFactory class="solr.SchemaCodecFactory"/>
  130 
  131   <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  132        Index Config - These settings control low-level behavior of indexing
  133        Most example settings here show the default value, but are commented
  134        out, to more easily see where customizations have been made.
  135 
  136        Note: This replaces <indexDefaults> and <mainIndex> from older versions
  137        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
  138   <indexConfig>
  139     <!-- maxFieldLength was removed in 4.0. To get similar behavior, include a
  140          LimitTokenCountFilterFactory in your fieldType definition. E.g.
  141      <filter class="solr.LimitTokenCountFilterFactory" maxTokenCount="10000"/>
  142     -->
  143     <!-- Maximum time to wait for a write lock (ms) for an IndexWriter. Default: 1000 -->
  144     <!-- <writeLockTimeout>1000</writeLockTimeout>  -->
  145 
  146     <!-- Expert: Enabling compound file will use less files for the index,
  147          using fewer file descriptors on the expense of performance decrease.
  148          Default in Lucene is "true". Default in Solr is "false" (since 3.6) -->
  149     <!-- <useCompoundFile>false</useCompoundFile> -->
  150 
  151     <!-- ramBufferSizeMB sets the amount of RAM that may be used by Lucene
  152          indexing for buffering added documents and deletions before they are
  153          flushed to the Directory.
  154          maxBufferedDocs sets a limit on the number of documents buffered
  155          before flushing.
  156          If both ramBufferSizeMB and maxBufferedDocs is set, then
  157          Lucene will flush based on whichever limit is hit first.
  158          The default is 100 MB.  -->
  159     <!-- <ramBufferSizeMB>100</ramBufferSizeMB> -->
  160     <!-- <maxBufferedDocs>1000</maxBufferedDocs> -->
  161 
  162     <!-- Expert: Merge Policy
  163          The Merge Policy in Lucene controls how merging of segments is done.
  164          The default since Solr/Lucene 3.3 is TieredMergePolicy.
  165          The default since Lucene 2.3 was the LogByteSizeMergePolicy,
  166          Even older versions of Lucene used LogDocMergePolicy.
  167       -->
  168     <!--
  169         <mergePolicyFactory class="solr.TieredMergePolicyFactory">
  170           <int name="maxMergeAtOnce">10</int>
  171           <int name="segmentsPerTier">10</int>
  172         </mergePolicyFactory>
  173      -->
  174 
  175     <!-- Expert: Merge Scheduler
  176          The Merge Scheduler in Lucene controls how merges are
  177          performed.  The ConcurrentMergeScheduler (Lucene 2.3 default)
  178          can perform merges in the background using separate threads.
  179          The SerialMergeScheduler (Lucene 2.2 default) does not.
  180      -->
  181     <!--
  182        <mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>
  183        -->
  184 
  185     <!-- LockFactory
  186 
  187          This option specifies which Lucene LockFactory implementation
  188          to use.
  189 
  190          single = SingleInstanceLockFactory - suggested for a
  191                   read-only index or when there is no possibility of
  192                   another process trying to modify the index.
  193          native = NativeFSLockFactory - uses OS native file locking.
  194                   Do not use when multiple solr webapps in the same
  195                   JVM are attempting to share a single index.
  196          simple = SimpleFSLockFactory  - uses a plain file for locking
  197 
  198          Defaults: 'native' is default for Solr3.6 and later, otherwise
  199                    'simple' is the default
  200 
  201          More details on the nuances of each LockFactory...
  202          http://wiki.apache.org/lucene-java/AvailableLockFactories
  203     -->
  204     <lockType>${solr.lock.type:native}</lockType>
  205 
  206     <!-- Commit Deletion Policy
  207          Custom deletion policies can be specified here. The class must
  208          implement org.apache.lucene.index.IndexDeletionPolicy.
  209 
  210          The default Solr IndexDeletionPolicy implementation supports
  211          deleting index commit points on number of commits, age of
  212          commit point and optimized status.
  213 
  214          The latest commit point should always be preserved regardless
  215          of the criteria.
  216     -->
  217     <!--
  218     <deletionPolicy class="solr.SolrDeletionPolicy">
  219     -->
  220       <!-- The number of commit points to be kept -->
  221       <!-- <str name="maxCommitsToKeep">1</str> -->
  222       <!-- The number of optimized commit points to be kept -->
  223       <!-- <str name="maxOptimizedCommitsToKeep">0</str> -->
  224       <!--
  225           Delete all commit points once they have reached the given age.
  226           Supports DateMathParser syntax e.g.
  227         -->
  228       <!--
  229          <str name="maxCommitAge">30MINUTES</str>
  230          <str name="maxCommitAge">1DAY</str>
  231       -->
  232     <!--
  233     </deletionPolicy>
  234     -->
  235 
  236     <!-- Lucene Infostream
  237 
  238          To aid in advanced debugging, Lucene provides an "InfoStream"
  239          of detailed information when indexing.
  240 
  241          Setting the value to true will instruct the underlying Lucene
  242          IndexWriter to write its info stream to solr's log. By default,
  243          this is enabled here, and controlled through log4j2.xml
  244       -->
  245      <infoStream>true</infoStream>
  246   </indexConfig>
  247 
  248 
  249   <!-- JMX
  250 
  251        This example enables JMX if and only if an existing MBeanServer
  252        is found, use this if you want to configure JMX through JVM
  253        parameters. Remove this to disable exposing Solr configuration
  254        and statistics to JMX.
  255 
  256        For more details see http://wiki.apache.org/solr/SolrJmx
  257     -->
  258   <jmx />
  259   <!-- If you want to connect to a particular server, specify the
  260        agentId
  261     -->
  262   <!-- <jmx agentId="myAgent" /> -->
  263   <!-- If you want to start a new MBeanServer, specify the serviceUrl -->
  264   <!-- <jmx serviceUrl="service:jmx:rmi:///jndi/rmi://localhost:9999/solr"/>
  265     -->
  266 
  267   <!-- The default high-performance update handler -->
  268   <updateHandler class="solr.DirectUpdateHandler2">
  269 
  270     <!-- Enables a transaction log, used for real-time get, durability, and
  271          and solr cloud replica recovery.  The log can grow as big as
  272          uncommitted changes to the index, so use of a hard autoCommit
  273          is recommended (see below).
  274          "dir" - the target directory for transaction logs, defaults to the
  275                 solr data directory.  -->
  276     <updateLog>
  277       <str name="dir">${solr.ulog.dir:}</str>
  278     </updateLog>
  279 
  280     <!-- AutoCommit
  281 
  282          Perform a hard commit automatically under certain conditions.
  283          Instead of enabling autoCommit, consider using "commitWithin"
  284          when adding documents.
  285 
  286          http://wiki.apache.org/solr/UpdateXmlMessages
  287 
  288          maxDocs - Maximum number of documents to add since the last
  289                    commit before automatically triggering a new commit.
  290 
  291          maxTime - Maximum amount of time in ms that is allowed to pass
  292                    since a document was added before automatically
  293                    triggering a new commit.
  294          openSearcher - if false, the commit causes recent index changes
  295            to be flushed to stable storage, but does not cause a new
  296            searcher to be opened to make those changes visible.
  297 
  298          If the updateLog is enabled, then it's highly recommended to
  299          have some sort of hard autoCommit to limit the log size.
  300       -->
  301      <autoCommit>
  302        <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
  303        <openSearcher>false</openSearcher>
  304      </autoCommit>
  305 
  306     <!-- softAutoCommit is like autoCommit except it causes a
  307          'soft' commit which only ensures that changes are visible
  308          but does not ensure that data is synced to disk.  This is
  309          faster and more near-realtime friendly than a hard commit.
  310       -->
  311 
  312      <autoSoftCommit>
  313        <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime>
  314      </autoSoftCommit>
  315 
  316     <!-- Update Related Event Listeners
  317 
  318          Various IndexWriter related events can trigger Listeners to
  319          take actions.
  320 
  321          postCommit - fired after every commit or optimize command
  322          postOptimize - fired after every optimize command
  323       -->
  324 
  325   </updateHandler>
  326 
  327   <!-- IndexReaderFactory
  328 
  329        Use the following format to specify a custom IndexReaderFactory,
  330        which allows for alternate IndexReader implementations.
  331 
  332        ** Experimental Feature **
  333 
  334        Please note - Using a custom IndexReaderFactory may prevent
  335        certain other features from working. The API to
  336        IndexReaderFactory may change without warning or may even be
  337        removed from future releases if the problems cannot be
  338        resolved.
  339 
  340 
  341        ** Features that may not work with custom IndexReaderFactory **
  342 
  343        The ReplicationHandler assumes a disk-resident index. Using a
  344        custom IndexReader implementation may cause incompatibility
  345        with ReplicationHandler and may cause replication to not work
  346        correctly. See SOLR-1366 for details.
  347 
  348     -->
  349   <!--
  350   <indexReaderFactory name="IndexReaderFactory" class="package.class">
  351     <str name="someArg">Some Value</str>
  352   </indexReaderFactory >
  353   -->
  354 
  355   <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  356        Query section - these settings control query time things like caches
  357        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
  358   <query>
  359     <!-- Max Boolean Clauses
  360 
  361          Maximum number of clauses in each BooleanQuery,  an exception
  362          is thrown if exceeded.
  363 
  364          ** WARNING **
  365 
  366          This option actually modifies a global Lucene property that
  367          will affect all SolrCores.  If multiple solrconfig.xml files
  368          disagree on this property, the value at any given moment will
  369          be based on the last SolrCore to be initialized.
  370 
  371       -->
  372     <maxBooleanClauses>${solr.max.booleanClauses:1024}</maxBooleanClauses>
  373 
  374 
  375     <!-- Solr Internal Query Caches
  376 
  377          There are two implementations of cache available for Solr,
  378          LRUCache, based on a synchronized LinkedHashMap, and
  379          FastLRUCache, based on a ConcurrentHashMap.
  380 
  381          FastLRUCache has faster gets and slower puts in single
  382          threaded operation and thus is generally faster than LRUCache
  383          when the hit ratio of the cache is high (> 75%), and may be
  384          faster under other scenarios on multi-cpu systems.
  385     -->
  386 
  387     <!-- Filter Cache
  388 
  389          Cache used by SolrIndexSearcher for filters (DocSets),
  390          unordered sets of *all* documents that match a query.  When a
  391          new searcher is opened, its caches may be prepopulated or
  392          "autowarmed" using data from caches in the old searcher.
  393          autowarmCount is the number of items to prepopulate.  For
  394          LRUCache, the autowarmed items will be the most recently
  395          accessed items.
  396 
  397          Parameters:
  398            class - the SolrCache implementation LRUCache or
  399                (LRUCache or FastLRUCache)
  400            size - the maximum number of entries in the cache
  401            initialSize - the initial capacity (number of entries) of
  402                the cache.  (see java.util.HashMap)
  403            autowarmCount - the number of entries to prepopulate from
  404                and old cache.
  405       -->
  406     <filterCache class="solr.FastLRUCache"
  407                  size="512"
  408                  initialSize="512"
  409                  autowarmCount="0"/>
  410 
  411     <!-- Query Result Cache
  412 
  413          Caches results of searches - ordered lists of document ids
  414          (DocList) based on a query, a sort, and the range of documents requested.
  415       -->
  416     <queryResultCache class="solr.LRUCache"
  417                      size="512"
  418                      initialSize="512"
  419                      autowarmCount="0"/>
  420 
  421     <!-- Document Cache
  422 
  423          Caches Lucene Document objects (the stored fields for each
  424          document).  Since Lucene internal document ids are transient,
  425          this cache will not be autowarmed.
  426       -->
  427     <documentCache class="solr.LRUCache"
  428                    size="512"
  429                    initialSize="512"
  430                    autowarmCount="0"/>
  431 
  432     <!-- custom cache currently used by block join -->
  433     <cache name="perSegFilter"
  434       class="solr.search.LRUCache"
  435       size="10"
  436       initialSize="0"
  437       autowarmCount="10"
  438       regenerator="solr.NoOpRegenerator" />
  439 
  440     <!-- Field Value Cache
  441 
  442          Cache used to hold field values that are quickly accessible
  443          by document id.  The fieldValueCache is created by default
  444          even if not configured here.
  445       -->
  446     <!--
  447        <fieldValueCache class="solr.FastLRUCache"
  448                         size="512"
  449                         autowarmCount="128"
  450                         showItems="32" />
  451       -->
  452 
  453     <!-- Custom Cache
  454 
  455          Example of a generic cache.  These caches may be accessed by
  456          name through SolrIndexSearcher.getCache(),cacheLookup(), and
  457          cacheInsert().  The purpose is to enable easy caching of
  458          user/application level data.  The regenerator argument should
  459          be specified as an implementation of solr.CacheRegenerator
  460          if autowarming is desired.
  461       -->
  462     <!--
  463        <cache name="myUserCache"
  464               class="solr.LRUCache"
  465               size="4096"
  466               initialSize="1024"
  467               autowarmCount="1024"
  468               regenerator="com.mycompany.MyRegenerator"
  469               />
  470       -->
  471 
  472 
  473     <!-- Lazy Field Loading
  474 
  475          If true, stored fields that are not requested will be loaded
  476          lazily.  This can result in a significant speed improvement
  477          if the usual case is to not load all stored fields,
  478          especially if the skipped fields are large compressed text
  479          fields.
  480     -->
  481     <enableLazyFieldLoading>true</enableLazyFieldLoading>
  482 
  483    <!-- Use Filter For Sorted Query
  484 
  485         A possible optimization that attempts to use a filter to
  486         satisfy a search.  If the requested sort does not include
  487         score, then the filterCache will be checked for a filter
  488         matching the query. If found, the filter will be used as the
  489         source of document ids, and then the sort will be applied to
  490         that.
  491 
  492         For most situations, this will not be useful unless you
  493         frequently get the same search repeatedly with different sort
  494         options, and none of them ever use "score"
  495      -->
  496    <!--
  497       <useFilterForSortedQuery>true</useFilterForSortedQuery>
  498      -->
  499 
  500    <!-- Result Window Size
  501 
  502         An optimization for use with the queryResultCache.  When a search
  503         is requested, a superset of the requested number of document ids
  504         are collected.  For example, if a search for a particular query
  505         requests matching documents 10 through 19, and queryWindowSize is 50,
  506         then documents 0 through 49 will be collected and cached.  Any further
  507         requests in that range can be satisfied via the cache.
  508      -->
  509    <queryResultWindowSize>20</queryResultWindowSize>
  510 
  511    <!-- Maximum number of documents to cache for any entry in the
  512         queryResultCache.
  513      -->
  514    <queryResultMaxDocsCached>200</queryResultMaxDocsCached>
  515 
  516    <!-- Query Related Event Listeners
  517 
  518         Various IndexSearcher related events can trigger Listeners to
  519         take actions.
  520 
  521         newSearcher - fired whenever a new searcher is being prepared
  522         and there is a current searcher handling requests (aka
  523         registered).  It can be used to prime certain caches to
  524         prevent long request times for certain requests.
  525 
  526         firstSearcher - fired whenever a new searcher is being
  527         prepared but there is no current registered searcher to handle
  528         requests or to gain autowarming data from.
  529 
  530 
  531      -->
  532     <!-- QuerySenderListener takes an array of NamedList and executes a
  533          local query request for each NamedList in sequence.
  534       -->
  535     <listener event="newSearcher" class="solr.QuerySenderListener">
  536       <arr name="queries">
  537         <!--
  538            <lst><str name="q">solr</str><str name="sort">price asc</str></lst>
  539            <lst><str name="q">rocks</str><str name="sort">weight asc</str></lst>
  540           -->
  541       </arr>
  542     </listener>
  543     <listener event="firstSearcher" class="solr.QuerySenderListener">
  544       <arr name="queries">
  545         <lst>
  546           <str name="q">static firstSearcher warming in solrconfig.xml</str>
  547         </lst>
  548       </arr>
  549     </listener>
  550 
  551     <!-- Use Cold Searcher
  552 
  553          If a search request comes in and there is no current
  554          registered searcher, then immediately register the still
  555          warming searcher and use it.  If "false" then all requests
  556          will block until the first searcher is done warming.
  557       -->
  558     <useColdSearcher>false</useColdSearcher>
  559 
  560   </query>
  561 
  562 
  563   <!-- Request Dispatcher
  564 
  565        This section contains instructions for how the SolrDispatchFilter
  566        should behave when processing requests for this SolrCore.
  567     -->
  568   <requestDispatcher>
  569     <!-- Request Parsing
  570 
  571          These settings indicate how Solr Requests may be parsed, and
  572          what restrictions may be placed on the ContentStreams from
  573          those requests
  574 
  575          enableRemoteStreaming - enables use of the stream.file
  576          and stream.url parameters for specifying remote streams.
  577 
  578          multipartUploadLimitInKB - specifies the max size (in KiB) of
  579          Multipart File Uploads that Solr will allow in a Request.
  580 
  581          formdataUploadLimitInKB - specifies the max size (in KiB) of
  582          form data (application/x-www-form-urlencoded) sent via
  583          POST. You can use POST to pass request parameters not
  584          fitting into the URL.
  585 
  586          addHttpRequestToContext - if set to true, it will instruct
  587          the requestParsers to include the original HttpServletRequest
  588          object in the context map of the SolrQueryRequest under the
  589          key "httpRequest". It will not be used by any of the existing
  590          Solr components, but may be useful when developing custom
  591          plugins.
  592 
  593          *** WARNING ***
  594          Before enabling remote streaming, you should make sure your
  595          system has authentication enabled.
  596 
  597     <requestParsers enableRemoteStreaming="false"
  598                     multipartUploadLimitInKB="-1"
  599                     formdataUploadLimitInKB="-1"
  600                     addHttpRequestToContext="false"/>
  601       -->
  602 
  603     <!-- HTTP Caching
  604 
  605          Set HTTP caching related parameters (for proxy caches and clients).
  606 
  607          The options below instruct Solr not to output any HTTP Caching
  608          related headers
  609       -->
  610     <httpCaching never304="true" />
  611     <!-- If you include a <cacheControl> directive, it will be used to
  612          generate a Cache-Control header (as well as an Expires header
  613          if the value contains "max-age=")
  614 
  615          By default, no Cache-Control header is generated.
  616 
  617          You can use the <cacheControl> option even if you have set
  618          never304="true"
  619       -->
  620     <!--
  621        <httpCaching never304="true" >
  622          <cacheControl>max-age=30, public</cacheControl>
  623        </httpCaching>
  624       -->
  625     <!-- To enable Solr to respond with automatically generated HTTP
  626          Caching headers, and to response to Cache Validation requests
  627          correctly, set the value of never304="false"
  628 
  629          This will cause Solr to generate Last-Modified and ETag
  630          headers based on the properties of the Index.
  631 
  632          The following options can also be specified to affect the
  633          values of these headers...
  634 
  635          lastModFrom - the default value is "openTime" which means the
  636          Last-Modified value (and validation against If-Modified-Since
  637          requests) will all be relative to when the current Searcher
  638          was opened.  You can change it to lastModFrom="dirLastMod" if
  639          you want the value to exactly correspond to when the physical
  640          index was last modified.
  641 
  642          etagSeed="..." is an option you can change to force the ETag
  643          header (and validation against If-None-Match requests) to be
  644          different even if the index has not changed (ie: when making
  645          significant changes to your config file)
  646 
  647          (lastModifiedFrom and etagSeed are both ignored if you use
  648          the never304="true" option)
  649       -->
  650     <!--
  651        <httpCaching lastModifiedFrom="openTime"
  652                     etagSeed="Solr">
  653          <cacheControl>max-age=30, public</cacheControl>
  654        </httpCaching>
  655       -->
  656   </requestDispatcher>
  657 
  658   <!-- Request Handlers
  659 
  660        http://wiki.apache.org/solr/SolrRequestHandler
  661 
  662        Incoming queries will be dispatched to a specific handler by name
  663        based on the path specified in the request.
  664 
  665        If a Request Handler is declared with startup="lazy", then it will
  666        not be initialized until the first request that uses it.
  667 
  668     -->
  669 
  670   <requestHandler name="/dataimport" class="solr.DataImportHandler">
  671     <lst name="defaults">
  672       <str name="config">solr-data-config.xml</str>
  673     </lst>
  674   </requestHandler>
  675 
  676   <!-- SearchHandler
  677 
  678        http://wiki.apache.org/solr/SearchHandler
  679 
  680        For processing Search Queries, the primary Request Handler
  681        provided with Solr is "SearchHandler" It delegates to a sequent
  682        of SearchComponents (see below) and supports distributed
  683        queries across multiple shards
  684     -->
  685   <requestHandler name="/select" class="solr.SearchHandler">
  686     <!-- default values for query parameters can be specified, these
  687          will be overridden by parameters in the request
  688       -->
  689      <lst name="defaults">
  690        <str name="echoParams">explicit</str>
  691        <int name="rows">10</int>
  692        <str name="df">text</str>
  693        <!-- Change from JSON to XML format (the default prior to Solr 7.0)
  694           <str name="wt">xml</str> 
  695          -->
  696      </lst>
  697     <!-- In addition to defaults, "appends" params can be specified
  698          to identify values which should be appended to the list of
  699          multi-val params from the query (or the existing "defaults").
  700       -->
  701     <!-- In this example, the param "fq=instock:true" would be appended to
  702          any query time fq params the user may specify, as a mechanism for
  703          partitioning the index, independent of any user selected filtering
  704          that may also be desired (perhaps as a result of faceted searching).
  705 
  706          NOTE: there is *absolutely* nothing a client can do to prevent these
  707          "appends" values from being used, so don't use this mechanism
  708          unless you are sure you always want it.
  709       -->
  710     <!--
  711        <lst name="appends">
  712          <str name="fq">inStock:true</str>
  713        </lst>
  714       -->
  715     <!-- "invariants" are a way of letting the Solr maintainer lock down
  716          the options available to Solr clients.  Any params values
  717          specified here are used regardless of what values may be specified
  718          in either the query, the "defaults", or the "appends" params.
  719 
  720          In this example, the facet.field and facet.query params would
  721          be fixed, limiting the facets clients can use.  Faceting is
  722          not turned on by default - but if the client does specify
  723          facet=true in the request, these are the only facets they
  724          will be able to see counts for; regardless of what other
  725          facet.field or facet.query params they may specify.
  726 
  727          NOTE: there is *absolutely* nothing a client can do to prevent these
  728          "invariants" values from being used, so don't use this mechanism
  729          unless you are sure you always want it.
  730       -->
  731     <!--
  732        <lst name="invariants">
  733          <str name="facet.field">cat</str>
  734          <str name="facet.field">manu_exact</str>
  735          <str name="facet.query">price:[* TO 500]</str>
  736          <str name="facet.query">price:[500 TO *]</str>
  737        </lst>
  738       -->
  739     <!-- If the default list of SearchComponents is not desired, that
  740          list can either be overridden completely, or components can be
  741          prepended or appended to the default list.  (see below)
  742       -->
  743     <!--
  744        <arr name="components">
  745          <str>nameOfCustomComponent1</str>
  746          <str>nameOfCustomComponent2</str>
  747        </arr>
  748       -->
  749     </requestHandler>
  750 
  751   <!-- A request handler that returns indented JSON by default -->
  752   <requestHandler name="/query" class="solr.SearchHandler">
  753      <lst name="defaults">
  754        <str name="echoParams">explicit</str>
  755        <str name="wt">json</str>
  756        <str name="indent">true</str>
  757        <str name="df">text</str>
  758      </lst>
  759   </requestHandler>
  760 
  761   <!-- A Robust Example
  762 
  763        This example SearchHandler declaration shows off usage of the
  764        SearchHandler with many defaults declared
  765 
  766        Note that multiple instances of the same Request Handler
  767        (SearchHandler) can be registered multiple times with different
  768        names (and different init parameters)
  769     -->
  770   <requestHandler name="/browse" class="solr.SearchHandler">
  771     <lst name="defaults">
  772       <str name="echoParams">explicit</str>
  773 
  774       <!-- VelocityResponseWriter settings -->
  775       <str name="wt">velocity</str>
  776       <str name="v.template">browse</str>
  777       <str name="v.layout">layout</str>
  778 
  779       <!-- Query settings -->
  780       <str name="defType">edismax</str>
  781       <str name="q.alt">*:*</str>
  782       <str name="rows">10</str>
  783       <str name="fl">*,score</str>
  784 
  785       <!-- Faceting defaults -->
  786       <str name="facet">on</str>
  787       <str name="facet.mincount">1</str>
  788     </lst>
  789   </requestHandler>
  790 
  791   <initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse">
  792     <lst name="defaults">
  793       <str name="df">text</str>
  794     </lst>
  795   </initParams>
  796 
  797   <!-- Solr Cell Update Request Handler
  798 
  799        http://wiki.apache.org/solr/ExtractingRequestHandler
  800 
  801     -->
  802   <requestHandler name="/update/extract"
  803                   startup="lazy"
  804                   class="solr.extraction.ExtractingRequestHandler" >
  805     <lst name="defaults">
  806       <str name="lowernames">true</str>
  807       <str name="uprefix">ignored_</str>
  808 
  809       <!-- capture link hrefs but ignore div attributes -->
  810       <str name="captureAttr">true</str>
  811       <str name="fmap.a">links</str>
  812       <str name="fmap.div">ignored_</str>
  813     </lst>
  814   </requestHandler>
  815   <!-- Search Components
  816 
  817        Search components are registered to SolrCore and used by
  818        instances of SearchHandler (which can access them by name)
  819 
  820        By default, the following components are available:
  821 
  822        <searchComponent name="query"     class="solr.QueryComponent" />
  823        <searchComponent name="facet"     class="solr.FacetComponent" />
  824        <searchComponent name="mlt"       class="solr.MoreLikeThisComponent" />
  825        <searchComponent name="highlight" class="solr.HighlightComponent" />
  826        <searchComponent name="stats"     class="solr.StatsComponent" />
  827        <searchComponent name="debug"     class="solr.DebugComponent" />
  828 
  829        Default configuration in a requestHandler would look like:
  830 
  831        <arr name="components">
  832          <str>query</str>
  833          <str>facet</str>
  834          <str>mlt</str>
  835          <str>highlight</str>
  836          <str>stats</str>
  837          <str>debug</str>
  838        </arr>
  839 
  840        If you register a searchComponent to one of the standard names,
  841        that will be used instead of the default.
  842 
  843        To insert components before or after the 'standard' components, use:
  844 
  845        <arr name="first-components">
  846          <str>myFirstComponentName</str>
  847        </arr>
  848 
  849        <arr name="last-components">
  850          <str>myLastComponentName</str>
  851        </arr>
  852 
  853        NOTE: The component registered with the name "debug" will
  854        always be executed after the "last-components"
  855 
  856      -->
  857 
  858    <!-- Spell Check
  859 
  860         The spell check component can return a list of alternative spelling
  861         suggestions.
  862 
  863         http://wiki.apache.org/solr/SpellCheckComponent
  864      -->
  865   <searchComponent name="spellcheck" class="solr.SpellCheckComponent">
  866 
  867     <str name="queryAnalyzerFieldType">text_general</str>
  868 
  869     <!-- Multiple "Spell Checkers" can be declared and used by this
  870          component
  871       -->
  872 
  873     <!-- a spellchecker built from a field of the main index -->
  874     <lst name="spellchecker">
  875       <str name="name">default</str>
  876       <str name="field">text</str>
  877       <str name="classname">solr.DirectSolrSpellChecker</str>
  878       <!-- the spellcheck distance measure used, the default is the internal levenshtein -->
  879       <str name="distanceMeasure">internal</str>
  880       <!-- minimum accuracy needed to be considered a valid spellcheck suggestion -->
  881       <float name="accuracy">0.5</float>
  882       <!-- the maximum #edits we consider when enumerating terms: can be 1 or 2 -->
  883       <int name="maxEdits">2</int>
  884       <!-- the minimum shared prefix when enumerating terms -->
  885       <int name="minPrefix">1</int>
  886       <!-- maximum number of inspections per result. -->
  887       <int name="maxInspections">5</int>
  888       <!-- minimum length of a query term to be considered for correction -->
  889       <int name="minQueryLength">4</int>
  890       <!-- maximum threshold of documents a query term can appear to be considered for correction -->
  891       <float name="maxQueryFrequency">0.01</float>
  892       <!-- uncomment this to require suggestions to occur in 1% of the documents
  893         <float name="thresholdTokenFrequency">.01</float>
  894       -->
  895     </lst>
  896 
  897     <!-- a spellchecker that can break or combine words.  See "/spell" handler below for usage -->
  898     <lst name="spellchecker">
  899       <str name="name">wordbreak</str>
  900       <str name="classname">solr.WordBreakSolrSpellChecker</str>
  901       <str name="field">name</str>
  902       <str name="combineWords">true</str>
  903       <str name="breakWords">true</str>
  904       <int name="maxChanges">10</int>
  905     </lst>
  906 
  907     <!-- a spellchecker that uses a different distance measure -->
  908     <!--
  909        <lst name="spellchecker">
  910          <str name="name">jarowinkler</str>
  911          <str name="field">spell</str>
  912          <str name="classname">solr.DirectSolrSpellChecker</str>
  913          <str name="distanceMeasure">
  914            org.apache.lucene.search.spell.JaroWinklerDistance
  915          </str>
  916        </lst>
  917      -->
  918 
  919     <!-- a spellchecker that use an alternate comparator
  920 
  921          comparatorClass be one of:
  922           1. score (default)
  923           2. freq (Frequency first, then score)
  924           3. A fully qualified class name
  925       -->
  926     <!--
  927        <lst name="spellchecker">
  928          <str name="name">freq</str>
  929          <str name="field">lowerfilt</str>
  930          <str name="classname">solr.DirectSolrSpellChecker</str>
  931          <str name="comparatorClass">freq</str>
  932       -->
  933 
  934     <!-- A spellchecker that reads the list of words from a file -->
  935     <!--
  936        <lst name="spellchecker">
  937          <str name="classname">solr.FileBasedSpellChecker</str>
  938          <str name="name">file</str>
  939          <str name="sourceLocation">spellings.txt</str>
  940          <str name="characterEncoding">UTF-8</str>
  941          <str name="spellcheckIndexDir">spellcheckerFile</str>
  942        </lst>
  943       -->
  944   </searchComponent>
  945 
  946   <!-- A request handler for demonstrating the spellcheck component.
  947 
  948        NOTE: This is purely as an example.  The whole purpose of the
  949        SpellCheckComponent is to hook it into the request handler that
  950        handles your normal user queries so that a separate request is
  951        not needed to get suggestions.
  952 
  953        IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW IS
  954        NOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!
  955 
  956        See http://wiki.apache.org/solr/SpellCheckComponent for details
  957        on the request parameters.
  958     -->
  959   <requestHandler name="/spell" class="solr.SearchHandler" startup="lazy">
  960     <lst name="defaults">
  961       <str name="df">text</str>
  962       <!-- Solr will use suggestions from both the 'default' spellchecker
  963            and from the 'wordbreak' spellchecker and combine them.
  964            collations (re-written queries) can include a combination of
  965            corrections from both spellcheckers -->
  966       <str name="spellcheck.dictionary">default</str>
  967       <str name="spellcheck.dictionary">wordbreak</str>
  968       <str name="spellcheck">on</str>
  969       <str name="spellcheck.extendedResults">true</str>
  970       <str name="spellcheck.count">10</str>
  971       <str name="spellcheck.alternativeTermCount">5</str>
  972       <str name="spellcheck.maxResultsForSuggest">5</str>
  973       <str name="spellcheck.collate">true</str>
  974       <str name="spellcheck.collateExtendedResults">true</str>
  975       <str name="spellcheck.maxCollationTries">10</str>
  976       <str name="spellcheck.maxCollations">5</str>
  977     </lst>
  978     <arr name="last-components">
  979       <str>spellcheck</str>
  980     </arr>
  981   </requestHandler>
  982 
  983   <searchComponent name="suggest" class="solr.SuggestComponent">
  984     <lst name="suggester">
  985       <str name="name">mySuggester</str>
  986       <str name="lookupImpl">FuzzyLookupFactory</str>      <!-- org.apache.solr.spelling.suggest.fst -->
  987       <str name="dictionaryImpl">DocumentDictionaryFactory</str>     <!-- org.apache.solr.spelling.suggest.HighFrequencyDictionaryFactory -->
  988       <str name="field">cat</str>
  989       <str name="weightField">price</str>
  990       <str name="suggestAnalyzerFieldType">string</str>
  991     </lst>
  992   </searchComponent>
  993 
  994   <requestHandler name="/suggest" class="solr.SearchHandler" startup="lazy">
  995     <lst name="defaults">
  996       <str name="suggest">true</str>
  997       <str name="suggest.count">10</str>
  998     </lst>
  999     <arr name="components">
 1000       <str>suggest</str>
 1001     </arr>
 1002   </requestHandler>
 1003   <!-- Term Vector Component
 1004 
 1005        http://wiki.apache.org/solr/TermVectorComponent
 1006     -->
 1007   <searchComponent name="tvComponent" class="solr.TermVectorComponent"/>
 1008 
 1009   <!-- A request handler for demonstrating the term vector component
 1010 
 1011        This is purely as an example.
 1012 
 1013        In reality you will likely want to add the component to your
 1014        already specified request handlers.
 1015     -->
 1016   <requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy">
 1017     <lst name="defaults">
 1018       <str name="df">text</str>
 1019       <bool name="tv">true</bool>
 1020     </lst>
 1021     <arr name="last-components">
 1022       <str>tvComponent</str>
 1023     </arr>
 1024   </requestHandler>
 1025 
 1026   <!-- Terms Component
 1027 
 1028        http://wiki.apache.org/solr/TermsComponent
 1029 
 1030        A component to return terms and document frequency of those
 1031        terms
 1032     -->
 1033   <searchComponent name="terms" class="solr.TermsComponent"/>
 1034 
 1035   <!-- A request handler for demonstrating the terms component -->
 1036   <requestHandler name="/terms" class="solr.SearchHandler" startup="lazy">
 1037      <lst name="defaults">
 1038       <bool name="terms">true</bool>
 1039       <bool name="distrib">false</bool>
 1040     </lst>
 1041     <arr name="components">
 1042       <str>terms</str>
 1043     </arr>
 1044   </requestHandler>
 1045 
 1046 
 1047   <!-- Query Elevation Component
 1048 
 1049        http://wiki.apache.org/solr/QueryElevationComponent
 1050 
 1051        a search component that enables you to configure the top
 1052        results for a given query regardless of the normal lucene
 1053        scoring.
 1054     -->
 1055   <searchComponent name="elevator" class="solr.QueryElevationComponent" >
 1056     <!-- pick a fieldType to analyze queries -->
 1057     <str name="queryFieldType">string</str>
 1058     <str name="config-file">elevate.xml</str>
 1059   </searchComponent>
 1060 
 1061   <!-- A request handler for demonstrating the elevator component -->
 1062   <requestHandler name="/elevate" class="solr.SearchHandler" startup="lazy">
 1063     <lst name="defaults">
 1064       <str name="echoParams">explicit</str>
 1065       <str name="df">text</str>
 1066     </lst>
 1067     <arr name="last-components">
 1068       <str>elevator</str>
 1069     </arr>
 1070   </requestHandler>
 1071 
 1072   <!-- Highlighting Component
 1073 
 1074        http://wiki.apache.org/solr/HighlightingParameters
 1075     -->
 1076   <searchComponent class="solr.HighlightComponent" name="highlight">
 1077     <highlighting>
 1078       <!-- Configure the standard fragmenter -->
 1079       <!-- This could most likely be commented out in the "default" case -->
 1080       <fragmenter name="gap"
 1081                   default="true"
 1082                   class="solr.highlight.GapFragmenter">
 1083         <lst name="defaults">
 1084           <int name="hl.fragsize">100</int>
 1085         </lst>
 1086       </fragmenter>
 1087 
 1088       <!-- A regular-expression-based fragmenter
 1089            (for sentence extraction)
 1090         -->
 1091       <fragmenter name="regex"
 1092                   class="solr.highlight.RegexFragmenter">
 1093         <lst name="defaults">
 1094           <!-- slightly smaller fragsizes work better because of slop -->
 1095           <int name="hl.fragsize">70</int>
 1096           <!-- allow 50% slop on fragment sizes -->
 1097           <float name="hl.regex.slop">0.5</float>
 1098           <!-- a basic sentence pattern -->
 1099           <str name="hl.regex.pattern">[-\w ,/\n\&quot;&apos;]{20,200}</str>
 1100         </lst>
 1101       </fragmenter>
 1102 
 1103       <!-- Configure the standard formatter -->
 1104       <formatter name="html"
 1105                  default="true"
 1106                  class="solr.highlight.HtmlFormatter">
 1107         <lst name="defaults">
 1108           <str name="hl.simple.pre"><![CDATA[<em>]]></str>
 1109           <str name="hl.simple.post"><![CDATA[</em>]]></str>
 1110         </lst>
 1111       </formatter>
 1112 
 1113       <!-- Configure the standard encoder -->
 1114       <encoder name="html"
 1115                class="solr.highlight.HtmlEncoder" />
 1116 
 1117       <!-- Configure the standard fragListBuilder -->
 1118       <fragListBuilder name="simple"
 1119                        class="solr.highlight.SimpleFragListBuilder"/>
 1120 
 1121       <!-- Configure the single fragListBuilder -->
 1122       <fragListBuilder name="single"
 1123                        class="solr.highlight.SingleFragListBuilder"/>
 1124 
 1125       <!-- Configure the weighted fragListBuilder -->
 1126       <fragListBuilder name="weighted"
 1127                        default="true"
 1128                        class="solr.highlight.WeightedFragListBuilder"/>
 1129 
 1130       <!-- default tag FragmentsBuilder -->
 1131       <fragmentsBuilder name="default"
 1132                         default="true"
 1133                         class="solr.highlight.ScoreOrderFragmentsBuilder">
 1134         <!--
 1135         <lst name="defaults">
 1136           <str name="hl.multiValuedSeparatorChar">/</str>
 1137         </lst>
 1138         -->
 1139       </fragmentsBuilder>
 1140 
 1141       <!-- multi-colored tag FragmentsBuilder -->
 1142       <fragmentsBuilder name="colored"
 1143                         class="solr.highlight.ScoreOrderFragmentsBuilder">
 1144         <lst name="defaults">
 1145           <str name="hl.tag.pre"><![CDATA[
 1146                <b style="background:yellow">,<b style="background:lawgreen">,
 1147                <b style="background:aquamarine">,<b style="background:magenta">,
 1148                <b style="background:palegreen">,<b style="background:coral">,
 1149                <b style="background:wheat">,<b style="background:khaki">,
 1150                <b style="background:lime">,<b style="background:deepskyblue">]]></str>
 1151           <str name="hl.tag.post"><![CDATA[</b>]]></str>
 1152         </lst>
 1153       </fragmentsBuilder>
 1154 
 1155       <boundaryScanner name="default"
 1156                        default="true"
 1157                        class="solr.highlight.SimpleBoundaryScanner">
 1158         <lst name="defaults">
 1159           <str name="hl.bs.maxScan">10</str>
 1160           <str name="hl.bs.chars">.,!? &#9;&#10;&#13;</str>
 1161         </lst>
 1162       </boundaryScanner>
 1163 
 1164       <boundaryScanner name="breakIterator"
 1165                        class="solr.highlight.BreakIteratorBoundaryScanner">
 1166         <lst name="defaults">
 1167           <!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE -->
 1168           <str name="hl.bs.type">WORD</str>
 1169           <!-- language and country are used when constructing Locale object.  -->
 1170           <!-- And the Locale object will be used when getting instance of BreakIterator -->
 1171           <str name="hl.bs.language">en</str>
 1172           <str name="hl.bs.country">US</str>
 1173         </lst>
 1174       </boundaryScanner>
 1175     </highlighting>
 1176   </searchComponent>
 1177 
 1178   <!-- Update Processors
 1179 
 1180        Chains of Update Processor Factories for dealing with Update
 1181        Requests can be declared, and then used by name in Update
 1182        Request Processors
 1183 
 1184        http://wiki.apache.org/solr/UpdateRequestProcessor
 1185 
 1186     -->
 1187   <!-- Deduplication
 1188 
 1189        An example dedup update processor that creates the "id" field
 1190        on the fly based on the hash code of some other fields.  This
 1191        example has overwriteDupes set to false since we are using the
 1192        id field as the signatureField and Solr will maintain
 1193        uniqueness based on that anyway.
 1194 
 1195     -->
 1196   <!--
 1197      <updateRequestProcessorChain name="dedupe">
 1198        <processor class="solr.processor.SignatureUpdateProcessorFactory">
 1199          <bool name="enabled">true</bool>
 1200          <str name="signatureField">id</str>
 1201          <bool name="overwriteDupes">false</bool>
 1202          <str name="fields">name,features,cat</str>
 1203          <str name="signatureClass">solr.processor.Lookup3Signature</str>
 1204        </processor>
 1205        <processor class="solr.LogUpdateProcessorFactory" />
 1206        <processor class="solr.RunUpdateProcessorFactory" />
 1207      </updateRequestProcessorChain>
 1208     -->
 1209 
 1210   <!-- Language identification
 1211 
 1212        This example update chain identifies the language of the incoming
 1213        documents using the langid contrib. The detected language is
 1214        written to field language_s. No field name mapping is done.
 1215        The fields used for detection are text, title, subject and description,
 1216        making this example suitable for detecting languages form full-text
 1217        rich documents injected via ExtractingRequestHandler.
 1218        See more about langId at http://wiki.apache.org/solr/LanguageDetection
 1219     -->
 1220     <!--
 1221      <updateRequestProcessorChain name="langid">
 1222        <processor class="org.apache.solr.update.processor.TikaLanguageIdentifierUpdateProcessorFactory">
 1223          <str name="langid.fl">text,title,subject,description</str>
 1224          <str name="langid.langField">language_s</str>
 1225          <str name="langid.fallback">en</str>
 1226        </processor>
 1227        <processor class="solr.LogUpdateProcessorFactory" />
 1228        <processor class="solr.RunUpdateProcessorFactory" />
 1229      </updateRequestProcessorChain>
 1230     -->
 1231 
 1232   <!-- Script update processor
 1233 
 1234     This example hooks in an update processor implemented using JavaScript.
 1235 
 1236     See more about the script update processor at http://wiki.apache.org/solr/ScriptUpdateProcessor
 1237   -->
 1238   <!--
 1239     <updateRequestProcessorChain name="script">
 1240       <processor class="solr.StatelessScriptUpdateProcessorFactory">
 1241         <str name="script">update-script.js</str>
 1242         <lst name="params">
 1243           <str name="config_param">example config parameter</str>
 1244         </lst>
 1245       </processor>
 1246       <processor class="solr.RunUpdateProcessorFactory" />
 1247     </updateRequestProcessorChain>
 1248   -->
 1249 
 1250   <!-- Response Writers
 1251 
 1252        http://wiki.apache.org/solr/QueryResponseWriter
 1253 
 1254        Request responses will be written using the writer specified by
 1255        the 'wt' request parameter matching the name of a registered
 1256        writer.
 1257 
 1258        The "default" writer is the default and will be used if 'wt' is
 1259        not specified in the request.
 1260     -->
 1261   <!-- The following response writers are implicitly configured unless
 1262        overridden...
 1263     -->
 1264   <!--
 1265      <queryResponseWriter name="xml"
 1266                           default="true"
 1267                           class="solr.XMLResponseWriter" />
 1268      <queryResponseWriter name="json" class="solr.JSONResponseWriter"/>
 1269      <queryResponseWriter name="python" class="solr.PythonResponseWriter"/>
 1270      <queryResponseWriter name="ruby" class="solr.RubyResponseWriter"/>
 1271      <queryResponseWriter name="php" class="solr.PHPResponseWriter"/>
 1272      <queryResponseWriter name="phps" class="solr.PHPSerializedResponseWriter"/>
 1273      <queryResponseWriter name="csv" class="solr.CSVResponseWriter"/>
 1274      <queryResponseWriter name="schema.xml" class="solr.SchemaXmlResponseWriter"/>
 1275     -->
 1276 
 1277   <queryResponseWriter name="json" class="solr.JSONResponseWriter">
 1278      <!-- For the purposes of the tutorial, JSON responses are written as
 1279       plain text so that they are easy to read in *any* browser.
 1280       If you expect a MIME type of "application/json" just remove this override.
 1281      -->
 1282     <str name="content-type">text/plain; charset=UTF-8</str>
 1283   </queryResponseWriter>
 1284 
 1285   <!--
 1286      Custom response writers can be declared as needed...
 1287     -->
 1288   <queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" startup="lazy">
 1289     <str name="template.base.dir">${velocity.template.base.dir:}</str>
 1290   </queryResponseWriter>
 1291 
 1292   <!-- XSLT response writer transforms the XML output by any xslt file found
 1293        in Solr's conf/xslt directory.  Changes to xslt files are checked for
 1294        every xsltCacheLifetimeSeconds.
 1295     -->
 1296   <queryResponseWriter name="xslt" class="solr.XSLTResponseWriter">
 1297     <int name="xsltCacheLifetimeSeconds">5</int>
 1298   </queryResponseWriter>
 1299 
 1300   <!-- Query Parsers
 1301 
 1302        https://lucene.apache.org/solr/guide/query-syntax-and-parsing.html
 1303 
 1304        Multiple QParserPlugins can be registered by name, and then
 1305        used in either the "defType" param for the QueryComponent (used
 1306        by SearchHandler) or in LocalParams
 1307     -->
 1308   <!-- example of registering a query parser -->
 1309   <!--
 1310      <queryParser name="myparser" class="com.mycompany.MyQParserPlugin"/>
 1311     -->
 1312 
 1313   <!-- Function Parsers
 1314 
 1315        http://wiki.apache.org/solr/FunctionQuery
 1316 
 1317        Multiple ValueSourceParsers can be registered by name, and then
 1318        used as function names when using the "func" QParser.
 1319     -->
 1320   <!-- example of registering a custom function parser  -->
 1321   <!--
 1322      <valueSourceParser name="myfunc"
 1323                         class="com.mycompany.MyValueSourceParser" />
 1324     -->
 1325 
 1326 
 1327   <!-- Document Transformers
 1328        http://wiki.apache.org/solr/DocTransformers
 1329     -->
 1330   <!--
 1331      Could be something like:
 1332      <transformer name="db" class="com.mycompany.LoadFromDatabaseTransformer" >
 1333        <int name="connection">jdbc://....</int>
 1334      </transformer>
 1335 
 1336      To add a constant value to all docs, use:
 1337      <transformer name="mytrans2" class="org.apache.solr.response.transform.ValueAugmenterFactory" >
 1338        <int name="value">5</int>
 1339      </transformer>
 1340 
 1341      If you want the user to still be able to change it with _value:something_ use this:
 1342      <transformer name="mytrans3" class="org.apache.solr.response.transform.ValueAugmenterFactory" >
 1343        <double name="defaultValue">5</double>
 1344      </transformer>
 1345 
 1346       If you are using the QueryElevationComponent, you may wish to mark documents that get boosted.  The
 1347       EditorialMarkerFactory will do exactly that:
 1348      <transformer name="qecBooster" class="org.apache.solr.response.transform.EditorialMarkerFactory" />
 1349     -->
 1350 
 1351 </config>