--- /dev/null
+<?xml version="1.0" encoding="UTF-8" ?>\r
+<!--\r
+ Licensed to the Apache Software Foundation (ASF) under one or more\r
+ contributor license agreements. See the NOTICE file distributed with\r
+ this work for additional information regarding copyright ownership.\r
+ The ASF licenses this file to You under the Apache License, Version 2.0\r
+ (the "License"); you may not use this file except in compliance with\r
+ the License. You may obtain a copy of the License at\r
+\r
+ http://www.apache.org/licenses/LICENSE-2.0\r
+\r
+ Unless required by applicable law or agreed to in writing, software\r
+ distributed under the License is distributed on an "AS IS" BASIS,\r
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\r
+ See the License for the specific language governing permissions and\r
+ limitations under the License.\r
+-->\r
+\r
+<!-- \r
+ For more details about configurations options that may appear in\r
+ this file, see http://wiki.apache.org/solr/SolrConfigXml. \r
+-->\r
+<config>\r
+ <!-- In all configuration below, a prefix of "solr." for class names\r
+ is an alias that causes solr to search appropriate packages,\r
+ including org.apache.solr.(search|update|request|core|analysis)\r
+\r
+ You may also specify a fully qualified Java classname if you\r
+ have your own custom plugins.\r
+ -->\r
+\r
+ <!-- Controls what version of Lucene various components of Solr\r
+ adhere to. Generally, you want to use the latest version to\r
+ get all bug fixes and improvements. It is highly recommended\r
+ that you fully re-index after changing this setting as it can\r
+ affect both how text is indexed and queried.\r
+ -->\r
+ <luceneMatchVersion>LUCENE_42</luceneMatchVersion>\r
+\r
+ <!-- <lib/> directives can be used to instruct Solr to load an Jars\r
+ identified and use them to resolve any "plugins" specified in\r
+ your solrconfig.xml or schema.xml (ie: Analyzers, Request\r
+ Handlers, etc...).\r
+\r
+ All directories and paths are resolved relative to the\r
+ instanceDir.\r
+\r
+ Please note that <lib/> directives are processed in the order\r
+ that they appear in your solrconfig.xml file, and are "stacked" \r
+ on top of each other when building a ClassLoader - so if you have \r
+ plugin jars with dependencies on other jars, the "lower level" \r
+ dependency jars should be loaded first.\r
+\r
+ If a "./lib" directory exists in your instanceDir, all files\r
+ found in it are included as if you had used the following\r
+ syntax...\r
+ \r
+ <lib dir="./lib" />\r
+ -->\r
+\r
+ <!-- A 'dir' option by itself adds any files found in the directory \r
+ to the classpath, this is useful for including all jars in a\r
+ directory.\r
+\r
+ When a 'regex' is specified in addition to a 'dir', only the\r
+ files in that directory which completely match the regex\r
+ (anchored on both ends) will be included.\r
+\r
+ The examples below can be used to load some solr-contribs along \r
+ with their external dependencies.\r
+ -->\r
+ <lib dir="../../../contrib/extraction/lib" regex=".*\.jar" />\r
+ <lib dir="../../../dist/" regex="solr-cell-\d.*\.jar" />\r
+\r
+ <lib dir="../../../contrib/clustering/lib/" regex=".*\.jar" />\r
+ <lib dir="../../../dist/" regex="solr-clustering-\d.*\.jar" />\r
+\r
+ <lib dir="../../../contrib/langid/lib/" regex=".*\.jar" />\r
+ <lib dir="../../../dist/" regex="solr-langid-\d.*\.jar" />\r
+\r
+ <lib dir="../../../contrib/velocity/lib" regex=".*\.jar" />\r
+ <lib dir="../../../dist/" regex="solr-velocity-\d.*\.jar" />\r
+\r
+ <!-- If a 'dir' option (with or without a regex) is used and nothing\r
+ is found that matches, it will be ignored\r
+ -->\r
+ <lib dir="/total/crap/dir/ignored" /> \r
+\r
+ <!-- an exact 'path' can be used instead of a 'dir' to specify a \r
+ specific jar file. This will cause a serious error to be logged \r
+ if it can't be loaded.\r
+ -->\r
+ <!--\r
+ <lib path="../a-jar-that-does-not-exist.jar" /> \r
+ -->\r
+ \r
+ <!-- Data Directory\r
+\r
+ Used to specify an alternate directory to hold all index data\r
+ other than the default ./data under the Solr home. If\r
+ replication is in use, this should match the replication\r
+ configuration.\r
+ -->\r
+ <dataDir>${solr.data.dir:}</dataDir>\r
+\r
+\r
+ <!-- The DirectoryFactory to use for indexes.\r
+ \r
+ solr.StandardDirectoryFactory is filesystem\r
+ based and tries to pick the best implementation for the current\r
+ JVM and platform. solr.NRTCachingDirectoryFactory, the default,\r
+ wraps solr.StandardDirectoryFactory and caches small files in memory\r
+ for better NRT performance.\r
+\r
+ One can force a particular implementation via solr.MMapDirectoryFactory,\r
+ solr.NIOFSDirectoryFactory, or solr.SimpleFSDirectoryFactory.\r
+\r
+ solr.RAMDirectoryFactory is memory based, not\r
+ persistent, and doesn't work with replication.\r
+ -->\r
+ <directoryFactory name="DirectoryFactory" \r
+ class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"/> \r
+\r
+ <!-- The CodecFactory for defining the format of the inverted index.\r
+ The default implementation is SchemaCodecFactory, which is the official Lucene\r
+ index format, but hooks into the schema to provide per-field customization of\r
+ the postings lists and per-document values in the fieldType element\r
+ (postingsFormat/docValuesFormat). Note that most of the alternative implementations\r
+ are experimental, so if you choose to customize the index format, its a good\r
+ idea to convert back to the official format e.g. via IndexWriter.addIndexes(IndexReader)\r
+ before upgrading to a newer version to avoid unnecessary reindexing.\r
+ -->\r
+ <codecFactory class="solr.SchemaCodecFactory"/>\r
+\r
+ <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
+ Index Config - These settings control low-level behavior of indexing\r
+ Most example settings here show the default value, but are commented\r
+ out, to more easily see where customizations have been made.\r
+ \r
+ Note: This replaces <indexDefaults> and <mainIndex> from older versions\r
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->\r
+ <indexConfig>\r
+ <!-- maxFieldLength was removed in 4.0. To get similar behavior, include a \r
+ LimitTokenCountFilterFactory in your fieldType definition. E.g. \r
+ <filter class="solr.LimitTokenCountFilterFactory" maxTokenCount="10000"/>\r
+ -->\r
+ <!-- Maximum time to wait for a write lock (ms) for an IndexWriter. Default: 1000 -->\r
+ <!-- <writeLockTimeout>1000</writeLockTimeout> -->\r
+\r
+ <!-- The maximum number of simultaneous threads that may be\r
+ indexing documents at once in IndexWriter; if more than this\r
+ many threads arrive they will wait for others to finish.\r
+ Default in Solr/Lucene is 8. -->\r
+ <!-- <maxIndexingThreads>8</maxIndexingThreads> -->\r
+\r
+ <!-- Expert: Enabling compound file will use less files for the index, \r
+ using fewer file descriptors on the expense of performance decrease. \r
+ Default in Lucene is "true". Default in Solr is "false" (since 3.6) -->\r
+ <!-- <useCompoundFile>false</useCompoundFile> -->\r
+\r
+ <!-- ramBufferSizeMB sets the amount of RAM that may be used by Lucene\r
+ indexing for buffering added documents and deletions before they are\r
+ flushed to the Directory.\r
+ maxBufferedDocs sets a limit on the number of documents buffered\r
+ before flushing.\r
+ If both ramBufferSizeMB and maxBufferedDocs is set, then\r
+ Lucene will flush based on whichever limit is hit first. -->\r
+ <!-- <ramBufferSizeMB>100</ramBufferSizeMB> -->\r
+ <!-- <maxBufferedDocs>1000</maxBufferedDocs> -->\r
+\r
+ <!-- Expert: Merge Policy \r
+ The Merge Policy in Lucene controls how merging of segments is done.\r
+ The default since Solr/Lucene 3.3 is TieredMergePolicy.\r
+ The default since Lucene 2.3 was the LogByteSizeMergePolicy,\r
+ Even older versions of Lucene used LogDocMergePolicy.\r
+ -->\r
+ <!--\r
+ <mergePolicy class="org.apache.lucene.index.TieredMergePolicy">\r
+ <int name="maxMergeAtOnce">10</int>\r
+ <int name="segmentsPerTier">10</int>\r
+ </mergePolicy>\r
+ -->\r
+ \r
+ <!-- Merge Factor\r
+ The merge factor controls how many segments will get merged at a time.\r
+ For TieredMergePolicy, mergeFactor is a convenience parameter which\r
+ will set both MaxMergeAtOnce and SegmentsPerTier at once.\r
+ For LogByteSizeMergePolicy, mergeFactor decides how many new segments\r
+ will be allowed before they are merged into one.\r
+ Default is 10 for both merge policies.\r
+ -->\r
+ <!-- \r
+ <mergeFactor>10</mergeFactor>\r
+ -->\r
+\r
+ <!-- Expert: Merge Scheduler\r
+ The Merge Scheduler in Lucene controls how merges are\r
+ performed. The ConcurrentMergeScheduler (Lucene 2.3 default)\r
+ can perform merges in the background using separate threads.\r
+ The SerialMergeScheduler (Lucene 2.2 default) does not.\r
+ -->\r
+ <!-- \r
+ <mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>\r
+ -->\r
+\r
+ <!-- LockFactory \r
+\r
+ This option specifies which Lucene LockFactory implementation\r
+ to use.\r
+ \r
+ single = SingleInstanceLockFactory - suggested for a\r
+ read-only index or when there is no possibility of\r
+ another process trying to modify the index.\r
+ native = NativeFSLockFactory - uses OS native file locking.\r
+ Do not use when multiple solr webapps in the same\r
+ JVM are attempting to share a single index.\r
+ simple = SimpleFSLockFactory - uses a plain file for locking\r
+\r
+ Defaults: 'native' is default for Solr3.6 and later, otherwise\r
+ 'simple' is the default\r
+\r
+ More details on the nuances of each LockFactory...\r
+ http://wiki.apache.org/lucene-java/AvailableLockFactories\r
+ -->\r
+ <lockType>${solr.lock.type:native}</lockType>\r
+\r
+ <!-- Unlock On Startup\r
+\r
+ If true, unlock any held write or commit locks on startup.\r
+ This defeats the locking mechanism that allows multiple\r
+ processes to safely access a lucene index, and should be used\r
+ with care. Default is "false".\r
+\r
+ This is not needed if lock type is 'single'\r
+ -->\r
+ <!--\r
+ <unlockOnStartup>false</unlockOnStartup>\r
+ -->\r
+ \r
+ <!-- Expert: Controls how often Lucene loads terms into memory\r
+ Default is 128 and is likely good for most everyone.\r
+ -->\r
+ <!-- <termIndexInterval>128</termIndexInterval> -->\r
+\r
+ <!-- If true, IndexReaders will be reopened (often more efficient)\r
+ instead of closed and then opened. Default: true\r
+ -->\r
+ <!-- \r
+ <reopenReaders>true</reopenReaders>\r
+ -->\r
+\r
+ <!-- Commit Deletion Policy\r
+ Custom deletion policies can be specified here. The class must\r
+ implement org.apache.lucene.index.IndexDeletionPolicy.\r
+\r
+ The default Solr IndexDeletionPolicy implementation supports\r
+ deleting index commit points on number of commits, age of\r
+ commit point and optimized status.\r
+ \r
+ The latest commit point should always be preserved regardless\r
+ of the criteria.\r
+ -->\r
+ <!-- \r
+ <deletionPolicy class="solr.SolrDeletionPolicy">\r
+ -->\r
+ <!-- The number of commit points to be kept -->\r
+ <!-- <str name="maxCommitsToKeep">1</str> -->\r
+ <!-- The number of optimized commit points to be kept -->\r
+ <!-- <str name="maxOptimizedCommitsToKeep">0</str> -->\r
+ <!--\r
+ Delete all commit points once they have reached the given age.\r
+ Supports DateMathParser syntax e.g.\r
+ -->\r
+ <!--\r
+ <str name="maxCommitAge">30MINUTES</str>\r
+ <str name="maxCommitAge">1DAY</str>\r
+ -->\r
+ <!-- \r
+ </deletionPolicy>\r
+ -->\r
+\r
+ <!-- Lucene Infostream\r
+ \r
+ To aid in advanced debugging, Lucene provides an "InfoStream"\r
+ of detailed information when indexing.\r
+\r
+ Setting The value to true will instruct the underlying Lucene\r
+ IndexWriter to write its debugging info the specified file\r
+ -->\r
+ <!-- <infoStream file="INFOSTREAM.txt">false</infoStream> --> \r
+ </indexConfig>\r
+\r
+\r
+ <!-- JMX\r
+ \r
+ This example enables JMX if and only if an existing MBeanServer\r
+ is found, use this if you want to configure JMX through JVM\r
+ parameters. Remove this to disable exposing Solr configuration\r
+ and statistics to JMX.\r
+\r
+ For more details see http://wiki.apache.org/solr/SolrJmx\r
+ -->\r
+ <jmx />\r
+ <!-- If you want to connect to a particular server, specify the\r
+ agentId \r
+ -->\r
+ <!-- <jmx agentId="myAgent" /> -->\r
+ <!-- If you want to start a new MBeanServer, specify the serviceUrl -->\r
+ <!-- <jmx serviceUrl="service:jmx:rmi:///jndi/rmi://localhost:9999/solr"/>\r
+ -->\r
+\r
+ <!-- The default high-performance update handler -->\r
+ <updateHandler class="solr.DirectUpdateHandler2">\r
+\r
+ <!-- Enables a transaction log, used for real-time get, durability, and\r
+ and solr cloud replica recovery. The log can grow as big as\r
+ uncommitted changes to the index, so use of a hard autoCommit\r
+ is recommended (see below).\r
+ "dir" - the target directory for transaction logs, defaults to the\r
+ solr data directory. --> \r
+ <updateLog>\r
+ <str name="dir">${solr.ulog.dir:}</str>\r
+ </updateLog>\r
+ \r
+ <!-- AutoCommit\r
+\r
+ Perform a hard commit automatically under certain conditions.\r
+ Instead of enabling autoCommit, consider using "commitWithin"\r
+ when adding documents. \r
+\r
+ http://wiki.apache.org/solr/UpdateXmlMessages\r
+\r
+ maxDocs - Maximum number of documents to add since the last\r
+ commit before automatically triggering a new commit.\r
+\r
+ maxTime - Maximum amount of time in ms that is allowed to pass\r
+ since a document was added before automatically\r
+ triggering a new commit. \r
+ openSearcher - if false, the commit causes recent index changes\r
+ to be flushed to stable storage, but does not cause a new\r
+ searcher to be opened to make those changes visible.\r
+\r
+ If the updateLog is enabled, then it's highly recommended to\r
+ have some sort of hard autoCommit to limit the log size.\r
+ -->\r
+ <autoCommit> \r
+ <maxTime>15000</maxTime> \r
+ <openSearcher>false</openSearcher> \r
+ </autoCommit>\r
+\r
+ <!-- softAutoCommit is like autoCommit except it causes a\r
+ 'soft' commit which only ensures that changes are visible\r
+ but does not ensure that data is synced to disk. This is\r
+ faster and more near-realtime friendly than a hard commit.\r
+ -->\r
+ <!--\r
+ <autoSoftCommit> \r
+ <maxTime>1000</maxTime> \r
+ </autoSoftCommit>\r
+ -->\r
+\r
+ <!-- Update Related Event Listeners\r
+ \r
+ Various IndexWriter related events can trigger Listeners to\r
+ take actions.\r
+\r
+ postCommit - fired after every commit or optimize command\r
+ postOptimize - fired after every optimize command\r
+ -->\r
+ <!-- The RunExecutableListener executes an external command from a\r
+ hook such as postCommit or postOptimize.\r
+ \r
+ exe - the name of the executable to run\r
+ dir - dir to use as the current working directory. (default=".")\r
+ wait - the calling thread waits until the executable returns. \r
+ (default="true")\r
+ args - the arguments to pass to the program. (default is none)\r
+ env - environment variables to set. (default is none)\r
+ -->\r
+ <!-- This example shows how RunExecutableListener could be used\r
+ with the script based replication...\r
+ http://wiki.apache.org/solr/CollectionDistribution\r
+ -->\r
+ <!--\r
+ <listener event="postCommit" class="solr.RunExecutableListener">\r
+ <str name="exe">solr/bin/snapshooter</str>\r
+ <str name="dir">.</str>\r
+ <bool name="wait">true</bool>\r
+ <arr name="args"> <str>arg1</str> <str>arg2</str> </arr>\r
+ <arr name="env"> <str>MYVAR=val1</str> </arr>\r
+ </listener>\r
+ -->\r
+\r
+ </updateHandler>\r
+ \r
+ <!-- IndexReaderFactory\r
+\r
+ Use the following format to specify a custom IndexReaderFactory,\r
+ which allows for alternate IndexReader implementations.\r
+\r
+ ** Experimental Feature **\r
+\r
+ Please note - Using a custom IndexReaderFactory may prevent\r
+ certain other features from working. The API to\r
+ IndexReaderFactory may change without warning or may even be\r
+ removed from future releases if the problems cannot be\r
+ resolved.\r
+\r
+\r
+ ** Features that may not work with custom IndexReaderFactory **\r
+\r
+ The ReplicationHandler assumes a disk-resident index. Using a\r
+ custom IndexReader implementation may cause incompatibility\r
+ with ReplicationHandler and may cause replication to not work\r
+ correctly. See SOLR-1366 for details.\r
+\r
+ -->\r
+ <!--\r
+ <indexReaderFactory name="IndexReaderFactory" class="package.class">\r
+ <str name="someArg">Some Value</str>\r
+ </indexReaderFactory >\r
+ -->\r
+ <!-- By explicitly declaring the Factory, the termIndexDivisor can\r
+ be specified.\r
+ -->\r
+ <!--\r
+ <indexReaderFactory name="IndexReaderFactory" \r
+ class="solr.StandardIndexReaderFactory">\r
+ <int name="setTermIndexDivisor">12</int>\r
+ </indexReaderFactory >\r
+ -->\r
+\r
+ <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r
+ Query section - these settings control query time things like caches\r
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->\r
+ <query>\r
+ <!-- Max Boolean Clauses\r
+\r
+ Maximum number of clauses in each BooleanQuery, an exception\r
+ is thrown if exceeded.\r
+\r
+ ** WARNING **\r
+ \r
+ This option actually modifies a global Lucene property that\r
+ will affect all SolrCores. If multiple solrconfig.xml files\r
+ disagree on this property, the value at any given moment will\r
+ be based on the last SolrCore to be initialized.\r
+ \r
+ -->\r
+ <maxBooleanClauses>1024</maxBooleanClauses>\r
+\r
+\r
+ <!-- Solr Internal Query Caches\r
+\r
+ There are two implementations of cache available for Solr,\r
+ LRUCache, based on a synchronized LinkedHashMap, and\r
+ FastLRUCache, based on a ConcurrentHashMap. \r
+\r
+ FastLRUCache has faster gets and slower puts in single\r
+ threaded operation and thus is generally faster than LRUCache\r
+ when the hit ratio of the cache is high (> 75%), and may be\r
+ faster under other scenarios on multi-cpu systems.\r
+ -->\r
+\r
+ <!-- Filter Cache\r
+\r
+ Cache used by SolrIndexSearcher for filters (DocSets),\r
+ unordered sets of *all* documents that match a query. When a\r
+ new searcher is opened, its caches may be prepopulated or\r
+ "autowarmed" using data from caches in the old searcher.\r
+ autowarmCount is the number of items to prepopulate. For\r
+ LRUCache, the autowarmed items will be the most recently\r
+ accessed items.\r
+\r
+ Parameters:\r
+ class - the SolrCache implementation LRUCache or\r
+ (LRUCache or FastLRUCache)\r
+ size - the maximum number of entries in the cache\r
+ initialSize - the initial capacity (number of entries) of\r
+ the cache. (see java.util.HashMap)\r
+ autowarmCount - the number of entries to prepopulate from\r
+ and old cache. \r
+ -->\r
+ <filterCache class="solr.FastLRUCache"\r
+ size="512"\r
+ initialSize="512"\r
+ autowarmCount="0"/>\r
+\r
+ <!-- Query Result Cache\r
+ \r
+ Caches results of searches - ordered lists of document ids\r
+ (DocList) based on a query, a sort, and the range of documents requested. \r
+ -->\r
+ <queryResultCache class="solr.LRUCache"\r
+ size="512"\r
+ initialSize="512"\r
+ autowarmCount="0"/>\r
+ \r
+ <!-- Document Cache\r
+\r
+ Caches Lucene Document objects (the stored fields for each\r
+ document). Since Lucene internal document ids are transient,\r
+ this cache will not be autowarmed. \r
+ -->\r
+ <documentCache class="solr.LRUCache"\r
+ size="512"\r
+ initialSize="512"\r
+ autowarmCount="0"/>\r
+ \r
+ <!-- Field Value Cache\r
+ \r
+ Cache used to hold field values that are quickly accessible\r
+ by document id. The fieldValueCache is created by default\r
+ even if not configured here.\r
+ -->\r
+ <!--\r
+ <fieldValueCache class="solr.FastLRUCache"\r
+ size="512"\r
+ autowarmCount="128"\r
+ showItems="32" />\r
+ -->\r
+\r
+ <!-- Custom Cache\r
+\r
+ Example of a generic cache. These caches may be accessed by\r
+ name through SolrIndexSearcher.getCache(),cacheLookup(), and\r
+ cacheInsert(). The purpose is to enable easy caching of\r
+ user/application level data. The regenerator argument should\r
+ be specified as an implementation of solr.CacheRegenerator \r
+ if autowarming is desired. \r
+ -->\r
+ <!--\r
+ <cache name="myUserCache"\r
+ class="solr.LRUCache"\r
+ size="4096"\r
+ initialSize="1024"\r
+ autowarmCount="1024"\r
+ regenerator="com.mycompany.MyRegenerator"\r
+ />\r
+ -->\r
+\r
+\r
+ <!-- Lazy Field Loading\r
+\r
+ If true, stored fields that are not requested will be loaded\r
+ lazily. This can result in a significant speed improvement\r
+ if the usual case is to not load all stored fields,\r
+ especially if the skipped fields are large compressed text\r
+ fields.\r
+ -->\r
+ <enableLazyFieldLoading>true</enableLazyFieldLoading>\r
+\r
+ <!-- Use Filter For Sorted Query\r
+\r
+ A possible optimization that attempts to use a filter to\r
+ satisfy a search. If the requested sort does not include\r
+ score, then the filterCache will be checked for a filter\r
+ matching the query. If found, the filter will be used as the\r
+ source of document ids, and then the sort will be applied to\r
+ that.\r
+\r
+ For most situations, this will not be useful unless you\r
+ frequently get the same search repeatedly with different sort\r
+ options, and none of them ever use "score"\r
+ -->\r
+ <!--\r
+ <useFilterForSortedQuery>true</useFilterForSortedQuery>\r
+ -->\r
+\r
+ <!-- Result Window Size\r
+\r
+ An optimization for use with the queryResultCache. When a search\r
+ is requested, a superset of the requested number of document ids\r
+ are collected. For example, if a search for a particular query\r
+ requests matching documents 10 through 19, and queryWindowSize is 50,\r
+ then documents 0 through 49 will be collected and cached. Any further\r
+ requests in that range can be satisfied via the cache. \r
+ -->\r
+ <queryResultWindowSize>20</queryResultWindowSize>\r
+\r
+ <!-- Maximum number of documents to cache for any entry in the\r
+ queryResultCache. \r
+ -->\r
+ <queryResultMaxDocsCached>200</queryResultMaxDocsCached>\r
+\r
+ <!-- Query Related Event Listeners\r
+\r
+ Various IndexSearcher related events can trigger Listeners to\r
+ take actions.\r
+\r
+ newSearcher - fired whenever a new searcher is being prepared\r
+ and there is a current searcher handling requests (aka\r
+ registered). It can be used to prime certain caches to\r
+ prevent long request times for certain requests.\r
+\r
+ firstSearcher - fired whenever a new searcher is being\r
+ prepared but there is no current registered searcher to handle\r
+ requests or to gain autowarming data from.\r
+\r
+ \r
+ -->\r
+ <!-- QuerySenderListener takes an array of NamedList and executes a\r
+ local query request for each NamedList in sequence. \r
+ -->\r
+ <listener event="newSearcher" class="solr.QuerySenderListener">\r
+ <arr name="queries">\r
+ <!--\r
+ <lst><str name="q">solr</str><str name="sort">price asc</str></lst>\r
+ <lst><str name="q">rocks</str><str name="sort">weight asc</str></lst>\r
+ -->\r
+ </arr>\r
+ </listener>\r
+ <listener event="firstSearcher" class="solr.QuerySenderListener">\r
+ <arr name="queries">\r
+ <lst>\r
+ <str name="q">static firstSearcher warming in solrconfig.xml</str>\r
+ </lst>\r
+ </arr>\r
+ </listener>\r
+\r
+ <!-- Use Cold Searcher\r
+\r
+ If a search request comes in and there is no current\r
+ registered searcher, then immediately register the still\r
+ warming searcher and use it. If "false" then all requests\r
+ will block until the first searcher is done warming.\r
+ -->\r
+ <useColdSearcher>false</useColdSearcher>\r
+\r
+ <!-- Max Warming Searchers\r
+ \r
+ Maximum number of searchers that may be warming in the\r
+ background concurrently. An error is returned if this limit\r
+ is exceeded.\r
+\r
+ Recommend values of 1-2 for read-only slaves, higher for\r
+ masters w/o cache warming.\r
+ -->\r
+ <maxWarmingSearchers>2</maxWarmingSearchers>\r
+\r
+ </query>\r
+\r
+\r
+ <!-- Request Dispatcher\r
+\r
+ This section contains instructions for how the SolrDispatchFilter\r
+ should behave when processing requests for this SolrCore.\r
+\r
+ handleSelect is a legacy option that affects the behavior of requests\r
+ such as /select?qt=XXX\r
+\r
+ handleSelect="true" will cause the SolrDispatchFilter to process\r
+ the request and dispatch the query to a handler specified by the \r
+ "qt" param, assuming "/select" isn't already registered.\r
+\r
+ handleSelect="false" will cause the SolrDispatchFilter to\r
+ ignore "/select" requests, resulting in a 404 unless a handler\r
+ is explicitly registered with the name "/select"\r
+\r
+ handleSelect="true" is not recommended for new users, but is the default\r
+ for backwards compatibility\r
+ -->\r
+ <requestDispatcher handleSelect="false" >\r
+ <!-- Request Parsing\r
+\r
+ These settings indicate how Solr Requests may be parsed, and\r
+ what restrictions may be placed on the ContentStreams from\r
+ those requests\r
+\r
+ enableRemoteStreaming - enables use of the stream.file\r
+ and stream.url parameters for specifying remote streams.\r
+\r
+ multipartUploadLimitInKB - specifies the max size (in KiB) of\r
+ Multipart File Uploads that Solr will allow in a Request.\r
+ \r
+ formdataUploadLimitInKB - specifies the max size (in KiB) of\r
+ form data (application/x-www-form-urlencoded) sent via\r
+ POST. You can use POST to pass request parameters not\r
+ fitting into the URL.\r
+ \r
+ *** WARNING ***\r
+ The settings below authorize Solr to fetch remote files, You\r
+ should make sure your system has some authentication before\r
+ using enableRemoteStreaming="true"\r
+\r
+ --> \r
+ <requestParsers enableRemoteStreaming="true" \r
+ multipartUploadLimitInKB="2048000"\r
+ formdataUploadLimitInKB="2048"/>\r
+\r
+ <!-- HTTP Caching\r
+\r
+ Set HTTP caching related parameters (for proxy caches and clients).\r
+\r
+ The options below instruct Solr not to output any HTTP Caching\r
+ related headers\r
+ -->\r
+ <httpCaching never304="true" />\r
+ <!-- If you include a <cacheControl> directive, it will be used to\r
+ generate a Cache-Control header (as well as an Expires header\r
+ if the value contains "max-age=")\r
+ \r
+ By default, no Cache-Control header is generated.\r
+ \r
+ You can use the <cacheControl> option even if you have set\r
+ never304="true"\r
+ -->\r
+ <!--\r
+ <httpCaching never304="true" >\r
+ <cacheControl>max-age=30, public</cacheControl> \r
+ </httpCaching>\r
+ -->\r
+ <!-- To enable Solr to respond with automatically generated HTTP\r
+ Caching headers, and to response to Cache Validation requests\r
+ correctly, set the value of never304="false"\r
+ \r
+ This will cause Solr to generate Last-Modified and ETag\r
+ headers based on the properties of the Index.\r
+\r
+ The following options can also be specified to affect the\r
+ values of these headers...\r
+\r
+ lastModFrom - the default value is "openTime" which means the\r
+ Last-Modified value (and validation against If-Modified-Since\r
+ requests) will all be relative to when the current Searcher\r
+ was opened. You can change it to lastModFrom="dirLastMod" if\r
+ you want the value to exactly correspond to when the physical\r
+ index was last modified.\r
+\r
+ etagSeed="..." is an option you can change to force the ETag\r
+ header (and validation against If-None-Match requests) to be\r
+ different even if the index has not changed (ie: when making\r
+ significant changes to your config file)\r
+\r
+ (lastModifiedFrom and etagSeed are both ignored if you use\r
+ the never304="true" option)\r
+ -->\r
+ <!--\r
+ <httpCaching lastModifiedFrom="openTime"\r
+ etagSeed="Solr">\r
+ <cacheControl>max-age=30, public</cacheControl> \r
+ </httpCaching>\r
+ -->\r
+ </requestDispatcher>\r
+\r
+ <!-- Request Handlers \r
+\r
+ http://wiki.apache.org/solr/SolrRequestHandler\r
+\r
+ Incoming queries will be dispatched to a specific handler by name\r
+ based on the path specified in the request.\r
+\r
+ Legacy behavior: If the request path uses "/select" but no Request\r
+ Handler has that name, and if handleSelect="true" has been specified in\r
+ the requestDispatcher, then the Request Handler is dispatched based on\r
+ the qt parameter. Handlers without a leading '/' are accessed this way\r
+ like so: http://host/app/[core/]select?qt=name If no qt is\r
+ given, then the requestHandler that declares default="true" will be\r
+ used or the one named "standard".\r
+\r
+ If a Request Handler is declared with startup="lazy", then it will\r
+ not be initialized until the first request that uses it.\r
+\r
+ -->\r
+ <!-- SearchHandler\r
+\r
+ http://wiki.apache.org/solr/SearchHandler\r
+\r
+ For processing Search Queries, the primary Request Handler\r
+ provided with Solr is "SearchHandler" It delegates to a sequent\r
+ of SearchComponents (see below) and supports distributed\r
+ queries across multiple shards\r
+ -->\r
+ <requestHandler name="/select" class="solr.SearchHandler">\r
+ <!-- default values for query parameters can be specified, these\r
+ will be overridden by parameters in the request\r
+ -->\r
+ <lst name="defaults">\r
+ <str name="echoParams">explicit</str>\r
+ <int name="rows">10</int>\r
+ <str name="df">text</str>\r
+ </lst>\r
+ <!-- In addition to defaults, "appends" params can be specified\r
+ to identify values which should be appended to the list of\r
+ multi-val params from the query (or the existing "defaults").\r
+ -->\r
+ <!-- In this example, the param "fq=instock:true" would be appended to\r
+ any query time fq params the user may specify, as a mechanism for\r
+ partitioning the index, independent of any user selected filtering\r
+ that may also be desired (perhaps as a result of faceted searching).\r
+\r
+ NOTE: there is *absolutely* nothing a client can do to prevent these\r
+ "appends" values from being used, so don't use this mechanism\r
+ unless you are sure you always want it.\r
+ -->\r
+ <!--\r
+ <lst name="appends">\r
+ <str name="fq">inStock:true</str>\r
+ </lst>\r
+ -->\r
+ <!-- "invariants" are a way of letting the Solr maintainer lock down\r
+ the options available to Solr clients. Any params values\r
+ specified here are used regardless of what values may be specified\r
+ in either the query, the "defaults", or the "appends" params.\r
+\r
+ In this example, the facet.field and facet.query params would\r
+ be fixed, limiting the facets clients can use. Faceting is\r
+ not turned on by default - but if the client does specify\r
+ facet=true in the request, these are the only facets they\r
+ will be able to see counts for; regardless of what other\r
+ facet.field or facet.query params they may specify.\r
+\r
+ NOTE: there is *absolutely* nothing a client can do to prevent these\r
+ "invariants" values from being used, so don't use this mechanism\r
+ unless you are sure you always want it.\r
+ -->\r
+ <!--\r
+ <lst name="invariants">\r
+ <str name="facet.field">cat</str>\r
+ <str name="facet.field">manu_exact</str>\r
+ <str name="facet.query">price:[* TO 500]</str>\r
+ <str name="facet.query">price:[500 TO *]</str>\r
+ </lst>\r
+ -->\r
+ <!-- If the default list of SearchComponents is not desired, that\r
+ list can either be overridden completely, or components can be\r
+ prepended or appended to the default list. (see below)\r
+ -->\r
+ <!--\r
+ <arr name="components">\r
+ <str>nameOfCustomComponent1</str>\r
+ <str>nameOfCustomComponent2</str>\r
+ </arr>\r
+ -->\r
+ <!-- A request handler that returns indented JSON by default -->\r
+ </requestHandler>\r
+\r
+ <requestHandler name="/query" class="solr.SearchHandler">\r
+ <lst name="defaults">\r
+ <str name="echoParams">explicit</str>\r
+ <str name="wt">json</str>\r
+ <str name="indent">true</str>\r
+ <str name="df">text</str>\r
+ </lst>\r
+ </requestHandler>\r
+\r
+\r
+ <!-- realtime get handler, guaranteed to return the latest stored fields of\r
+ any document, without the need to commit or open a new searcher. The\r
+ current implementation relies on the updateLog feature being enabled. -->\r
+ <requestHandler name="/get" class="solr.RealTimeGetHandler">\r
+ <lst name="defaults">\r
+ <str name="omitHeader">true</str>\r
+ <str name="wt">json</str>\r
+ <str name="indent">true</str>\r
+ </lst>\r
+ </requestHandler>\r
+\r
+ \r
+ <!-- A Robust Example \r
+ \r
+ This example SearchHandler declaration shows off usage of the\r
+ SearchHandler with many defaults declared\r
+\r
+ Note that multiple instances of the same Request Handler\r
+ (SearchHandler) can be registered multiple times with different\r
+ names (and different init parameters)\r
+ -->\r
+ <requestHandler name="/browse" class="solr.SearchHandler">\r
+ <lst name="defaults">\r
+ <str name="echoParams">explicit</str>\r
+\r
+ <!-- VelocityResponseWriter settings -->\r
+ <str name="wt">velocity</str>\r
+ <str name="v.template">browse</str>\r
+ <str name="v.layout">layout</str>\r
+ <str name="title">Solritas</str>\r
+\r
+ <!-- Query settings -->\r
+ <str name="defType">edismax</str>\r
+ <str name="qf">\r
+ text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4\r
+ title^10.0 description^5.0 keywords^5.0 author^2.0 resourcename^1.0\r
+ </str>\r
+ <str name="df">text</str>\r
+ <str name="mm">100%</str>\r
+ <str name="q.alt">*:*</str>\r
+ <str name="rows">10</str>\r
+ <str name="fl">*,score</str>\r
+\r
+ <str name="mlt.qf">\r
+ text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4\r
+ title^10.0 description^5.0 keywords^5.0 author^2.0 resourcename^1.0\r
+ </str>\r
+ <str name="mlt.fl">text,features,name,sku,id,manu,cat,title,description,keywords,author,resourcename</str>\r
+ <int name="mlt.count">3</int>\r
+\r
+ <!-- Faceting defaults -->\r
+ <str name="facet">on</str>\r
+ <str name="facet.field">cat</str>\r
+ <str name="facet.field">manu_exact</str>\r
+ <str name="facet.field">content_type</str>\r
+ <str name="facet.field">author_s</str>\r
+ <str name="facet.query">ipod</str>\r
+ <str name="facet.query">GB</str>\r
+ <str name="facet.mincount">1</str>\r
+ <str name="facet.pivot">cat,inStock</str>\r
+ <str name="facet.range.other">after</str>\r
+ <str name="facet.range">price</str>\r
+ <int name="f.price.facet.range.start">0</int>\r
+ <int name="f.price.facet.range.end">600</int>\r
+ <int name="f.price.facet.range.gap">50</int>\r
+ <str name="facet.range">popularity</str>\r
+ <int name="f.popularity.facet.range.start">0</int>\r
+ <int name="f.popularity.facet.range.end">10</int>\r
+ <int name="f.popularity.facet.range.gap">3</int>\r
+ <str name="facet.range">manufacturedate_dt</str>\r
+ <str name="f.manufacturedate_dt.facet.range.start">NOW/YEAR-10YEARS</str>\r
+ <str name="f.manufacturedate_dt.facet.range.end">NOW</str>\r
+ <str name="f.manufacturedate_dt.facet.range.gap">+1YEAR</str>\r
+ <str name="f.manufacturedate_dt.facet.range.other">before</str>\r
+ <str name="f.manufacturedate_dt.facet.range.other">after</str>\r
+\r
+ <!-- Highlighting defaults -->\r
+ <str name="hl">on</str>\r
+ <str name="hl.fl">content features title name</str>\r
+ <str name="hl.encoder">html</str>\r
+ <str name="hl.simple.pre"><b></str>\r
+ <str name="hl.simple.post"></b></str>\r
+ <str name="f.title.hl.fragsize">0</str>\r
+ <str name="f.title.hl.alternateField">title</str>\r
+ <str name="f.name.hl.fragsize">0</str>\r
+ <str name="f.name.hl.alternateField">name</str>\r
+ <str name="f.content.hl.snippets">3</str>\r
+ <str name="f.content.hl.fragsize">200</str>\r
+ <str name="f.content.hl.alternateField">content</str>\r
+ <str name="f.content.hl.maxAlternateFieldLength">750</str>\r
+\r
+ <!-- Spell checking defaults -->\r
+ <str name="spellcheck">on</str>\r
+ <str name="spellcheck.extendedResults">false</str> \r
+ <str name="spellcheck.count">5</str>\r
+ <str name="spellcheck.alternativeTermCount">2</str>\r
+ <str name="spellcheck.maxResultsForSuggest">5</str> \r
+ <str name="spellcheck.collate">true</str>\r
+ <str name="spellcheck.collateExtendedResults">true</str> \r
+ <str name="spellcheck.maxCollationTries">5</str>\r
+ <str name="spellcheck.maxCollations">3</str> \r
+ </lst>\r
+\r
+ <!-- append spellchecking to our list of components -->\r
+ <arr name="last-components">\r
+ <str>spellcheck</str>\r
+ </arr>\r
+ </requestHandler>\r
+\r
+\r
+ <!-- Update Request Handler. \r
+ \r
+ http://wiki.apache.org/solr/UpdateXmlMessages\r
+\r
+ The canonical Request Handler for Modifying the Index through\r
+ commands specified using XML, JSON, CSV, or JAVABIN\r
+\r
+ Note: Since solr1.1 requestHandlers requires a valid content\r
+ type header if posted in the body. For example, curl now\r
+ requires: -H 'Content-type:text/xml; charset=utf-8'\r
+ \r
+ To override the request content type and force a specific \r
+ Content-type, use the request parameter: \r
+ ?update.contentType=text/csv\r
+ \r
+ This handler will pick a response format to match the input\r
+ if the 'wt' parameter is not explicit\r
+ -->\r
+ <requestHandler name="/update" class="solr.UpdateRequestHandler">\r
+ <!-- See below for information on defining \r
+ updateRequestProcessorChains that can be used by name \r
+ on each Update Request\r
+ -->\r
+ <!--\r
+ <lst name="defaults">\r
+ <str name="update.chain">dedupe</str>\r
+ </lst>\r
+ -->\r
+ </requestHandler>\r
+\r
+ <!-- for back compat with clients using /update/json and /update/csv --> \r
+ <requestHandler name="/update/json" class="solr.JsonUpdateRequestHandler">\r
+ <lst name="defaults">\r
+ <str name="stream.contentType">application/json</str>\r
+ </lst>\r
+ </requestHandler>\r
+ <requestHandler name="/update/csv" class="solr.CSVRequestHandler">\r
+ <lst name="defaults">\r
+ <str name="stream.contentType">application/csv</str>\r
+ </lst>\r
+ </requestHandler>\r
+\r
+ <!-- Solr Cell Update Request Handler\r
+\r
+ http://wiki.apache.org/solr/ExtractingRequestHandler \r
+\r
+ -->\r
+ <requestHandler name="/update/extract" \r
+ startup="lazy"\r
+ class="solr.extraction.ExtractingRequestHandler" >\r
+ <lst name="defaults">\r
+ <str name="lowernames">true</str>\r
+ <str name="uprefix">ignored_</str>\r
+\r
+ <!-- capture link hrefs but ignore div attributes -->\r
+ <str name="captureAttr">true</str>\r
+ <str name="fmap.a">links</str>\r
+ <str name="fmap.div">ignored_</str>\r
+ </lst>\r
+ </requestHandler>\r
+\r
+\r
+ <!-- Field Analysis Request Handler\r
+\r
+ RequestHandler that provides much the same functionality as\r
+ analysis.jsp. Provides the ability to specify multiple field\r
+ types and field names in the same request and outputs\r
+ index-time and query-time analysis for each of them.\r
+\r
+ Request parameters are:\r
+ analysis.fieldname - field name whose analyzers are to be used\r
+\r
+ analysis.fieldtype - field type whose analyzers are to be used\r
+ analysis.fieldvalue - text for index-time analysis\r
+ q (or analysis.q) - text for query time analysis\r
+ analysis.showmatch (true|false) - When set to true and when\r
+ query analysis is performed, the produced tokens of the\r
+ field value analysis will be marked as "matched" for every\r
+ token that is produces by the query analysis\r
+ -->\r
+ <requestHandler name="/analysis/field" \r
+ startup="lazy"\r
+ class="solr.FieldAnalysisRequestHandler" />\r
+\r
+\r
+ <!-- Document Analysis Handler\r
+\r
+ http://wiki.apache.org/solr/AnalysisRequestHandler\r
+\r
+ An analysis handler that provides a breakdown of the analysis\r
+ process of provided documents. This handler expects a (single)\r
+ content stream with the following format:\r
+\r
+ <docs>\r
+ <doc>\r
+ <field name="id">1</field>\r
+ <field name="name">The Name</field>\r
+ <field name="text">The Text Value</field>\r
+ </doc>\r
+ <doc>...</doc>\r
+ <doc>...</doc>\r
+ ...\r
+ </docs>\r
+\r
+ Note: Each document must contain a field which serves as the\r
+ unique key. This key is used in the returned response to associate\r
+ an analysis breakdown to the analyzed document.\r
+\r
+ Like the FieldAnalysisRequestHandler, this handler also supports\r
+ query analysis by sending either an "analysis.query" or "q"\r
+ request parameter that holds the query text to be analyzed. It\r
+ also supports the "analysis.showmatch" parameter which when set to\r
+ true, all field tokens that match the query tokens will be marked\r
+ as a "match". \r
+ -->\r
+ <requestHandler name="/analysis/document" \r
+ class="solr.DocumentAnalysisRequestHandler" \r
+ startup="lazy" />\r
+\r
+ <!-- Admin Handlers\r
+\r
+ Admin Handlers - This will register all the standard admin\r
+ RequestHandlers. \r
+ -->\r
+ <requestHandler name="/admin/" \r
+ class="solr.admin.AdminHandlers" />\r
+ <!-- This single handler is equivalent to the following... -->\r
+ <!--\r
+ <requestHandler name="/admin/luke" class="solr.admin.LukeRequestHandler" />\r
+ <requestHandler name="/admin/system" class="solr.admin.SystemInfoHandler" />\r
+ <requestHandler name="/admin/plugins" class="solr.admin.PluginInfoHandler" />\r
+ <requestHandler name="/admin/threads" class="solr.admin.ThreadDumpHandler" />\r
+ <requestHandler name="/admin/properties" class="solr.admin.PropertiesRequestHandler" />\r
+ <requestHandler name="/admin/file" class="solr.admin.ShowFileRequestHandler" >\r
+ -->\r
+ <!-- If you wish to hide files under ${solr.home}/conf, explicitly\r
+ register the ShowFileRequestHandler using: \r
+ -->\r
+ <!--\r
+ <requestHandler name="/admin/file" \r
+ class="solr.admin.ShowFileRequestHandler" >\r
+ <lst name="invariants">\r
+ <str name="hidden">synonyms.txt</str> \r
+ <str name="hidden">anotherfile.txt</str> \r
+ </lst>\r
+ </requestHandler>\r
+ -->\r
+\r
+ <!-- ping/healthcheck -->\r
+ <requestHandler name="/admin/ping" class="solr.PingRequestHandler">\r
+ <lst name="invariants">\r
+ <str name="q">solrpingquery</str>\r
+ </lst>\r
+ <lst name="defaults">\r
+ <str name="echoParams">all</str>\r
+ </lst>\r
+ <!-- An optional feature of the PingRequestHandler is to configure the \r
+ handler with a "healthcheckFile" which can be used to enable/disable \r
+ the PingRequestHandler.\r
+ relative paths are resolved against the data dir \r
+ -->\r
+ <!-- <str name="healthcheckFile">server-enabled.txt</str> -->\r
+ </requestHandler>\r
+\r
+ <!-- Echo the request contents back to the client -->\r
+ <requestHandler name="/debug/dump" class="solr.DumpRequestHandler" >\r
+ <lst name="defaults">\r
+ <str name="echoParams">explicit</str> \r
+ <str name="echoHandler">true</str>\r
+ </lst>\r
+ </requestHandler>\r
+ \r
+ <!-- Solr Replication\r
+\r
+ The SolrReplicationHandler supports replicating indexes from a\r
+ "master" used for indexing and "slaves" used for queries.\r
+\r
+ http://wiki.apache.org/solr/SolrReplication \r
+\r
+ It is also necessary for SolrCloud to function (in Cloud mode, the\r
+ replication handler is used to bulk transfer segments when nodes \r
+ are added or need to recover).\r
+\r
+ https://wiki.apache.org/solr/SolrCloud/\r
+ -->\r
+ <requestHandler name="/replication" class="solr.ReplicationHandler" > \r
+ <!--\r
+ To enable simple master/slave replication, uncomment one of the \r
+ sections below, depending on whether this solr instance should be\r
+ the "master" or a "slave". If this instance is a "slave" you will \r
+ also need to fill in the masterUrl to point to a real machine.\r
+ -->\r
+ <!--\r
+ <lst name="master">\r
+ <str name="replicateAfter">commit</str>\r
+ <str name="replicateAfter">startup</str>\r
+ <str name="confFiles">schema.xml,stopwords.txt</str>\r
+ </lst>\r
+ -->\r
+ <!--\r
+ <lst name="slave">\r
+ <str name="masterUrl">http://your-master-hostname:8983/solr</str>\r
+ <str name="pollInterval">00:00:60</str>\r
+ </lst>\r
+ -->\r
+ </requestHandler>\r
+\r
+ <!-- Search Components\r
+\r
+ Search components are registered to SolrCore and used by \r
+ instances of SearchHandler (which can access them by name)\r
+ \r
+ By default, the following components are available:\r
+ \r
+ <searchComponent name="query" class="solr.QueryComponent" />\r
+ <searchComponent name="facet" class="solr.FacetComponent" />\r
+ <searchComponent name="mlt" class="solr.MoreLikeThisComponent" />\r
+ <searchComponent name="highlight" class="solr.HighlightComponent" />\r
+ <searchComponent name="stats" class="solr.StatsComponent" />\r
+ <searchComponent name="debug" class="solr.DebugComponent" />\r
+ \r
+ Default configuration in a requestHandler would look like:\r
+\r
+ <arr name="components">\r
+ <str>query</str>\r
+ <str>facet</str>\r
+ <str>mlt</str>\r
+ <str>highlight</str>\r
+ <str>stats</str>\r
+ <str>debug</str>\r
+ </arr>\r
+\r
+ If you register a searchComponent to one of the standard names, \r
+ that will be used instead of the default.\r
+\r
+ To insert components before or after the 'standard' components, use:\r
+ \r
+ <arr name="first-components">\r
+ <str>myFirstComponentName</str>\r
+ </arr>\r
+ \r
+ <arr name="last-components">\r
+ <str>myLastComponentName</str>\r
+ </arr>\r
+\r
+ NOTE: The component registered with the name "debug" will\r
+ always be executed after the "last-components" \r
+ \r
+ -->\r
+ <!-- Spell Check\r
+\r
+ The spell check component can return a list of alternative spelling\r
+ suggestions. \r
+\r
+ http://wiki.apache.org/solr/SpellCheckComponent\r
+ -->\r
+ <searchComponent name="spellcheck" class="solr.SpellCheckComponent">\r
+\r
+ <str name="queryAnalyzerFieldType">textSpell</str>\r
+\r
+ <!-- Multiple "Spell Checkers" can be declared and used by this\r
+ component\r
+ -->\r
+\r
+ <!-- a spellchecker built from a field of the main index -->\r
+ <lst name="spellchecker">\r
+ <str name="name">default</str>\r
+ <str name="field">name</str>\r
+ <str name="classname">solr.DirectSolrSpellChecker</str>\r
+ <!-- the spellcheck distance measure used, the default is the internal levenshtein -->\r
+ <str name="distanceMeasure">internal</str>\r
+ <!-- minimum accuracy needed to be considered a valid spellcheck suggestion -->\r
+ <float name="accuracy">0.5</float>\r
+ <!-- the maximum #edits we consider when enumerating terms: can be 1 or 2 -->\r
+ <int name="maxEdits">2</int>\r
+ <!-- the minimum shared prefix when enumerating terms -->\r
+ <int name="minPrefix">1</int>\r
+ <!-- maximum number of inspections per result. -->\r
+ <int name="maxInspections">5</int>\r
+ <!-- minimum length of a query term to be considered for correction -->\r
+ <int name="minQueryLength">4</int>\r
+ <!-- maximum threshold of documents a query term can appear to be considered for correction -->\r
+ <float name="maxQueryFrequency">0.01</float>\r
+ <!-- uncomment this to require suggestions to occur in 1% of the documents\r
+ <float name="thresholdTokenFrequency">.01</float>\r
+ -->\r
+ </lst>\r
+ \r
+ <!-- a spellchecker that can break or combine words. See "/spell" handler below for usage -->\r
+ <lst name="spellchecker">\r
+ <str name="name">wordbreak</str>\r
+ <str name="classname">solr.WordBreakSolrSpellChecker</str> \r
+ <str name="field">name</str>\r
+ <str name="combineWords">true</str>\r
+ <str name="breakWords">true</str>\r
+ <int name="maxChanges">10</int>\r
+ </lst>\r
+\r
+ <!-- a spellchecker that uses a different distance measure -->\r
+ <!--\r
+ <lst name="spellchecker">\r
+ <str name="name">jarowinkler</str>\r
+ <str name="field">spell</str>\r
+ <str name="classname">solr.DirectSolrSpellChecker</str>\r
+ <str name="distanceMeasure">\r
+ org.apache.lucene.search.spell.JaroWinklerDistance\r
+ </str>\r
+ </lst>\r
+ -->\r
+\r
+ <!-- a spellchecker that use an alternate comparator \r
+\r
+ comparatorClass be one of:\r
+ 1. score (default)\r
+ 2. freq (Frequency first, then score)\r
+ 3. A fully qualified class name\r
+ -->\r
+ <!--\r
+ <lst name="spellchecker">\r
+ <str name="name">freq</str>\r
+ <str name="field">lowerfilt</str>\r
+ <str name="classname">solr.DirectSolrSpellChecker</str>\r
+ <str name="comparatorClass">freq</str>\r
+ -->\r
+\r
+ <!-- A spellchecker that reads the list of words from a file -->\r
+ <!--\r
+ <lst name="spellchecker">\r
+ <str name="classname">solr.FileBasedSpellChecker</str>\r
+ <str name="name">file</str>\r
+ <str name="sourceLocation">spellings.txt</str>\r
+ <str name="characterEncoding">UTF-8</str>\r
+ <str name="spellcheckIndexDir">spellcheckerFile</str>\r
+ </lst>\r
+ -->\r
+ </searchComponent>\r
+\r
+ <!-- A request handler for demonstrating the spellcheck component. \r
+\r
+ NOTE: This is purely as an example. The whole purpose of the\r
+ SpellCheckComponent is to hook it into the request handler that\r
+ handles your normal user queries so that a separate request is\r
+ not needed to get suggestions.\r
+\r
+ IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW IS\r
+ NOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!\r
+ \r
+ See http://wiki.apache.org/solr/SpellCheckComponent for details\r
+ on the request parameters.\r
+ -->\r
+ <requestHandler name="/spell" class="solr.SearchHandler" startup="lazy">\r
+ <lst name="defaults">\r
+ <str name="df">text</str>\r
+ <!-- Solr will use suggestions from both the 'default' spellchecker\r
+ and from the 'wordbreak' spellchecker and combine them.\r
+ collations (re-written queries) can include a combination of\r
+ corrections from both spellcheckers -->\r
+ <str name="spellcheck.dictionary">default</str>\r
+ <str name="spellcheck.dictionary">wordbreak</str>\r
+ <str name="spellcheck">on</str>\r
+ <str name="spellcheck.extendedResults">true</str> \r
+ <str name="spellcheck.count">10</str>\r
+ <str name="spellcheck.alternativeTermCount">5</str>\r
+ <str name="spellcheck.maxResultsForSuggest">5</str> \r
+ <str name="spellcheck.collate">true</str>\r
+ <str name="spellcheck.collateExtendedResults">true</str> \r
+ <str name="spellcheck.maxCollationTries">10</str>\r
+ <str name="spellcheck.maxCollations">5</str> \r
+ </lst>\r
+ <arr name="last-components">\r
+ <str>spellcheck</str>\r
+ </arr>\r
+ </requestHandler>\r
+\r
+ <!-- Term Vector Component\r
+\r
+ http://wiki.apache.org/solr/TermVectorComponent\r
+ -->\r
+ <searchComponent name="tvComponent" class="solr.TermVectorComponent"/>\r
+\r
+ <!-- A request handler for demonstrating the term vector component\r
+\r
+ This is purely as an example.\r
+\r
+ In reality you will likely want to add the component to your \r
+ already specified request handlers. \r
+ -->\r
+ <requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy">\r
+ <lst name="defaults">\r
+ <str name="df">text</str>\r
+ <bool name="tv">true</bool>\r
+ </lst>\r
+ <arr name="last-components">\r
+ <str>tvComponent</str>\r
+ </arr>\r
+ </requestHandler>\r
+\r
+ <!-- Clustering Component\r
+\r
+ http://wiki.apache.org/solr/ClusteringComponent\r
+\r
+ You'll need to set the solr.clustering.enabled system property\r
+ when running solr to run with clustering enabled:\r
+\r
+ java -Dsolr.clustering.enabled=true -jar start.jar\r
+\r
+ -->\r
+ <searchComponent name="clustering"\r
+ enable="${solr.clustering.enabled:false}"\r
+ class="solr.clustering.ClusteringComponent" >\r
+ <!-- Declare an engine -->\r
+ <lst name="engine">\r
+ <!-- The name, only one can be named "default" -->\r
+ <str name="name">default</str>\r
+\r
+ <!-- Class name of Carrot2 clustering algorithm.\r
+\r
+ Currently available algorithms are:\r
+ \r
+ * org.carrot2.clustering.lingo.LingoClusteringAlgorithm\r
+ * org.carrot2.clustering.stc.STCClusteringAlgorithm\r
+ * org.carrot2.clustering.kmeans.BisectingKMeansClusteringAlgorithm\r
+ \r
+ See http://project.carrot2.org/algorithms.html for the\r
+ algorithm's characteristics.\r
+ -->\r
+ <str name="carrot.algorithm">org.carrot2.clustering.lingo.LingoClusteringAlgorithm</str>\r
+\r
+ <!-- Overriding values for Carrot2 default algorithm attributes.\r
+\r
+ For a description of all available attributes, see:\r
+ http://download.carrot2.org/stable/manual/#chapter.components.\r
+ Use attribute key as name attribute of str elements\r
+ below. These can be further overridden for individual\r
+ requests by specifying attribute key as request parameter\r
+ name and attribute value as parameter value.\r
+ -->\r
+ <str name="LingoClusteringAlgorithm.desiredClusterCountBase">20</str>\r
+\r
+ <!-- Location of Carrot2 lexical resources.\r
+\r
+ A directory from which to load Carrot2-specific stop words\r
+ and stop labels. Absolute or relative to Solr config directory.\r
+ If a specific resource (e.g. stopwords.en) is present in the\r
+ specified dir, it will completely override the corresponding\r
+ default one that ships with Carrot2.\r
+\r
+ For an overview of Carrot2 lexical resources, see:\r
+ http://download.carrot2.org/head/manual/#chapter.lexical-resources\r
+ -->\r
+ <str name="carrot.lexicalResourcesDir">clustering/carrot2</str>\r
+\r
+ <!-- The language to assume for the documents.\r
+\r
+ For a list of allowed values, see:\r
+ http://download.carrot2.org/stable/manual/#section.attribute.lingo.MultilingualClustering.defaultLanguage\r
+ -->\r
+ <str name="MultilingualClustering.defaultLanguage">ENGLISH</str>\r
+ </lst>\r
+ <lst name="engine">\r
+ <str name="name">stc</str>\r
+ <str name="carrot.algorithm">org.carrot2.clustering.stc.STCClusteringAlgorithm</str>\r
+ </lst>\r
+ </searchComponent>\r
+\r
+ <!-- A request handler for demonstrating the clustering component\r
+\r
+ This is purely as an example.\r
+\r
+ In reality you will likely want to add the component to your \r
+ already specified request handlers. \r
+ -->\r
+ <requestHandler name="/clustering"\r
+ startup="lazy"\r
+ enable="${solr.clustering.enabled:false}"\r
+ class="solr.SearchHandler">\r
+ <lst name="defaults">\r
+ <bool name="clustering">true</bool>\r
+ <str name="clustering.engine">default</str>\r
+ <bool name="clustering.results">true</bool>\r
+ <!-- The title field -->\r
+ <str name="carrot.title">name</str>\r
+ <str name="carrot.url">id</str>\r
+ <!-- The field to cluster on -->\r
+ <str name="carrot.snippet">features</str>\r
+ <!-- produce summaries -->\r
+ <bool name="carrot.produceSummary">true</bool>\r
+ <!-- the maximum number of labels per cluster -->\r
+ <!--<int name="carrot.numDescriptions">5</int>-->\r
+ <!-- produce sub clusters -->\r
+ <bool name="carrot.outputSubClusters">false</bool>\r
+ \r
+ <str name="defType">edismax</str>\r
+ <str name="qf">\r
+ text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4\r
+ </str>\r
+ <str name="q.alt">*:*</str>\r
+ <str name="rows">10</str>\r
+ <str name="fl">*,score</str>\r
+ </lst> \r
+ <arr name="last-components">\r
+ <str>clustering</str>\r
+ </arr>\r
+ </requestHandler>\r
+ \r
+ <!-- Terms Component\r
+\r
+ http://wiki.apache.org/solr/TermsComponent\r
+\r
+ A component to return terms and document frequency of those\r
+ terms\r
+ -->\r
+ <searchComponent name="terms" class="solr.TermsComponent"/>\r
+\r
+ <!-- A request handler for demonstrating the terms component -->\r
+ <requestHandler name="/terms" class="solr.SearchHandler" startup="lazy">\r
+ <lst name="defaults">\r
+ <bool name="terms">true</bool>\r
+ <bool name="distrib">false</bool>\r
+ </lst> \r
+ <arr name="components">\r
+ <str>terms</str>\r
+ </arr>\r
+ </requestHandler>\r
+\r
+\r
+ <!-- Query Elevation Component\r
+\r
+ http://wiki.apache.org/solr/QueryElevationComponent\r
+\r
+ a search component that enables you to configure the top\r
+ results for a given query regardless of the normal lucene\r
+ scoring.\r
+ -->\r
+ <searchComponent name="elevator" class="solr.QueryElevationComponent" >\r
+ <!-- pick a fieldType to analyze queries -->\r
+ <str name="queryFieldType">string</str>\r
+ <str name="config-file">elevate.xml</str>\r
+ </searchComponent>\r
+\r
+ <!-- A request handler for demonstrating the elevator component -->\r
+ <requestHandler name="/elevate" class="solr.SearchHandler" startup="lazy">\r
+ <lst name="defaults">\r
+ <str name="echoParams">explicit</str>\r
+ <str name="df">text</str>\r
+ </lst>\r
+ <arr name="last-components">\r
+ <str>elevator</str>\r
+ </arr>\r
+ </requestHandler>\r
+\r
+ <!-- Highlighting Component\r
+\r
+ http://wiki.apache.org/solr/HighlightingParameters\r
+ -->\r
+ <searchComponent class="solr.HighlightComponent" name="highlight">\r
+ <highlighting>\r
+ <!-- Configure the standard fragmenter -->\r
+ <!-- This could most likely be commented out in the "default" case -->\r
+ <fragmenter name="gap" \r
+ default="true"\r
+ class="solr.highlight.GapFragmenter">\r
+ <lst name="defaults">\r
+ <int name="hl.fragsize">100</int>\r
+ </lst>\r
+ </fragmenter>\r
+\r
+ <!-- A regular-expression-based fragmenter \r
+ (for sentence extraction) \r
+ -->\r
+ <fragmenter name="regex" \r
+ class="solr.highlight.RegexFragmenter">\r
+ <lst name="defaults">\r
+ <!-- slightly smaller fragsizes work better because of slop -->\r
+ <int name="hl.fragsize">70</int>\r
+ <!-- allow 50% slop on fragment sizes -->\r
+ <float name="hl.regex.slop">0.5</float>\r
+ <!-- a basic sentence pattern -->\r
+ <str name="hl.regex.pattern">[-\w ,/\n\"']{20,200}</str>\r
+ </lst>\r
+ </fragmenter>\r
+\r
+ <!-- Configure the standard formatter -->\r
+ <formatter name="html" \r
+ default="true"\r
+ class="solr.highlight.HtmlFormatter">\r
+ <lst name="defaults">\r
+ <str name="hl.simple.pre"><![CDATA[<em>]]></str>\r
+ <str name="hl.simple.post"><![CDATA[</em>]]></str>\r
+ </lst>\r
+ </formatter>\r
+\r
+ <!-- Configure the standard encoder -->\r
+ <encoder name="html" \r
+ class="solr.highlight.HtmlEncoder" />\r
+\r
+ <!-- Configure the standard fragListBuilder -->\r
+ <fragListBuilder name="simple" \r
+ class="solr.highlight.SimpleFragListBuilder"/>\r
+ \r
+ <!-- Configure the single fragListBuilder -->\r
+ <fragListBuilder name="single" \r
+ class="solr.highlight.SingleFragListBuilder"/>\r
+ \r
+ <!-- Configure the weighted fragListBuilder -->\r
+ <fragListBuilder name="weighted" \r
+ default="true"\r
+ class="solr.highlight.WeightedFragListBuilder"/>\r
+ \r
+ <!-- default tag FragmentsBuilder -->\r
+ <fragmentsBuilder name="default" \r
+ default="true"\r
+ class="solr.highlight.ScoreOrderFragmentsBuilder">\r
+ <!-- \r
+ <lst name="defaults">\r
+ <str name="hl.multiValuedSeparatorChar">/</str>\r
+ </lst>\r
+ -->\r
+ </fragmentsBuilder>\r
+\r
+ <!-- multi-colored tag FragmentsBuilder -->\r
+ <fragmentsBuilder name="colored" \r
+ class="solr.highlight.ScoreOrderFragmentsBuilder">\r
+ <lst name="defaults">\r
+ <str name="hl.tag.pre"><![CDATA[\r
+ <b style="background:yellow">,<b style="background:lawgreen">,\r
+ <b style="background:aquamarine">,<b style="background:magenta">,\r
+ <b style="background:palegreen">,<b style="background:coral">,\r
+ <b style="background:wheat">,<b style="background:khaki">,\r
+ <b style="background:lime">,<b style="background:deepskyblue">]]></str>\r
+ <str name="hl.tag.post"><![CDATA[</b>]]></str>\r
+ </lst>\r
+ </fragmentsBuilder>\r
+ \r
+ <boundaryScanner name="default" \r
+ default="true"\r
+ class="solr.highlight.SimpleBoundaryScanner">\r
+ <lst name="defaults">\r
+ <str name="hl.bs.maxScan">10</str>\r
+ <str name="hl.bs.chars">.,!? 	 </str>\r
+ </lst>\r
+ </boundaryScanner>\r
+ \r
+ <boundaryScanner name="breakIterator" \r
+ class="solr.highlight.BreakIteratorBoundaryScanner">\r
+ <lst name="defaults">\r
+ <!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE -->\r
+ <str name="hl.bs.type">WORD</str>\r
+ <!-- language and country are used when constructing Locale object. -->\r
+ <!-- And the Locale object will be used when getting instance of BreakIterator -->\r
+ <str name="hl.bs.language">en</str>\r
+ <str name="hl.bs.country">US</str>\r
+ </lst>\r
+ </boundaryScanner>\r
+ </highlighting>\r
+ </searchComponent>\r
+\r
+ <!-- Update Processors\r
+\r
+ Chains of Update Processor Factories for dealing with Update\r
+ Requests can be declared, and then used by name in Update\r
+ Request Processors\r
+\r
+ http://wiki.apache.org/solr/UpdateRequestProcessor\r
+\r
+ --> \r
+ <!-- Deduplication\r
+\r
+ An example dedup update processor that creates the "id" field\r
+ on the fly based on the hash code of some other fields. This\r
+ example has overwriteDupes set to false since we are using the\r
+ id field as the signatureField and Solr will maintain\r
+ uniqueness based on that anyway. \r
+ \r
+ -->\r
+ <!-- \r
+ <updateRequestProcessorChain name="dedupe">\r
+ <processor class="solr.processor.SignatureUpdateProcessorFactory">\r
+ <bool name="enabled">true</bool>\r
+ <str name="signatureField">id</str>\r
+ <bool name="overwriteDupes">false</bool>\r
+ <str name="fields">name,features,cat</str>\r
+ <str name="signatureClass">solr.processor.Lookup3Signature</str>\r
+ </processor>\r
+ <processor class="solr.LogUpdateProcessorFactory" />\r
+ <processor class="solr.RunUpdateProcessorFactory" />\r
+ </updateRequestProcessorChain>\r
+ -->\r
+ <updateRequestProcessorChain name="uuid">\r
+ <processor class="solr.UUIDUpdateProcessorFactory">\r
+ <str name="fieldName">id</str>\r
+ </processor>\r
+ <processor class="solr.RunUpdateProcessorFactory" />\r
+ </updateRequestProcessorChain>\r
+ <!-- Language identification\r
+\r
+ This example update chain identifies the language of the incoming\r
+ documents using the langid contrib. The detected language is\r
+ written to field language_s. No field name mapping is done.\r
+ The fields used for detection are text, title, subject and description,\r
+ making this example suitable for detecting languages form full-text\r
+ rich documents injected via ExtractingRequestHandler.\r
+ See more about langId at http://wiki.apache.org/solr/LanguageDetection\r
+ -->\r
+ <!--\r
+ <updateRequestProcessorChain name="langid">\r
+ <processor class="org.apache.solr.update.processor.TikaLanguageIdentifierUpdateProcessorFactory">\r
+ <str name="langid.fl">text,title,subject,description</str>\r
+ <str name="langid.langField">language_s</str>\r
+ <str name="langid.fallback">en</str>\r
+ </processor>\r
+ <processor class="solr.LogUpdateProcessorFactory" />\r
+ <processor class="solr.RunUpdateProcessorFactory" />\r
+ </updateRequestProcessorChain>\r
+ -->\r
+\r
+ <!-- Script update processor\r
+\r
+ This example hooks in an update processor implemented using JavaScript.\r
+\r
+ See more about the script update processor at http://wiki.apache.org/solr/ScriptUpdateProcessor\r
+ -->\r
+ <!--\r
+ <updateRequestProcessorChain name="script">\r
+ <processor class="solr.StatelessScriptUpdateProcessorFactory">\r
+ <str name="script">update-script.js</str>\r
+ <lst name="params">\r
+ <str name="config_param">example config parameter</str>\r
+ </lst>\r
+ </processor>\r
+ <processor class="solr.RunUpdateProcessorFactory" />\r
+ </updateRequestProcessorChain>\r
+ -->\r
+ \r
+ <!-- Response Writers\r
+\r
+ http://wiki.apache.org/solr/QueryResponseWriter\r
+\r
+ Request responses will be written using the writer specified by\r
+ the 'wt' request parameter matching the name of a registered\r
+ writer.\r
+\r
+ The "default" writer is the default and will be used if 'wt' is\r
+ not specified in the request.\r
+ -->\r
+ <!-- The following response writers are implicitly configured unless\r
+ overridden...\r
+ -->\r
+ <!--\r
+ <queryResponseWriter name="xml" \r
+ default="true"\r
+ class="solr.XMLResponseWriter" />\r
+ <queryResponseWriter name="json" class="solr.JSONResponseWriter"/>\r
+ <queryResponseWriter name="python" class="solr.PythonResponseWriter"/>\r
+ <queryResponseWriter name="ruby" class="solr.RubyResponseWriter"/>\r
+ <queryResponseWriter name="php" class="solr.PHPResponseWriter"/>\r
+ <queryResponseWriter name="phps" class="solr.PHPSerializedResponseWriter"/>\r
+ <queryResponseWriter name="csv" class="solr.CSVResponseWriter"/>\r
+ -->\r
+\r
+ <queryResponseWriter name="json" class="solr.JSONResponseWriter">\r
+ <!-- For the purposes of the tutorial, JSON responses are written as\r
+ plain text so that they are easy to read in *any* browser.\r
+ If you expect a MIME type of "application/json" just remove this override.\r
+ -->\r
+ <str name="content-type">text/plain; charset=UTF-8</str>\r
+ </queryResponseWriter>\r
+ \r
+ <!--\r
+ Custom response writers can be declared as needed...\r
+ -->\r
+ <queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" startup="lazy"/>\r
+ \r
+\r
+ <!-- XSLT response writer transforms the XML output by any xslt file found\r
+ in Solr's conf/xslt directory. Changes to xslt files are checked for\r
+ every xsltCacheLifetimeSeconds. \r
+ -->\r
+ <queryResponseWriter name="xslt" class="solr.XSLTResponseWriter">\r
+ <int name="xsltCacheLifetimeSeconds">5</int>\r
+ </queryResponseWriter>\r
+\r
+ <!-- Query Parsers\r
+\r
+ http://wiki.apache.org/solr/SolrQuerySyntax\r
+\r
+ Multiple QParserPlugins can be registered by name, and then\r
+ used in either the "defType" param for the QueryComponent (used\r
+ by SearchHandler) or in LocalParams\r
+ -->\r
+ <!-- example of registering a query parser -->\r
+ <!--\r
+ <queryParser name="myparser" class="com.mycompany.MyQParserPlugin"/>\r
+ -->\r
+\r
+ <!-- Function Parsers\r
+\r
+ http://wiki.apache.org/solr/FunctionQuery\r
+\r
+ Multiple ValueSourceParsers can be registered by name, and then\r
+ used as function names when using the "func" QParser.\r
+ -->\r
+ <!-- example of registering a custom function parser -->\r
+ <!--\r
+ <valueSourceParser name="myfunc" \r
+ class="com.mycompany.MyValueSourceParser" />\r
+ -->\r
+ \r
+ \r
+ <!-- Document Transformers\r
+ http://wiki.apache.org/solr/DocTransformers\r
+ -->\r
+ <!--\r
+ Could be something like:\r
+ <transformer name="db" class="com.mycompany.LoadFromDatabaseTransformer" >\r
+ <int name="connection">jdbc://....</int>\r
+ </transformer>\r
+ \r
+ To add a constant value to all docs, use:\r
+ <transformer name="mytrans2" class="org.apache.solr.response.transform.ValueAugmenterFactory" >\r
+ <int name="value">5</int>\r
+ </transformer>\r
+ \r
+ If you want the user to still be able to change it with _value:something_ use this:\r
+ <transformer name="mytrans3" class="org.apache.solr.response.transform.ValueAugmenterFactory" >\r
+ <double name="defaultValue">5</double>\r
+ </transformer>\r
+\r
+ If you are using the QueryElevationComponent, you may wish to mark documents that get boosted. The\r
+ EditorialMarkerFactory will do exactly that:\r
+ <transformer name="qecBooster" class="org.apache.solr.response.transform.EditorialMarkerFactory" />\r
+ -->\r
+ \r
+\r
+ <!-- Legacy config for the admin interface -->\r
+ <admin>\r
+ <defaultQuery>*:*</defaultQuery>\r
+ </admin>\r
+\r
+</config>\r
OSDN Git Service
