ambari-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oleew...@apache.org
Subject [07/10] ambari git commit: AMBARI-15679. Stack definition for Logsearch (oleewre)
Date Sat, 09 Apr 2016 11:13:27 GMT
http://git-wip-us.apache.org/repos/asf/ambari/blob/4a2dcfbe/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-audit_logs-solrconfig.xml
----------------------------------------------------------------------
diff --git a/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-audit_logs-solrconfig.xml b/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-audit_logs-solrconfig.xml
new file mode 100644
index 0000000..155756e
--- /dev/null
+++ b/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-audit_logs-solrconfig.xml
@@ -0,0 +1,1929 @@
+<?xml version="1.0"?>
+<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
+<!--
+/**
+ * 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.
+ */
+-->
+
+<!-- This is a special config file for properties used to monitor status of the service -->
+<configuration supports_adding_forbidden="true">
+
+  <property>
+    <name>logsearch_audit_logs_max_retention</name>
+    <value>7</value>
+    <display-name>Max retention</display-name>
+    <description>Days to retain the audit logs in Solr</description>
+  </property>
+
+  <!-- solrconfig.xml -->
+
+  <property>
+    <name>content</name>
+    <description>This is the jinja template for solrconfig.xml file for service logs</description>
+    <value>&lt;?xml version="1.0" encoding="UTF-8" ?&gt;
+&lt;!--
+ 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.
+--&gt;
+
+&lt;!-- 
+     For more details about configurations options that may appear in
+     this file, see http://wiki.apache.org/solr/SolrConfigXml. 
+--&gt;
+&lt;config&gt;
+  &lt;!-- 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.
+    --&gt;
+
+  &lt;!-- 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.
+  --&gt;
+  &lt;luceneMatchVersion&gt;5.0.0&lt;/luceneMatchVersion&gt;
+
+  &lt;!-- &lt;lib/&gt; 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 &lt;lib/&gt; 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...
+       
+              &lt;lib dir="./lib" /&gt;
+    --&gt;
+
+  &lt;!-- 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 examples below can be used to load some solr-contribs along 
+       with their external dependencies.
+    --&gt;
+  &lt;lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-dataimporthandler-.*\.jar" /&gt;
+
+  &lt;lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib" regex=".*\.jar" /&gt;
+  &lt;lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-cell-\d.*\.jar" /&gt;
+
+  &lt;lib dir="${solr.install.dir:../../../..}/contrib/clustering/lib/" regex=".*\.jar" /&gt;
+  &lt;lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-clustering-\d.*\.jar" /&gt;
+
+  &lt;lib dir="${solr.install.dir:../../../..}/contrib/langid/lib/" regex=".*\.jar" /&gt;
+  &lt;lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-langid-\d.*\.jar" /&gt;
+
+  &lt;lib dir="${solr.install.dir:../../../..}/contrib/velocity/lib" regex=".*\.jar" /&gt;
+  &lt;lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-velocity-\d.*\.jar" /&gt;
+
+  &lt;!-- 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.
+    --&gt;
+  &lt;!--
+     &lt;lib path="../a-jar-that-does-not-exist.jar" /&gt; 
+  --&gt;
+  
+  &lt;!-- 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.
+    --&gt;
+  &lt;dataDir&gt;${solr.data.dir:}&lt;/dataDir&gt;
+
+
+  &lt;!-- 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,
+       solr.NIOFSDirectoryFactory, or solr.SimpleFSDirectoryFactory.
+
+       solr.RAMDirectoryFactory is memory based, not
+       persistent, and doesn't work with replication.
+    --&gt;
+  &lt;directoryFactory name="DirectoryFactory" 
+                    class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"&gt;
+    
+         
+    &lt;!-- These will be used if you are using the solr.HdfsDirectoryFactory,
+         otherwise they will be ignored. If you don't plan on using hdfs,
+         you can safely remove this section. --&gt;      
+    &lt;!-- The root directory that collection data should be written to. --&gt;     
+    &lt;str name="solr.hdfs.home"&gt;${solr.hdfs.home:}&lt;/str&gt;
+    &lt;!-- The hadoop configuration files to use for the hdfs client. --&gt;    
+    &lt;str name="solr.hdfs.confdir"&gt;${solr.hdfs.confdir:}&lt;/str&gt;
+    &lt;!-- Enable/Disable the hdfs cache. --&gt;    
+    &lt;str name="solr.hdfs.blockcache.enabled"&gt;${solr.hdfs.blockcache.enabled:true}&lt;/str&gt;
+    &lt;!-- Enable/Disable using one global cache for all SolrCores. 
+         The settings used will be from the first HdfsDirectoryFactory created. --&gt;    
+    &lt;str name="solr.hdfs.blockcache.global"&gt;${solr.hdfs.blockcache.global:true}&lt;/str&gt;
+    
+  &lt;/directoryFactory&gt; 
+
+  &lt;!-- 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.
+  --&gt;
+  &lt;codecFactory class="solr.SchemaCodecFactory"/&gt;
+
+  &lt;!-- To enable dynamic schema REST APIs, use the following for &lt;schemaFactory&gt;: --&gt;
+  
+       &lt;schemaFactory class="ManagedIndexSchemaFactory"&gt;
+         &lt;bool name="mutable"&gt;true&lt;/bool&gt;
+         &lt;str name="managedSchemaResourceName"&gt;managed-schema&lt;/str&gt;
+       &lt;/schemaFactory&gt;
+&lt;!--       
+       When ManagedIndexSchemaFactory is specified, Solr will load the schema from
+       the resource named in 'managedSchemaResourceName', rather than from schema.xml.
+       Note that the managed schema resource CANNOT be named schema.xml.  If the managed
+       schema does not exist, Solr will create it after reading schema.xml, then rename
+       'schema.xml' to 'schema.xml.bak'. 
+       
+       Do NOT hand edit the managed schema - external modifications will be ignored and
+       overwritten as a result of schema modification REST API calls.
+
+       When ManagedIndexSchemaFactory is specified with mutable = true, schema
+       modification REST API calls will be allowed; otherwise, error responses will be
+       sent back for these requests. 
+
+  &lt;schemaFactory class="ClassicIndexSchemaFactory"/&gt;
+  --&gt;
+
+  &lt;!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+       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 &lt;indexDefaults&gt; and &lt;mainIndex&gt; from older versions
+       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --&gt;
+  &lt;indexConfig&gt;
+    &lt;!-- maxFieldLength was removed in 4.0. To get similar behavior, include a 
+         LimitTokenCountFilterFactory in your fieldType definition. E.g. 
+     &lt;filter class="solr.LimitTokenCountFilterFactory" maxTokenCount="10000"/&gt;
+    --&gt;
+    &lt;!-- Maximum time to wait for a write lock (ms) for an IndexWriter. Default: 1000 --&gt;
+    &lt;!-- &lt;writeLockTimeout&gt;1000&lt;/writeLockTimeout&gt;  --&gt;
+    &lt;!-- LogSearch customization to avoid timeouts --&gt;
+    &lt;writeLockTimeout&gt;10000&lt;/writeLockTimeout&gt;
+
+    &lt;!-- The maximum number of simultaneous threads that may be
+         indexing documents at once in IndexWriter; if more than this
+         many threads arrive they will wait for others to finish.
+         Default in Solr/Lucene is 8. --&gt;
+    &lt;!-- &lt;maxIndexingThreads&gt;8&lt;/maxIndexingThreads&gt;  --&gt;
+    &lt;!-- LogSearch customization of increase performance --&gt;
+    &lt;maxIndexingThreads&gt;50&lt;/maxIndexingThreads&gt;
+
+    &lt;!-- 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) --&gt;
+    &lt;!-- &lt;useCompoundFile&gt;false&lt;/useCompoundFile&gt; --&gt;
+
+    &lt;!-- 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.
+         The default is 100 MB.  --&gt;
+    &lt;!-- &lt;ramBufferSizeMB&gt;100&lt;/ramBufferSizeMB&gt; --&gt;
+    &lt;!-- &lt;maxBufferedDocs&gt;1000&lt;/maxBufferedDocs&gt; --&gt;
+
+    &lt;!-- 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.
+      --&gt;
+    &lt;!--
+        &lt;mergePolicy class="org.apache.lucene.index.TieredMergePolicy"&gt;
+          &lt;int name="maxMergeAtOnce"&gt;10&lt;/int&gt;
+          &lt;int name="segmentsPerTier"&gt;10&lt;/int&gt;
+        &lt;/mergePolicy&gt;
+      --&gt;
+       
+    &lt;!-- Merge Factor
+         The merge factor controls how many segments will get merged at a time.
+         For TieredMergePolicy, mergeFactor is a convenience parameter which
+         will set both MaxMergeAtOnce and SegmentsPerTier at once.
+         For LogByteSizeMergePolicy, mergeFactor decides how many new segments
+         will be allowed before they are merged into one.
+         Default is 10 for both merge policies.
+      --&gt;
+    &lt;!-- 
+    &lt;mergeFactor&gt;10&lt;/mergeFactor&gt;
+      --&gt;
+    &lt;!-- LogSearch customization. Increased to 25 to maximize indexing speed --&gt;
+    &lt;mergeFactor&gt;25&lt;/mergeFactor&gt;
+
+    &lt;!-- 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.
+     --&gt;
+    &lt;!-- 
+       &lt;mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/&gt;
+       --&gt;
+
+    &lt;!-- 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...
+         http://wiki.apache.org/lucene-java/AvailableLockFactories
+    --&gt;
+    &lt;lockType&gt;${solr.lock.type:native}&lt;/lockType&gt;
+
+    &lt;!-- Unlock On Startup
+
+         If true, unlock any held write or commit locks on startup.
+         This defeats the locking mechanism that allows multiple
+         processes to safely access a lucene index, and should be used
+         with care. Default is "false".
+
+         This is not needed if lock type is 'single'
+     --&gt;
+    &lt;!--
+    &lt;unlockOnStartup&gt;false&lt;/unlockOnStartup&gt;
+      --&gt;
+
+    &lt;!-- 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.
+    --&gt;
+    &lt;!-- 
+    &lt;deletionPolicy class="solr.SolrDeletionPolicy"&gt;
+    --&gt;
+      &lt;!-- The number of commit points to be kept --&gt;
+      &lt;!-- &lt;str name="maxCommitsToKeep"&gt;1&lt;/str&gt; --&gt;
+      &lt;!-- The number of optimized commit points to be kept --&gt;
+      &lt;!-- &lt;str name="maxOptimizedCommitsToKeep"&gt;0&lt;/str&gt; --&gt;
+      &lt;!--
+          Delete all commit points once they have reached the given age.
+          Supports DateMathParser syntax e.g.
+        --&gt;
+      &lt;!--
+         &lt;str name="maxCommitAge"&gt;30MINUTES&lt;/str&gt;
+         &lt;str name="maxCommitAge"&gt;1DAY&lt;/str&gt;
+      --&gt;
+    &lt;!-- 
+    &lt;/deletionPolicy&gt;
+    --&gt;
+
+    &lt;!-- 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 info stream to solr's log. By default,
+         this is enabled here, and controlled through log4j.properties.
+      --&gt;
+     &lt;infoStream&gt;true&lt;/infoStream&gt;
+  &lt;/indexConfig&gt;
+
+
+  &lt;!-- JMX
+       
+       This example enables JMX if and only if an existing MBeanServer
+       is found, use this if you want to configure JMX through JVM
+       parameters. Remove this to disable exposing Solr configuration
+       and statistics to JMX.
+
+       For more details see http://wiki.apache.org/solr/SolrJmx
+    --&gt;
+  &lt;jmx /&gt;
+  &lt;!-- If you want to connect to a particular server, specify the
+       agentId 
+    --&gt;
+  &lt;!-- &lt;jmx agentId="myAgent" /&gt; --&gt;
+  &lt;!-- If you want to start a new MBeanServer, specify the serviceUrl --&gt;
+  &lt;!-- &lt;jmx serviceUrl="service:jmx:rmi:///jndi/rmi://localhost:9999/solr"/&gt;
+    --&gt;
+
+  &lt;!-- The default high-performance update handler --&gt;
+  &lt;updateHandler class="solr.DirectUpdateHandler2"&gt;
+
+    &lt;!-- 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.  --&gt; 
+    &lt;updateLog&gt;
+      &lt;str name="dir"&gt;${solr.ulog.dir:}&lt;/str&gt;
+    &lt;/updateLog&gt;
+ 
+    &lt;!-- AutoCommit
+
+         Perform a hard commit automatically under certain conditions.
+         Instead of enabling autoCommit, consider using "commitWithin"
+         when adding documents. 
+
+         http://wiki.apache.org/solr/UpdateXmlMessages
+
+         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.
+      --&gt;
+     &lt;autoCommit&gt; 
+       &lt;maxTime&gt;${solr.autoCommit.maxTime:15000}&lt;/maxTime&gt; 
+       &lt;openSearcher&gt;false&lt;/openSearcher&gt; 
+     &lt;/autoCommit&gt;
+
+    &lt;!-- 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.
+      --&gt;
+
+     &lt;autoSoftCommit&gt; 
+       &lt;maxTime&gt;${solr.autoSoftCommit.maxTime:5000}&lt;/maxTime&gt; 
+     &lt;/autoSoftCommit&gt;
+
+    &lt;!-- 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
+      --&gt;
+    &lt;!-- The RunExecutableListener executes an external command from a
+         hook such as postCommit or postOptimize.
+         
+         exe - the name of the executable to run
+         dir - dir to use as the current working directory. (default=".")
+         wait - the calling thread waits until the executable returns. 
+                (default="true")
+         args - the arguments to pass to the program.  (default is none)
+         env - environment variables to set.  (default is none)
+      --&gt;
+    &lt;!-- This example shows how RunExecutableListener could be used
+         with the script based replication...
+         http://wiki.apache.org/solr/CollectionDistribution
+      --&gt;
+    &lt;!--
+       &lt;listener event="postCommit" class="solr.RunExecutableListener"&gt;
+         &lt;str name="exe"&gt;solr/bin/snapshooter&lt;/str&gt;
+         &lt;str name="dir"&gt;.&lt;/str&gt;
+         &lt;bool name="wait"&gt;true&lt;/bool&gt;
+         &lt;arr name="args"&gt; &lt;str&gt;arg1&lt;/str&gt; &lt;str&gt;arg2&lt;/str&gt; &lt;/arr&gt;
+         &lt;arr name="env"&gt; &lt;str&gt;MYVAR=val1&lt;/str&gt; &lt;/arr&gt;
+       &lt;/listener&gt;
+      --&gt;
+
+  &lt;/updateHandler&gt;
+  
+  &lt;!-- 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.
+
+    --&gt;
+  &lt;!--
+  &lt;indexReaderFactory name="IndexReaderFactory" class="package.class"&gt;
+    &lt;str name="someArg"&gt;Some Value&lt;/str&gt;
+  &lt;/indexReaderFactory &gt;
+  --&gt;
+
+  &lt;!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+       Query section - these settings control query time things like caches
+       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --&gt;
+  &lt;query&gt;
+    &lt;!-- Max Boolean Clauses
+
+         Maximum number of clauses in each BooleanQuery,  an exception
+         is thrown if exceeded.
+
+         ** WARNING **
+         
+         This option actually modifies a global Lucene property that
+         will affect all SolrCores.  If multiple solrconfig.xml files
+         disagree on this property, the value at any given moment will
+         be based on the last SolrCore to be initialized.
+         
+      --&gt;
+    &lt;maxBooleanClauses&gt;1024&lt;/maxBooleanClauses&gt;
+
+
+    &lt;!-- Solr Internal Query Caches
+
+         There are two implementations of cache available for Solr,
+         LRUCache, based on a synchronized LinkedHashMap, and
+         FastLRUCache, based on a ConcurrentHashMap.  
+
+         FastLRUCache has faster gets and slower puts in single
+         threaded operation and thus is generally faster than LRUCache
+         when the hit ratio of the cache is high (&gt; 75%), and may be
+         faster under other scenarios on multi-cpu systems.
+    --&gt;
+
+    &lt;!-- 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
+         LRUCache, the autowarmed items will be the most recently
+         accessed items.
+
+         Parameters:
+           class - the SolrCache implementation LRUCache or
+               (LRUCache or FastLRUCache)
+           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
+               and old cache.  
+      --&gt;
+    &lt;filterCache class="solr.FastLRUCache"
+                 size="512"
+                 initialSize="512"
+                 autowarmCount="0"/&gt;
+
+    &lt;!-- 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.  
+      --&gt;
+    &lt;queryResultCache class="solr.LRUCache"
+                     size="512"
+                     initialSize="512"
+                     autowarmCount="0"/&gt;
+   
+    &lt;!-- 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.  
+      --&gt;
+    &lt;documentCache class="solr.LRUCache"
+                   size="512"
+                   initialSize="512"
+                   autowarmCount="0"/&gt;
+    
+    &lt;!-- custom cache currently used by block join --&gt; 
+    &lt;cache name="perSegFilter"
+      class="solr.search.LRUCache"
+      size="10"
+      initialSize="0"
+      autowarmCount="10"
+      regenerator="solr.NoOpRegenerator" /&gt;
+
+    &lt;!-- 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.
+      --&gt;
+    &lt;!--
+       &lt;fieldValueCache class="solr.FastLRUCache"
+                        size="512"
+                        autowarmCount="128"
+                        showItems="32" /&gt;
+      --&gt;
+
+    &lt;!-- 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.  
+      --&gt;
+    &lt;!--
+       &lt;cache name="myUserCache"
+              class="solr.LRUCache"
+              size="4096"
+              initialSize="1024"
+              autowarmCount="1024"
+              regenerator="com.mycompany.MyRegenerator"
+              /&gt;
+      --&gt;
+
+
+    &lt;!-- 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.
+    --&gt;
+    &lt;enableLazyFieldLoading&gt;true&lt;/enableLazyFieldLoading&gt;
+
+   &lt;!-- 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"
+     --&gt;
+   &lt;!--
+      &lt;useFilterForSortedQuery&gt;true&lt;/useFilterForSortedQuery&gt;
+     --&gt;
+
+   &lt;!-- 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.  
+     --&gt;
+   &lt;queryResultWindowSize&gt;20&lt;/queryResultWindowSize&gt;
+
+   &lt;!-- Maximum number of documents to cache for any entry in the
+        queryResultCache. 
+     --&gt;
+   &lt;queryResultMaxDocsCached&gt;200&lt;/queryResultMaxDocsCached&gt;
+
+   &lt;!-- 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.
+
+        
+     --&gt;
+    &lt;!-- QuerySenderListener takes an array of NamedList and executes a
+         local query request for each NamedList in sequence. 
+      --&gt;
+    &lt;listener event="newSearcher" class="solr.QuerySenderListener"&gt;
+      &lt;arr name="queries"&gt;
+        &lt;!--
+           &lt;lst&gt;&lt;str name="q"&gt;solr&lt;/str&gt;&lt;str name="sort"&gt;price asc&lt;/str&gt;&lt;/lst&gt;
+           &lt;lst&gt;&lt;str name="q"&gt;rocks&lt;/str&gt;&lt;str name="sort"&gt;weight asc&lt;/str&gt;&lt;/lst&gt;
+          --&gt;
+      &lt;/arr&gt;
+    &lt;/listener&gt;
+    &lt;listener event="firstSearcher" class="solr.QuerySenderListener"&gt;
+      &lt;arr name="queries"&gt;
+        &lt;lst&gt;
+          &lt;str name="q"&gt;static firstSearcher warming in solrconfig.xml&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/arr&gt;
+    &lt;/listener&gt;
+
+    &lt;!-- 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.
+      --&gt;
+    &lt;useColdSearcher&gt;false&lt;/useColdSearcher&gt;
+
+    &lt;!-- Max Warming Searchers
+         
+         Maximum number of searchers that may be warming in the
+         background concurrently.  An error is returned if this limit
+         is exceeded.
+
+         Recommend values of 1-2 for read-only slaves, higher for
+         masters w/o cache warming.
+      --&gt;
+    &lt;maxWarmingSearchers&gt;2&lt;/maxWarmingSearchers&gt;
+
+  &lt;/query&gt;
+
+
+  &lt;!-- Request Dispatcher
+
+       This section contains instructions for how the SolrDispatchFilter
+       should behave when processing requests for this SolrCore.
+
+       handleSelect is a legacy option that affects the behavior of requests
+       such as /select?qt=XXX
+
+       handleSelect="true" will cause the SolrDispatchFilter to process
+       the request and dispatch the query to a handler specified by the 
+       "qt" param, assuming "/select" isn't already registered.
+
+       handleSelect="false" will cause the SolrDispatchFilter to
+       ignore "/select" requests, resulting in a 404 unless a handler
+       is explicitly registered with the name "/select"
+
+       handleSelect="true" is not recommended for new users, but is the default
+       for backwards compatibility
+    --&gt;
+  &lt;requestDispatcher handleSelect="false" &gt;
+    &lt;!-- Request Parsing
+
+         These settings indicate how Solr Requests may be parsed, and
+         what restrictions may be placed on the ContentStreams from
+         those requests
+
+         enableRemoteStreaming - enables use of the stream.file
+         and stream.url parameters for specifying remote streams.
+
+         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.
+         
+         *** WARNING ***
+         The settings below authorize Solr to fetch remote files, You
+         should make sure your system has some authentication before
+         using enableRemoteStreaming="true"
+
+      --&gt; 
+    &lt;requestParsers enableRemoteStreaming="true" 
+                    multipartUploadLimitInKB="2048000"
+                    formdataUploadLimitInKB="2048"
+                    addHttpRequestToContext="false"/&gt;
+
+    &lt;!-- 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
+      --&gt;
+    &lt;httpCaching never304="true" /&gt;
+    &lt;!-- If you include a &lt;cacheControl&gt; 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 &lt;cacheControl&gt; option even if you have set
+         never304="true"
+      --&gt;
+    &lt;!--
+       &lt;httpCaching never304="true" &gt;
+         &lt;cacheControl&gt;max-age=30, public&lt;/cacheControl&gt; 
+       &lt;/httpCaching&gt;
+      --&gt;
+    &lt;!-- 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)
+      --&gt;
+    &lt;!--
+       &lt;httpCaching lastModifiedFrom="openTime"
+                    etagSeed="Solr"&gt;
+         &lt;cacheControl&gt;max-age=30, public&lt;/cacheControl&gt; 
+       &lt;/httpCaching&gt;
+      --&gt;
+  &lt;/requestDispatcher&gt;
+
+  &lt;!-- Request Handlers 
+
+       http://wiki.apache.org/solr/SolrRequestHandler
+
+       Incoming queries will be dispatched to a specific handler by name
+       based on the path specified in the request.
+
+       Legacy behavior: If the request path uses "/select" but no Request
+       Handler has that name, and if handleSelect="true" has been specified in
+       the requestDispatcher, then the Request Handler is dispatched based on
+       the qt parameter.  Handlers without a leading '/' are accessed this way
+       like so: http://host/app/[core/]select?qt=name  If no qt is
+       given, then the requestHandler that declares default="true" will be
+       used or the one named "standard".
+
+       If a Request Handler is declared with startup="lazy", then it will
+       not be initialized until the first request that uses it.
+
+    --&gt;
+
+  &lt;requestHandler name="/dataimport" class="solr.DataImportHandler"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="config"&gt;solr-data-config.xml&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;!-- SearchHandler
+
+       http://wiki.apache.org/solr/SearchHandler
+
+       For processing Search Queries, the primary Request Handler
+       provided with Solr is "SearchHandler" It delegates to a sequent
+       of SearchComponents (see below) and supports distributed
+       queries across multiple shards
+    --&gt;
+  &lt;requestHandler name="/select" class="solr.SearchHandler"&gt;
+    &lt;!-- default values for query parameters can be specified, these
+         will be overridden by parameters in the request
+      --&gt;
+     &lt;lst name="defaults"&gt;
+       &lt;str name="echoParams"&gt;explicit&lt;/str&gt;
+       &lt;int name="rows"&gt;10&lt;/int&gt;
+       &lt;str name="df"&gt;text&lt;/str&gt;
+     &lt;/lst&gt;
+    &lt;!-- In addition to defaults, "appends" params can be specified
+         to identify values which should be appended to the list of
+         multi-val params from the query (or the existing "defaults").
+      --&gt;
+    &lt;!-- In this example, the param "fq=instock:true" would be appended to
+         any query time fq params the user may specify, as a mechanism for
+         partitioning the index, independent of any user selected filtering
+         that may also be desired (perhaps as a result of faceted searching).
+
+         NOTE: there is *absolutely* nothing a client can do to prevent these
+         "appends" values from being used, so don't use this mechanism
+         unless you are sure you always want it.
+      --&gt;
+    &lt;!--
+       &lt;lst name="appends"&gt;
+         &lt;str name="fq"&gt;inStock:true&lt;/str&gt;
+       &lt;/lst&gt;
+      --&gt;
+    &lt;!-- "invariants" are a way of letting the Solr maintainer lock down
+         the options available to Solr clients.  Any params values
+         specified here are used regardless of what values may be specified
+         in either the query, the "defaults", or the "appends" params.
+
+         In this example, the facet.field and facet.query params would
+         be fixed, limiting the facets clients can use.  Faceting is
+         not turned on by default - but if the client does specify
+         facet=true in the request, these are the only facets they
+         will be able to see counts for; regardless of what other
+         facet.field or facet.query params they may specify.
+
+         NOTE: there is *absolutely* nothing a client can do to prevent these
+         "invariants" values from being used, so don't use this mechanism
+         unless you are sure you always want it.
+      --&gt;
+    &lt;!--
+       &lt;lst name="invariants"&gt;
+         &lt;str name="facet.field"&gt;cat&lt;/str&gt;
+         &lt;str name="facet.field"&gt;manu_exact&lt;/str&gt;
+         &lt;str name="facet.query"&gt;price:[* TO 500]&lt;/str&gt;
+         &lt;str name="facet.query"&gt;price:[500 TO *]&lt;/str&gt;
+       &lt;/lst&gt;
+      --&gt;
+    &lt;!-- If the default list of SearchComponents is not desired, that
+         list can either be overridden completely, or components can be
+         prepended or appended to the default list.  (see below)
+      --&gt;
+    &lt;!--
+       &lt;arr name="components"&gt;
+         &lt;str&gt;nameOfCustomComponent1&lt;/str&gt;
+         &lt;str&gt;nameOfCustomComponent2&lt;/str&gt;
+       &lt;/arr&gt;
+      --&gt;
+    &lt;/requestHandler&gt;
+
+  &lt;!-- A request handler that returns indented JSON by default --&gt;
+  &lt;requestHandler name="/query" class="solr.SearchHandler"&gt;
+     &lt;lst name="defaults"&gt;
+       &lt;str name="echoParams"&gt;explicit&lt;/str&gt;
+       &lt;str name="wt"&gt;json&lt;/str&gt;
+       &lt;str name="indent"&gt;true&lt;/str&gt;
+       &lt;str name="df"&gt;text&lt;/str&gt;
+     &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+
+
+  &lt;!-- realtime get handler, guaranteed to return the latest stored fields of
+       any document, without the need to commit or open a new searcher.  The
+       current implementation relies on the updateLog feature being enabled.
+
+       ** WARNING **
+       Do NOT disable the realtime get handler at /get if you are using
+       SolrCloud otherwise any leader election will cause a full sync in ALL
+       replicas for the shard in question. Similarly, a replica recovery will
+       also always fetch the complete index from the leader because a partial
+       sync will not be possible in the absence of this handler.
+  --&gt;
+  &lt;requestHandler name="/get" class="solr.RealTimeGetHandler"&gt;
+     &lt;lst name="defaults"&gt;
+       &lt;str name="omitHeader"&gt;true&lt;/str&gt;
+       &lt;str name="wt"&gt;json&lt;/str&gt;
+       &lt;str name="indent"&gt;true&lt;/str&gt;
+     &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+
+
+  &lt;!-- A Robust Example
+
+       This example SearchHandler declaration shows off usage of the
+       SearchHandler with many defaults declared
+
+       Note that multiple instances of the same Request Handler
+       (SearchHandler) can be registered multiple times with different
+       names (and different init parameters)
+    --&gt;
+  &lt;requestHandler name="/browse" class="solr.SearchHandler"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="echoParams"&gt;explicit&lt;/str&gt;
+
+      &lt;!-- VelocityResponseWriter settings --&gt;
+      &lt;str name="wt"&gt;velocity&lt;/str&gt;
+      &lt;str name="v.template"&gt;browse&lt;/str&gt;
+      &lt;str name="v.layout"&gt;layout&lt;/str&gt;
+
+      &lt;!-- Query settings --&gt;
+      &lt;str name="defType"&gt;edismax&lt;/str&gt;
+      &lt;str name="q.alt"&gt;*:*&lt;/str&gt;
+      &lt;str name="rows"&gt;10&lt;/str&gt;
+      &lt;str name="fl"&gt;*,score&lt;/str&gt;
+
+      &lt;!-- Faceting defaults --&gt;
+      &lt;str name="facet"&gt;on&lt;/str&gt;
+      &lt;str name="facet.mincount"&gt;1&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+
+
+  &lt;initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="df"&gt;text&lt;/str&gt;
+      &lt;str name="update.chain"&gt;add-unknown-fields-to-the-schema&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/initParams&gt;
+
+  &lt;!-- Update Request Handler.
+       
+       http://wiki.apache.org/solr/UpdateXmlMessages
+
+       The canonical Request Handler for Modifying the Index through
+       commands specified using XML, JSON, CSV, or JAVABIN
+
+       Note: Since solr1.1 requestHandlers requires a valid content
+       type header if posted in the body. For example, curl now
+       requires: -H 'Content-type:text/xml; charset=utf-8'
+       
+       To override the request content type and force a specific 
+       Content-type, use the request parameter: 
+         ?update.contentType=text/csv
+       
+       This handler will pick a response format to match the input
+       if the 'wt' parameter is not explicit
+    --&gt;
+  &lt;requestHandler name="/update" class="solr.UpdateRequestHandler"&gt;
+    &lt;!-- See below for information on defining 
+         updateRequestProcessorChains that can be used by name 
+         on each Update Request
+      --&gt;
+    &lt;!--
+       &lt;lst name="defaults"&gt;
+         &lt;str name="update.chain"&gt;dedupe&lt;/str&gt;
+       &lt;/lst&gt;
+       --&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;!-- Solr Cell Update Request Handler
+
+       http://wiki.apache.org/solr/ExtractingRequestHandler 
+
+    --&gt;
+  &lt;requestHandler name="/update/extract" 
+                  startup="lazy"
+                  class="solr.extraction.ExtractingRequestHandler" &gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="lowernames"&gt;true&lt;/str&gt;
+      &lt;str name="uprefix"&gt;ignored_&lt;/str&gt;
+
+      &lt;!-- capture link hrefs but ignore div attributes --&gt;
+      &lt;str name="captureAttr"&gt;true&lt;/str&gt;
+      &lt;str name="fmap.a"&gt;links&lt;/str&gt;
+      &lt;str name="fmap.div"&gt;ignored_&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+
+
+  &lt;!-- Field Analysis Request Handler
+
+       RequestHandler that provides much the same functionality as
+       analysis.jsp. Provides the ability to specify multiple field
+       types and field names in the same request and outputs
+       index-time and query-time analysis for each of them.
+
+       Request parameters are:
+       analysis.fieldname - field name whose analyzers are to be used
+
+       analysis.fieldtype - field type whose analyzers are to be used
+       analysis.fieldvalue - text for index-time analysis
+       q (or analysis.q) - text for query time analysis
+       analysis.showmatch (true|false) - When set to true and when
+           query analysis is performed, the produced tokens of the
+           field value analysis will be marked as "matched" for every
+           token that is produces by the query analysis
+   --&gt;
+  &lt;requestHandler name="/analysis/field" 
+                  startup="lazy"
+                  class="solr.FieldAnalysisRequestHandler" /&gt;
+
+
+  &lt;!-- Document Analysis Handler
+
+       http://wiki.apache.org/solr/AnalysisRequestHandler
+
+       An analysis handler that provides a breakdown of the analysis
+       process of provided documents. This handler expects a (single)
+       content stream with the following format:
+
+       &lt;docs&gt;
+         &lt;doc&gt;
+           &lt;field name="id"&gt;1&lt;/field&gt;
+           &lt;field name="name"&gt;The Name&lt;/field&gt;
+           &lt;field name="text"&gt;The Text Value&lt;/field&gt;
+         &lt;/doc&gt;
+         &lt;doc&gt;...&lt;/doc&gt;
+         &lt;doc&gt;...&lt;/doc&gt;
+         ...
+       &lt;/docs&gt;
+
+    Note: Each document must contain a field which serves as the
+    unique key. This key is used in the returned response to associate
+    an analysis breakdown to the analyzed document.
+
+    Like the FieldAnalysisRequestHandler, this handler also supports
+    query analysis by sending either an "analysis.query" or "q"
+    request parameter that holds the query text to be analyzed. It
+    also supports the "analysis.showmatch" parameter which when set to
+    true, all field tokens that match the query tokens will be marked
+    as a "match". 
+  --&gt;
+  &lt;requestHandler name="/analysis/document" 
+                  class="solr.DocumentAnalysisRequestHandler" 
+                  startup="lazy" /&gt;
+
+  &lt;!-- Admin Handlers
+
+       Admin Handlers - This will register all the standard admin
+       RequestHandlers.  
+    --&gt;
+  &lt;requestHandler name="/admin/" 
+                  class="solr.admin.AdminHandlers" /&gt;
+  &lt;!-- This single handler is equivalent to the following... --&gt;
+  &lt;!--
+     &lt;requestHandler name="/admin/luke"       class="solr.admin.LukeRequestHandler" /&gt;
+     &lt;requestHandler name="/admin/system"     class="solr.admin.SystemInfoHandler" /&gt;
+     &lt;requestHandler name="/admin/plugins"    class="solr.admin.PluginInfoHandler" /&gt;
+     &lt;requestHandler name="/admin/threads"    class="solr.admin.ThreadDumpHandler" /&gt;
+     &lt;requestHandler name="/admin/properties" class="solr.admin.PropertiesRequestHandler" /&gt;
+     &lt;requestHandler name="/admin/file"       class="solr.admin.ShowFileRequestHandler" &gt;
+    --&gt;
+  &lt;!-- If you wish to hide files under ${solr.home}/conf, explicitly
+       register the ShowFileRequestHandler using the definition below. 
+       NOTE: The glob pattern ('*') is the only pattern supported at present, *.xml will
+             not exclude all files ending in '.xml'. Use it to exclude _all_ updates
+    --&gt;
+  &lt;!--
+     &lt;requestHandler name="/admin/file" 
+                     class="solr.admin.ShowFileRequestHandler" &gt;
+       &lt;lst name="invariants"&gt;
+         &lt;str name="hidden"&gt;synonyms.txt&lt;/str&gt; 
+         &lt;str name="hidden"&gt;anotherfile.txt&lt;/str&gt; 
+         &lt;str name="hidden"&gt;*&lt;/str&gt; 
+       &lt;/lst&gt;
+     &lt;/requestHandler&gt;
+    --&gt;
+
+  &lt;!--
+    Enabling this request handler (which is NOT a default part of the admin handler) will allow the Solr UI to edit
+    all the config files. This is intended for secure/development use ONLY! Leaving available and publically
+    accessible is a security vulnerability and should be done with extreme caution!
+  --&gt;
+  &lt;!--
+  &lt;requestHandler name="/admin/fileedit" class="solr.admin.EditFileRequestHandler" &gt;
+    &lt;lst name="invariants"&gt;
+         &lt;str name="hidden"&gt;synonyms.txt&lt;/str&gt;
+         &lt;str name="hidden"&gt;anotherfile.txt&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+  --&gt;
+  &lt;!-- ping/healthcheck --&gt;
+  &lt;requestHandler name="/admin/ping" class="solr.PingRequestHandler"&gt;
+    &lt;lst name="invariants"&gt;
+      &lt;str name="q"&gt;solrpingquery&lt;/str&gt;
+    &lt;/lst&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="echoParams"&gt;all&lt;/str&gt;
+    &lt;/lst&gt;
+    &lt;!-- An optional feature of the PingRequestHandler is to configure the 
+         handler with a "healthcheckFile" which can be used to enable/disable 
+         the PingRequestHandler.
+         relative paths are resolved against the data dir 
+      --&gt;
+    &lt;!-- &lt;str name="healthcheckFile"&gt;server-enabled.txt&lt;/str&gt; --&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;!-- Echo the request contents back to the client --&gt;
+  &lt;requestHandler name="/debug/dump" class="solr.DumpRequestHandler" &gt;
+    &lt;lst name="defaults"&gt;
+     &lt;str name="echoParams"&gt;explicit&lt;/str&gt; 
+     &lt;str name="echoHandler"&gt;true&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/requestHandler&gt;
+  
+  &lt;!-- Solr Replication
+
+       The SolrReplicationHandler supports replicating indexes from a
+       "master" used for indexing and "slaves" used for queries.
+
+       http://wiki.apache.org/solr/SolrReplication 
+
+       It is also necessary for SolrCloud to function (in Cloud mode, the
+       replication handler is used to bulk transfer segments when nodes 
+       are added or need to recover).
+
+       https://wiki.apache.org/solr/SolrCloud/
+    --&gt;
+  &lt;requestHandler name="/replication" class="solr.ReplicationHandler" &gt; 
+    &lt;!--
+       To enable simple master/slave replication, uncomment one of the 
+       sections below, depending on whether this solr instance should be
+       the "master" or a "slave".  If this instance is a "slave" you will 
+       also need to fill in the masterUrl to point to a real machine.
+    --&gt;
+    &lt;!--
+       &lt;lst name="master"&gt;
+         &lt;str name="replicateAfter"&gt;commit&lt;/str&gt;
+         &lt;str name="replicateAfter"&gt;startup&lt;/str&gt;
+         &lt;str name="confFiles"&gt;schema.xml,stopwords.txt&lt;/str&gt;
+       &lt;/lst&gt;
+    --&gt;
+    &lt;!--
+       &lt;lst name="slave"&gt;
+         &lt;str name="masterUrl"&gt;http://your-master-hostname:8983/solr&lt;/str&gt;
+         &lt;str name="pollInterval"&gt;00:00:60&lt;/str&gt;
+       &lt;/lst&gt;
+    --&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;!-- Search Components
+
+       Search components are registered to SolrCore and used by 
+       instances of SearchHandler (which can access them by name)
+       
+       By default, the following components are available:
+       
+       &lt;searchComponent name="query"     class="solr.QueryComponent" /&gt;
+       &lt;searchComponent name="facet"     class="solr.FacetComponent" /&gt;
+       &lt;searchComponent name="mlt"       class="solr.MoreLikeThisComponent" /&gt;
+       &lt;searchComponent name="highlight" class="solr.HighlightComponent" /&gt;
+       &lt;searchComponent name="stats"     class="solr.StatsComponent" /&gt;
+       &lt;searchComponent name="debug"     class="solr.DebugComponent" /&gt;
+   
+       Default configuration in a requestHandler would look like:
+
+       &lt;arr name="components"&gt;
+         &lt;str&gt;query&lt;/str&gt;
+         &lt;str&gt;facet&lt;/str&gt;
+         &lt;str&gt;mlt&lt;/str&gt;
+         &lt;str&gt;highlight&lt;/str&gt;
+         &lt;str&gt;stats&lt;/str&gt;
+         &lt;str&gt;debug&lt;/str&gt;
+       &lt;/arr&gt;
+
+       If you register a searchComponent to one of the standard names, 
+       that will be used instead of the default.
+
+       To insert components before or after the 'standard' components, use:
+    
+       &lt;arr name="first-components"&gt;
+         &lt;str&gt;myFirstComponentName&lt;/str&gt;
+       &lt;/arr&gt;
+    
+       &lt;arr name="last-components"&gt;
+         &lt;str&gt;myLastComponentName&lt;/str&gt;
+       &lt;/arr&gt;
+
+       NOTE: The component registered with the name "debug" will
+       always be executed after the "last-components" 
+       
+     --&gt;
+  
+   &lt;!-- Spell Check
+
+        The spell check component can return a list of alternative spelling
+        suggestions.  
+
+        http://wiki.apache.org/solr/SpellCheckComponent
+     --&gt;
+  &lt;searchComponent name="spellcheck" class="solr.SpellCheckComponent"&gt;
+
+    &lt;str name="queryAnalyzerFieldType"&gt;key_lower_case&lt;/str&gt;
+
+    &lt;!-- Multiple "Spell Checkers" can be declared and used by this
+         component
+      --&gt;
+
+    &lt;!-- a spellchecker built from a field of the main index --&gt;
+    &lt;lst name="spellchecker"&gt;
+      &lt;str name="name"&gt;default&lt;/str&gt;
+      &lt;str name="field"&gt;text&lt;/str&gt;
+      &lt;str name="classname"&gt;solr.DirectSolrSpellChecker&lt;/str&gt;
+      &lt;!-- the spellcheck distance measure used, the default is the internal levenshtein --&gt;
+      &lt;str name="distanceMeasure"&gt;internal&lt;/str&gt;
+      &lt;!-- minimum accuracy needed to be considered a valid spellcheck suggestion --&gt;
+      &lt;float name="accuracy"&gt;0.5&lt;/float&gt;
+      &lt;!-- the maximum #edits we consider when enumerating terms: can be 1 or 2 --&gt;
+      &lt;int name="maxEdits"&gt;2&lt;/int&gt;
+      &lt;!-- the minimum shared prefix when enumerating terms --&gt;
+      &lt;int name="minPrefix"&gt;1&lt;/int&gt;
+      &lt;!-- maximum number of inspections per result. --&gt;
+      &lt;int name="maxInspections"&gt;5&lt;/int&gt;
+      &lt;!-- minimum length of a query term to be considered for correction --&gt;
+      &lt;int name="minQueryLength"&gt;4&lt;/int&gt;
+      &lt;!-- maximum threshold of documents a query term can appear to be considered for correction --&gt;
+      &lt;float name="maxQueryFrequency"&gt;0.01&lt;/float&gt;
+      &lt;!-- uncomment this to require suggestions to occur in 1% of the documents
+      	&lt;float name="thresholdTokenFrequency"&gt;.01&lt;/float&gt;
+      --&gt;
+    &lt;/lst&gt;
+    
+    &lt;!-- a spellchecker that can break or combine words.  See "/spell" handler below for usage --&gt;
+    &lt;lst name="spellchecker"&gt;
+      &lt;str name="name"&gt;wordbreak&lt;/str&gt;
+      &lt;str name="classname"&gt;solr.WordBreakSolrSpellChecker&lt;/str&gt;      
+      &lt;str name="field"&gt;name&lt;/str&gt;
+      &lt;str name="combineWords"&gt;true&lt;/str&gt;
+      &lt;str name="breakWords"&gt;true&lt;/str&gt;
+      &lt;int name="maxChanges"&gt;10&lt;/int&gt;
+    &lt;/lst&gt;
+
+    &lt;!-- a spellchecker that uses a different distance measure --&gt;
+    &lt;!--
+       &lt;lst name="spellchecker"&gt;
+         &lt;str name="name"&gt;jarowinkler&lt;/str&gt;
+         &lt;str name="field"&gt;spell&lt;/str&gt;
+         &lt;str name="classname"&gt;solr.DirectSolrSpellChecker&lt;/str&gt;
+         &lt;str name="distanceMeasure"&gt;
+           org.apache.lucene.search.spell.JaroWinklerDistance
+         &lt;/str&gt;
+       &lt;/lst&gt;
+     --&gt;
+
+    &lt;!-- a spellchecker that use an alternate comparator 
+
+         comparatorClass be one of:
+          1. score (default)
+          2. freq (Frequency first, then score)
+          3. A fully qualified class name
+      --&gt;
+    &lt;!--
+       &lt;lst name="spellchecker"&gt;
+         &lt;str name="name"&gt;freq&lt;/str&gt;
+         &lt;str name="field"&gt;lowerfilt&lt;/str&gt;
+         &lt;str name="classname"&gt;solr.DirectSolrSpellChecker&lt;/str&gt;
+         &lt;str name="comparatorClass"&gt;freq&lt;/str&gt;
+      --&gt;
+
+    &lt;!-- A spellchecker that reads the list of words from a file --&gt;
+    &lt;!--
+       &lt;lst name="spellchecker"&gt;
+         &lt;str name="classname"&gt;solr.FileBasedSpellChecker&lt;/str&gt;
+         &lt;str name="name"&gt;file&lt;/str&gt;
+         &lt;str name="sourceLocation"&gt;spellings.txt&lt;/str&gt;
+         &lt;str name="characterEncoding"&gt;UTF-8&lt;/str&gt;
+         &lt;str name="spellcheckIndexDir"&gt;spellcheckerFile&lt;/str&gt;
+       &lt;/lst&gt;
+      --&gt;
+  &lt;/searchComponent&gt;
+  
+  &lt;!-- 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 http://wiki.apache.org/solr/SpellCheckComponent for details
+       on the request parameters.
+    --&gt;
+  &lt;requestHandler name="/spell" class="solr.SearchHandler" startup="lazy"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="df"&gt;text&lt;/str&gt;
+      &lt;!-- 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 --&gt;
+      &lt;str name="spellcheck.dictionary"&gt;default&lt;/str&gt;
+      &lt;str name="spellcheck.dictionary"&gt;wordbreak&lt;/str&gt;
+      &lt;str name="spellcheck"&gt;on&lt;/str&gt;
+      &lt;str name="spellcheck.extendedResults"&gt;true&lt;/str&gt;       
+      &lt;str name="spellcheck.count"&gt;10&lt;/str&gt;
+      &lt;str name="spellcheck.alternativeTermCount"&gt;5&lt;/str&gt;
+      &lt;str name="spellcheck.maxResultsForSuggest"&gt;5&lt;/str&gt;       
+      &lt;str name="spellcheck.collate"&gt;true&lt;/str&gt;
+      &lt;str name="spellcheck.collateExtendedResults"&gt;true&lt;/str&gt;  
+      &lt;str name="spellcheck.maxCollationTries"&gt;10&lt;/str&gt;
+      &lt;str name="spellcheck.maxCollations"&gt;5&lt;/str&gt;         
+    &lt;/lst&gt;
+    &lt;arr name="last-components"&gt;
+      &lt;str&gt;spellcheck&lt;/str&gt;
+    &lt;/arr&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;searchComponent name="suggest" class="solr.SuggestComponent"&gt;
+  	&lt;lst name="suggester"&gt;
+      &lt;str name="name"&gt;mySuggester&lt;/str&gt;
+      &lt;str name="lookupImpl"&gt;FuzzyLookupFactory&lt;/str&gt;      &lt;!-- org.apache.solr.spelling.suggest.fst --&gt;
+      &lt;str name="dictionaryImpl"&gt;DocumentDictionaryFactory&lt;/str&gt;     &lt;!-- org.apache.solr.spelling.suggest.HighFrequencyDictionaryFactory --&gt; 
+      &lt;str name="field"&gt;cat&lt;/str&gt;
+      &lt;str name="weightField"&gt;price&lt;/str&gt;
+      &lt;str name="suggestAnalyzerFieldType"&gt;string&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/searchComponent&gt;
+
+  &lt;requestHandler name="/suggest" class="solr.SearchHandler" startup="lazy"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="suggest"&gt;true&lt;/str&gt;
+      &lt;str name="suggest.count"&gt;10&lt;/str&gt;
+    &lt;/lst&gt;
+    &lt;arr name="components"&gt;
+      &lt;str&gt;suggest&lt;/str&gt;
+    &lt;/arr&gt;
+  &lt;/requestHandler&gt;
+  &lt;!-- Term Vector Component
+
+       http://wiki.apache.org/solr/TermVectorComponent
+    --&gt;
+  &lt;searchComponent name="tvComponent" class="solr.TermVectorComponent"/&gt;
+
+  &lt;!-- A request handler for demonstrating the term vector component
+
+       This is purely as an example.
+
+       In reality you will likely want to add the component to your 
+       already specified request handlers. 
+    --&gt;
+  &lt;requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="df"&gt;text&lt;/str&gt;
+      &lt;bool name="tv"&gt;true&lt;/bool&gt;
+    &lt;/lst&gt;
+    &lt;arr name="last-components"&gt;
+      &lt;str&gt;tvComponent&lt;/str&gt;
+    &lt;/arr&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;!-- Clustering Component
+
+       You'll need to set the solr.clustering.enabled system property
+       when running solr to run with clustering enabled:
+
+            java -Dsolr.clustering.enabled=true -jar start.jar
+
+       http://wiki.apache.org/solr/ClusteringComponent
+       http://carrot2.github.io/solr-integration-strategies/
+    --&gt;
+  &lt;searchComponent name="clustering"
+                   enable="${solr.clustering.enabled:false}"
+                   class="solr.clustering.ClusteringComponent" &gt;
+    &lt;lst name="engine"&gt;
+      &lt;str name="name"&gt;lingo&lt;/str&gt;
+
+      &lt;!-- Class name of a clustering algorithm compatible with the Carrot2 framework.
+
+           Currently available open source algorithms are:
+           * org.carrot2.clustering.lingo.LingoClusteringAlgorithm
+           * org.carrot2.clustering.stc.STCClusteringAlgorithm
+           * org.carrot2.clustering.kmeans.BisectingKMeansClusteringAlgorithm
+
+           See http://project.carrot2.org/algorithms.html for more information.
+
+           A commercial algorithm Lingo3G (needs to be installed separately) is defined as:
+           * com.carrotsearch.lingo3g.Lingo3GClusteringAlgorithm
+        --&gt;
+      &lt;str name="carrot.algorithm"&gt;org.carrot2.clustering.lingo.LingoClusteringAlgorithm&lt;/str&gt;
+
+      &lt;!-- Override location of the clustering algorithm's resources 
+           (attribute definitions and lexical resources).
+
+           A directory from which to load algorithm-specific stop words,
+           stop labels and attribute definition XMLs. 
+
+           For an overview of Carrot2 lexical resources, see:
+           http://download.carrot2.org/head/manual/#chapter.lexical-resources
+
+           For an overview of Lingo3G lexical resources, see:
+           http://download.carrotsearch.com/lingo3g/manual/#chapter.lexical-resources
+       --&gt;
+      &lt;str name="carrot.resourcesDir"&gt;clustering/carrot2&lt;/str&gt;
+    &lt;/lst&gt;
+
+    &lt;!-- An example definition for the STC clustering algorithm. --&gt;
+    &lt;lst name="engine"&gt;
+      &lt;str name="name"&gt;stc&lt;/str&gt;
+      &lt;str name="carrot.algorithm"&gt;org.carrot2.clustering.stc.STCClusteringAlgorithm&lt;/str&gt;
+    &lt;/lst&gt;
+
+    &lt;!-- An example definition for the bisecting kmeans clustering algorithm. --&gt;
+    &lt;lst name="engine"&gt;
+      &lt;str name="name"&gt;kmeans&lt;/str&gt;
+      &lt;str name="carrot.algorithm"&gt;org.carrot2.clustering.kmeans.BisectingKMeansClusteringAlgorithm&lt;/str&gt;
+    &lt;/lst&gt;
+  &lt;/searchComponent&gt;
+
+  &lt;!-- A request handler for demonstrating the clustering component
+
+       This is purely as an example.
+
+       In reality you will likely want to add the component to your 
+       already specified request handlers. 
+    --&gt;
+  &lt;requestHandler name="/clustering"
+                  startup="lazy"
+                  enable="${solr.clustering.enabled:false}"
+                  class="solr.SearchHandler"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;bool name="clustering"&gt;true&lt;/bool&gt;
+      &lt;bool name="clustering.results"&gt;true&lt;/bool&gt;
+      &lt;!-- Field name with the logical "title" of a each document (optional) --&gt;
+      &lt;str name="carrot.title"&gt;name&lt;/str&gt;
+      &lt;!-- Field name with the logical "URL" of a each document (optional) --&gt;
+      &lt;str name="carrot.url"&gt;id&lt;/str&gt;
+      &lt;!-- Field name with the logical "content" of a each document (optional) --&gt;
+      &lt;str name="carrot.snippet"&gt;features&lt;/str&gt;
+      &lt;!-- Apply highlighter to the title/ content and use this for clustering. --&gt;
+      &lt;bool name="carrot.produceSummary"&gt;true&lt;/bool&gt;
+      &lt;!-- the maximum number of labels per cluster --&gt;
+      &lt;!--&lt;int name="carrot.numDescriptions"&gt;5&lt;/int&gt;--&gt;
+      &lt;!-- produce sub clusters --&gt;
+      &lt;bool name="carrot.outputSubClusters"&gt;false&lt;/bool&gt;
+
+      &lt;!-- Configure the remaining request handler parameters. --&gt;
+      &lt;str name="defType"&gt;edismax&lt;/str&gt;
+      &lt;str name="qf"&gt;
+        text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
+      &lt;/str&gt;
+      &lt;str name="q.alt"&gt;*:*&lt;/str&gt;
+      &lt;str name="rows"&gt;10&lt;/str&gt;
+      &lt;str name="fl"&gt;*,score&lt;/str&gt;
+    &lt;/lst&gt;
+    &lt;arr name="last-components"&gt;
+      &lt;str&gt;clustering&lt;/str&gt;
+    &lt;/arr&gt;
+  &lt;/requestHandler&gt;
+  
+  &lt;!-- Terms Component
+
+       http://wiki.apache.org/solr/TermsComponent
+
+       A component to return terms and document frequency of those
+       terms
+    --&gt;
+  &lt;searchComponent name="terms" class="solr.TermsComponent"/&gt;
+
+  &lt;!-- A request handler for demonstrating the terms component --&gt;
+  &lt;requestHandler name="/terms" class="solr.SearchHandler" startup="lazy"&gt;
+     &lt;lst name="defaults"&gt;
+      &lt;bool name="terms"&gt;true&lt;/bool&gt;
+      &lt;bool name="distrib"&gt;false&lt;/bool&gt;
+    &lt;/lst&gt;     
+    &lt;arr name="components"&gt;
+      &lt;str&gt;terms&lt;/str&gt;
+    &lt;/arr&gt;
+  &lt;/requestHandler&gt;
+
+
+  &lt;!-- Query Elevation Component
+
+       http://wiki.apache.org/solr/QueryElevationComponent
+
+       a search component that enables you to configure the top
+       results for a given query regardless of the normal lucene
+       scoring.
+    --&gt;
+  &lt;searchComponent name="elevator" class="solr.QueryElevationComponent" &gt;
+    &lt;!-- pick a fieldType to analyze queries --&gt;
+    &lt;str name="queryFieldType"&gt;string&lt;/str&gt;
+    &lt;str name="config-file"&gt;elevate.xml&lt;/str&gt;
+  &lt;/searchComponent&gt;
+
+  &lt;!-- A request handler for demonstrating the elevator component --&gt;
+  &lt;requestHandler name="/elevate" class="solr.SearchHandler" startup="lazy"&gt;
+    &lt;lst name="defaults"&gt;
+      &lt;str name="echoParams"&gt;explicit&lt;/str&gt;
+      &lt;str name="df"&gt;text&lt;/str&gt;
+    &lt;/lst&gt;
+    &lt;arr name="last-components"&gt;
+      &lt;str&gt;elevator&lt;/str&gt;
+    &lt;/arr&gt;
+  &lt;/requestHandler&gt;
+
+  &lt;!-- Highlighting Component
+
+       http://wiki.apache.org/solr/HighlightingParameters
+    --&gt;
+  &lt;searchComponent class="solr.HighlightComponent" name="highlight"&gt;
+    &lt;highlighting&gt;
+      &lt;!-- Configure the standard fragmenter --&gt;
+      &lt;!-- This could most likely be commented out in the "default" case --&gt;
+      &lt;fragmenter name="gap" 
+                  default="true"
+                  class="solr.highlight.GapFragmenter"&gt;
+        &lt;lst name="defaults"&gt;
+          &lt;int name="hl.fragsize"&gt;100&lt;/int&gt;
+        &lt;/lst&gt;
+      &lt;/fragmenter&gt;
+
+      &lt;!-- A regular-expression-based fragmenter 
+           (for sentence extraction) 
+        --&gt;
+      &lt;fragmenter name="regex" 
+                  class="solr.highlight.RegexFragmenter"&gt;
+        &lt;lst name="defaults"&gt;
+          &lt;!-- slightly smaller fragsizes work better because of slop --&gt;
+          &lt;int name="hl.fragsize"&gt;70&lt;/int&gt;
+          &lt;!-- allow 50% slop on fragment sizes --&gt;
+          &lt;float name="hl.regex.slop"&gt;0.5&lt;/float&gt;
+          &lt;!-- a basic sentence pattern --&gt;
+          &lt;str name="hl.regex.pattern"&gt;[-\w ,/\n\&amp;quot;&amp;apos;]{20,200}&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/fragmenter&gt;
+
+      &lt;!-- Configure the standard formatter --&gt;
+      &lt;formatter name="html" 
+                 default="true"
+                 class="solr.highlight.HtmlFormatter"&gt;
+        &lt;lst name="defaults"&gt;
+          &lt;str name="hl.simple.pre"&gt;&lt;![CDATA[&lt;em&gt;]]&gt;&lt;/str&gt;
+          &lt;str name="hl.simple.post"&gt;&lt;![CDATA[&lt;/em&gt;]]&gt;&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/formatter&gt;
+
+      &lt;!-- Configure the standard encoder --&gt;
+      &lt;encoder name="html" 
+               class="solr.highlight.HtmlEncoder" /&gt;
+
+      &lt;!-- Configure the standard fragListBuilder --&gt;
+      &lt;fragListBuilder name="simple" 
+                       class="solr.highlight.SimpleFragListBuilder"/&gt;
+      
+      &lt;!-- Configure the single fragListBuilder --&gt;
+      &lt;fragListBuilder name="single" 
+                       class="solr.highlight.SingleFragListBuilder"/&gt;
+      
+      &lt;!-- Configure the weighted fragListBuilder --&gt;
+      &lt;fragListBuilder name="weighted" 
+                       default="true"
+                       class="solr.highlight.WeightedFragListBuilder"/&gt;
+      
+      &lt;!-- default tag FragmentsBuilder --&gt;
+      &lt;fragmentsBuilder name="default" 
+                        default="true"
+                        class="solr.highlight.ScoreOrderFragmentsBuilder"&gt;
+        &lt;!-- 
+        &lt;lst name="defaults"&gt;
+          &lt;str name="hl.multiValuedSeparatorChar"&gt;/&lt;/str&gt;
+        &lt;/lst&gt;
+        --&gt;
+      &lt;/fragmentsBuilder&gt;
+
+      &lt;!-- multi-colored tag FragmentsBuilder --&gt;
+      &lt;fragmentsBuilder name="colored" 
+                        class="solr.highlight.ScoreOrderFragmentsBuilder"&gt;
+        &lt;lst name="defaults"&gt;
+          &lt;str name="hl.tag.pre"&gt;&lt;![CDATA[
+               &lt;b style="background:yellow"&gt;,&lt;b style="background:lawgreen"&gt;,
+               &lt;b style="background:aquamarine"&gt;,&lt;b style="background:magenta"&gt;,
+               &lt;b style="background:palegreen"&gt;,&lt;b style="background:coral"&gt;,
+               &lt;b style="background:wheat"&gt;,&lt;b style="background:khaki"&gt;,
+               &lt;b style="background:lime"&gt;,&lt;b style="background:deepskyblue"&gt;]]&gt;&lt;/str&gt;
+          &lt;str name="hl.tag.post"&gt;&lt;![CDATA[&lt;/b&gt;]]&gt;&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/fragmentsBuilder&gt;
+      
+      &lt;boundaryScanner name="default" 
+                       default="true"
+                       class="solr.highlight.SimpleBoundaryScanner"&gt;
+        &lt;lst name="defaults"&gt;
+          &lt;str name="hl.bs.maxScan"&gt;10&lt;/str&gt;
+          &lt;str name="hl.bs.chars"&gt;.,!? &amp;#9;&amp;#10;&amp;#13;&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/boundaryScanner&gt;
+      
+      &lt;boundaryScanner name="breakIterator" 
+                       class="solr.highlight.BreakIteratorBoundaryScanner"&gt;
+        &lt;lst name="defaults"&gt;
+          &lt;!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE --&gt;
+          &lt;str name="hl.bs.type"&gt;WORD&lt;/str&gt;
+          &lt;!-- language and country are used when constructing Locale object.  --&gt;
+          &lt;!-- And the Locale object will be used when getting instance of BreakIterator --&gt;
+          &lt;str name="hl.bs.language"&gt;en&lt;/str&gt;
+          &lt;str name="hl.bs.country"&gt;US&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/boundaryScanner&gt;
+    &lt;/highlighting&gt;
+  &lt;/searchComponent&gt;
+
+  &lt;!-- Update Processors
+
+       Chains of Update Processor Factories for dealing with Update
+       Requests can be declared, and then used by name in Update
+       Request Processors
+
+       http://wiki.apache.org/solr/UpdateRequestProcessor
+
+    --&gt; 
+
+  &lt;!-- Add unknown fields to the schema 
+  
+       An example field type guessing update processor 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.  
+       
+       This requires that the schema is both managed and mutable, by
+       declaring schemaFactory as ManagedIndexSchemaFactory, with
+       mutable specified as true. 
+       
+       See http://wiki.apache.org/solr/GuessingFieldTypes
+    --&gt;
+  &lt;updateRequestProcessorChain name="add-unknown-fields-to-the-schema"&gt;
+
+    &lt;processor class="solr.DefaultValueUpdateProcessorFactory"&gt;
+        &lt;str name="fieldName"&gt;_ttl_&lt;/str&gt;
+        &lt;str name="value"&gt;+{{logsearch_audit_logs_max_retention}}DAYS&lt;/str&gt;
+    &lt;/processor&gt;
+    &lt;processor class="solr.processor.DocExpirationUpdateProcessorFactory"&gt;
+        &lt;int name="autoDeletePeriodSeconds"&gt;30&lt;/int&gt;
+        &lt;str name="ttlFieldName"&gt;_ttl_&lt;/str&gt;
+        &lt;str name="expirationFieldName"&gt;_expire_at_&lt;/str&gt;
+    &lt;/processor&gt;
+    &lt;processor class="solr.FirstFieldValueUpdateProcessorFactory"&gt;
+      &lt;str name="fieldName"&gt;_expire_at_&lt;/str&gt;
+    &lt;/processor&gt;
+
+
+    &lt;processor class="solr.RemoveBlankFieldUpdateProcessorFactory"/&gt;
+    &lt;processor class="solr.ParseBooleanFieldUpdateProcessorFactory"/&gt;
+    &lt;processor class="solr.ParseLongFieldUpdateProcessorFactory"/&gt;
+    &lt;processor class="solr.ParseDoubleFieldUpdateProcessorFactory"/&gt;
+    &lt;processor class="solr.ParseDateFieldUpdateProcessorFactory"&gt;
+      &lt;arr name="format"&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm:ss.SSSZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm:ss,SSSZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm:ss.SSS&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm:ss,SSS&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm:ssZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm:ss&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mmZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd'T'HH:mm&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm:ss.SSSZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm:ss,SSSZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm:ss.SSS&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm:ss,SSS&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm:ssZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm:ss&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mmZ&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd HH:mm&lt;/str&gt;
+        &lt;str&gt;yyyy-MM-dd&lt;/str&gt;
+      &lt;/arr&gt;
+    &lt;/processor&gt;
+    &lt;processor class="solr.AddSchemaFieldsUpdateProcessorFactory"&gt;
+      &lt;str name="defaultFieldType"&gt;key_lower_case&lt;/str&gt;
+      &lt;lst name="typeMapping"&gt;
+        &lt;str name="valueClass"&gt;java.lang.Boolean&lt;/str&gt;
+        &lt;str name="fieldType"&gt;booleans&lt;/str&gt;
+      &lt;/lst&gt;
+      &lt;lst name="typeMapping"&gt;
+        &lt;str name="valueClass"&gt;java.util.Date&lt;/str&gt;
+        &lt;str name="fieldType"&gt;tdates&lt;/str&gt;
+      &lt;/lst&gt;
+      &lt;lst name="typeMapping"&gt;
+        &lt;str name="valueClass"&gt;java.lang.Long&lt;/str&gt;
+        &lt;str name="valueClass"&gt;java.lang.Integer&lt;/str&gt;
+        &lt;str name="fieldType"&gt;tlongs&lt;/str&gt;
+      &lt;/lst&gt;
+      &lt;lst name="typeMapping"&gt;
+        &lt;str name="valueClass"&gt;java.lang.Number&lt;/str&gt;
+        &lt;str name="fieldType"&gt;tdoubles&lt;/str&gt;
+      &lt;/lst&gt;
+    &lt;/processor&gt;
+
+    &lt;processor class="solr.LogUpdateProcessorFactory"/&gt;
+    &lt;processor class="solr.RunUpdateProcessorFactory"/&gt;
+  &lt;/updateRequestProcessorChain&gt;
+
+
+  &lt;!-- Deduplication
+
+       An example dedup update processor that creates the "id" field
+       on the fly based on the hash code of some other fields.  This
+       example has overwriteDupes set to false since we are using the
+       id field as the signatureField and Solr will maintain
+       uniqueness based on that anyway.  
+       
+    --&gt;
+  &lt;!--
+     &lt;updateRequestProcessorChain name="dedupe"&gt;
+       &lt;processor class="solr.processor.SignatureUpdateProcessorFactory"&gt;
+         &lt;bool name="enabled"&gt;true&lt;/bool&gt;
+         &lt;str name="signatureField"&gt;id&lt;/str&gt;
+         &lt;bool name="overwriteDupes"&gt;false&lt;/bool&gt;
+         &lt;str name="fields"&gt;name,features,cat&lt;/str&gt;
+         &lt;str name="signatureClass"&gt;solr.processor.Lookup3Signature&lt;/str&gt;
+       &lt;/processor&gt;
+       &lt;processor class="solr.LogUpdateProcessorFactory" /&gt;
+       &lt;processor class="solr.RunUpdateProcessorFactory" /&gt;
+     &lt;/updateRequestProcessorChain&gt;
+    --&gt;
+  
+  &lt;!-- Language identification
+
+       This example update chain identifies the language of the incoming
+       documents using the langid contrib. The detected language is
+       written to field language_s. No field name mapping is done.
+       The fields used for detection are text, title, subject and description,
+       making this example suitable for detecting languages form full-text
+       rich documents injected via ExtractingRequestHandler.
+       See more about langId at http://wiki.apache.org/solr/LanguageDetection
+    --&gt;
+    &lt;!--
+     &lt;updateRequestProcessorChain name="langid"&gt;
+       &lt;processor class="org.apache.solr.update.processor.TikaLanguageIdentifierUpdateProcessorFactory"&gt;
+         &lt;str name="langid.fl"&gt;text,title,subject,description&lt;/str&gt;
+         &lt;str name="langid.langField"&gt;language_s&lt;/str&gt;
+         &lt;str name="langid.fallback"&gt;en&lt;/str&gt;
+       &lt;/processor&gt;
+       &lt;processor class="solr.LogUpdateProcessorFactory" /&gt;
+       &lt;processor class="solr.RunUpdateProcessorFactory" /&gt;
+     &lt;/updateRequestProcessorChain&gt;
+    --&gt;
+
+  &lt;!-- Script update processor
+
+    This example hooks in an update processor implemented using JavaScript.
+
+    See more about the script update processor at http://wiki.apache.org/solr/ScriptUpdateProcessor
+  --&gt;
+  &lt;!--
+    &lt;updateRequestProcessorChain name="script"&gt;
+      &lt;processor class="solr.StatelessScriptUpdateProcessorFactory"&gt;
+        &lt;str name="script"&gt;update-script.js&lt;/str&gt;
+        &lt;lst name="params"&gt;
+          &lt;str name="config_param"&gt;example config parameter&lt;/str&gt;
+        &lt;/lst&gt;
+      &lt;/processor&gt;
+      &lt;processor class="solr.RunUpdateProcessorFactory" /&gt;
+    &lt;/updateRequestProcessorChain&gt;
+  --&gt;
+ 
+  &lt;!-- Response Writers
+
+       http://wiki.apache.org/solr/QueryResponseWriter
+
+       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.
+    --&gt;
+  &lt;!-- The following response writers are implicitly configured unless
+       overridden...
+    --&gt;
+  &lt;!--
+     &lt;queryResponseWriter name="xml" 
+                          default="true"
+                          class="solr.XMLResponseWriter" /&gt;
+     &lt;queryResponseWriter name="json" class="solr.JSONResponseWriter"/&gt;
+     &lt;queryResponseWriter name="python" class="solr.PythonResponseWriter"/&gt;
+     &lt;queryResponseWriter name="ruby" class="solr.RubyResponseWriter"/&gt;
+     &lt;queryResponseWriter name="php" class="solr.PHPResponseWriter"/&gt;
+     &lt;queryResponseWriter name="phps" class="solr.PHPSerializedResponseWriter"/&gt;
+     &lt;queryResponseWriter name="csv" class="solr.CSVResponseWriter"/&gt;
+     &lt;queryResponseWriter name="schema.xml" class="solr.SchemaXmlResponseWriter"/&gt;
+    --&gt;
+
+  &lt;queryResponseWriter name="json" class="solr.JSONResponseWriter"&gt;
+     &lt;!-- For the purposes of the tutorial, JSON responses are written as
+      plain text so that they are easy to read in *any* browser.
+      If you expect a MIME type of "application/json" just remove this override.
+     --&gt;
+    &lt;str name="content-type"&gt;text/plain; charset=UTF-8&lt;/str&gt;
+  &lt;/queryResponseWriter&gt;
+  
+  &lt;!--
+     Custom response writers can be declared as needed...
+    --&gt;
+  &lt;queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" startup="lazy"&gt;
+    &lt;str name="template.base.dir"&gt;${velocity.template.base.dir:}&lt;/str&gt;
+  &lt;/queryResponseWriter&gt;
+
+  &lt;!-- XSLT response writer transforms the XML output by any xslt file found
+       in Solr's conf/xslt directory.  Changes to xslt files are checked for
+       every xsltCacheLifetimeSeconds.  
+    --&gt;
+  &lt;queryResponseWriter name="xslt" class="solr.XSLTResponseWriter"&gt;
+    &lt;int name="xsltCacheLifetimeSeconds"&gt;5&lt;/int&gt;
+  &lt;/queryResponseWriter&gt;
+
+  &lt;!-- Query Parsers
+
+       http://wiki.apache.org/solr/SolrQuerySyntax
+
+       Multiple QParserPlugins can be registered by name, and then
+       used in either the "defType" param for the QueryComponent (used
+       by SearchHandler) or in LocalParams
+    --&gt;
+  &lt;!-- example of registering a query parser --&gt;
+  &lt;!--
+     &lt;queryParser name="myparser" class="com.mycompany.MyQParserPlugin"/&gt;
+    --&gt;
+
+  &lt;!-- Function Parsers
+
+       http://wiki.apache.org/solr/FunctionQuery
+
+       Multiple ValueSourceParsers can be registered by name, and then
+       used as function names when using the "func" QParser.
+    --&gt;
+  &lt;!-- example of registering a custom function parser  --&gt;
+  &lt;!--
+     &lt;valueSourceParser name="myfunc" 
+                        class="com.mycompany.MyValueSourceParser" /&gt;
+    --&gt;
+    
+  
+  &lt;!-- Document Transformers
+       http://wiki.apache.org/solr/DocTransformers
+    --&gt;
+  &lt;!--
+     Could be something like:
+     &lt;transformer name="db" class="com.mycompany.LoadFromDatabaseTransformer" &gt;
+       &lt;int name="connection"&gt;jdbc://....&lt;/int&gt;
+     &lt;/transformer&gt;
+     
+     To add a constant value to all docs, use:
+     &lt;transformer name="mytrans2" class="org.apache.solr.response.transform.ValueAugmenterFactory" &gt;
+       &lt;int name="value"&gt;5&lt;/int&gt;
+     &lt;/transformer&gt;
+     
+     If you want the user to still be able to change it with _value:something_ use this:
+     &lt;transformer name="mytrans3" class="org.apache.solr.response.transform.ValueAugmenterFactory" &gt;
+       &lt;double name="defaultValue"&gt;5&lt;/double&gt;
+     &lt;/transformer&gt;
+
+      If you are using the QueryElevationComponent, you may wish to mark documents that get boosted.  The
+      EditorialMarkerFactory will do exactly that:
+     &lt;transformer name="qecBooster" class="org.apache.solr.response.transform.EditorialMarkerFactory" /&gt;
+    --&gt;
+    
+
+  &lt;!-- Legacy config for the admin interface --&gt;
+  &lt;admin&gt;
+    &lt;defaultQuery&gt;*:*&lt;/defaultQuery&gt;
+  &lt;/admin&gt;
+
+&lt;/config&gt;
+    </value>
+  </property>
+
+  
+</configuration>  


Mime
View raw message