· 5 years ago · Jul 09, 2020, 07:18 AM
1<?xml version="1.0" encoding="UTF-8" ?>
2<!--
3 Licensed to the Apache Software Foundation (ASF) under one or more
4 contributor license agreements. See the NOTICE file distributed with
5 this work for additional information regarding copyright ownership.
6 The ASF licenses this file to You under the Apache License, Version 2.0
7 (the "License"); you may not use this file except in compliance with
8 the License. You may obtain a copy of the License at
9
10 http://www.apache.org/licenses/LICENSE-2.0
11
12 Unless required by applicable law or agreed to in writing, software
13 distributed under the License is distributed on an "AS IS" BASIS,
14 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15 See the License for the specific language governing permissions and
16 limitations under the License.
17-->
18
19<!--
20 For more details about configurations options that may appear in
21 this file, see http://wiki.apache.org/solr/SolrConfigXml.
22-->
23<config name="drupal-4.3-solr-4.x" >
24 <!-- In all configuration below, a prefix of "solr." for class names
25 is an alias that causes solr to search appropriate packages,
26 including org.apache.solr.(search|update|request|core|analysis)
27
28 You may also specify a fully qualified Java classname if you
29 have your own custom plugins.
30 -->
31
32 <!-- Set this to 'false' if you want solr to continue working after
33 it has encountered an severe configuration error. In a
34 production environment, you may want solr to keep working even
35 if one handler is mis-configured.
36
37 You may also set this to false using by setting the system
38 property:
39
40 -Dsolr.abortOnConfigurationError=false
41 -->
42 <abortOnConfigurationError>${solr.abortOnConfigurationError:true}</abortOnConfigurationError>
43
44 <!-- Controls what version of Lucene various components of Solr
45 adhere to. Generally, you want to use the latest version to
46 get all bug fixes and improvements. It is highly recommended
47 that you fully re-index after changing this setting as it can
48 affect both how text is indexed and queried.
49 -->
50 <luceneMatchVersion>${solr.luceneMatchVersion:LUCENE_40}</luceneMatchVersion>
51
52 <!-- lib directives can be used to instruct Solr to load an Jars
53 identified and use them to resolve any "plugins" specified in
54 your solrconfig.xml or schema.xml (ie: Analyzers, Request
55 Handlers, etc...).
56
57 All directories and paths are resolved relative to the
58 instanceDir.
59
60 If a "./lib" directory exists in your instanceDir, all files
61 found in it are included as if you had used the following
62 syntax...
63
64 <lib dir="./lib" />
65 -->
66
67 <!-- A dir option by itself adds any files found in the directory to
68 the classpath, this is useful for including all jars in a
69 directory.
70 -->
71 <lib dir="/opt/solr/dist/" regex="solr-cell-\d.*\.jar" />
72 <lib dir="/opt/solr/contrib/extraction/lib" regex=".*\.jar" />
73
74 <!-- The velocity library has been known to crash Solr in some
75 instances when deployed as a war file to Tomcat. Therefore all
76 references have been removed from the default configuration.
77 @see http://drupal.org/node/1612556
78 -->
79 <!-- <lib dir="../../contrib/velocity/lib" /> -->
80
81 <!-- When a regex is specified in addition to a directory, only the
82 files in that directory which completely match the regex
83 (anchored on both ends) will be included.
84 -->
85 <!--<lib dir="../../dist/" regex="apache-solr-cell-\d.*\.jar" />-->
86 <!--<lib dir="../../dist/" regex="apache-solr-clustering-\d.*\.jar" />-->
87 <!--<lib dir="../../dist/" regex="apache-solr-dataimporthandler-\d.*\.jar" />-->
88 <!--<lib dir="../../dist/" regex="apache-solr-langid-\d.*\.jar" />-->
89 <!-- <lib dir="../../dist/" regex="apache-solr-velocity-\d.*\.jar" /> -->
90
91 <!-- If a dir option (with or without a regex) is used and nothing
92 is found that matches, it will be ignored
93 -->
94 <!--<lib dir="../../contrib/clustering/lib/" />-->
95 <!--<lib dir="/total/crap/dir/ignored" />-->
96
97 <!-- an exact path can be used to specify a specific file. This
98 will cause a serious error to be logged if it can't be loaded.
99 -->
100 <!--
101 <lib path="../a-jar-that-does-not-exist.jar" />
102 -->
103
104 <!-- Data Directory
105
106 Used to specify an alternate directory to hold all index data
107 other than the default ./data under the Solr home. If
108 replication is in use, this should match the replication
109 configuration.
110 -->
111 <dataDir>/var/solr/cores/igbxBuGfYy_anemo_eu/data</dataDir>
112
113
114 <!-- The DirectoryFactory to use for indexes.
115
116 solr.StandardDirectoryFactory, the default, is filesystem
117 based and tries to pick the best implementation for the current
118 JVM and platform. One can force a particular implementation
119 via solr.MMapDirectoryFactory, solr.NIOFSDirectoryFactory, or
120 solr.SimpleFSDirectoryFactory.
121
122 solr.RAMDirectoryFactory is memory based, not
123 persistent, and doesn't work with replication.
124 -->
125 <directoryFactory name="DirectoryFactory"
126 class="${solr.directoryFactory:solr.StandardDirectoryFactory}"/>
127
128 <!-- Index Defaults
129
130 Values here affect all index writers and act as a default
131 unless overridden.
132
133 WARNING: See also the <mainIndex> section below for parameters
134 that overfor Solr's main Lucene index.
135 -->
136 <indexConfig>
137
138 <useCompoundFile>false</useCompoundFile>
139
140 <mergeFactor>4</mergeFactor>
141 <!-- Sets the amount of RAM that may be used by Lucene indexing
142 for buffering added documents and deletions before they are
143 flushed to the Directory. -->
144 <ramBufferSizeMB>32</ramBufferSizeMB>
145 <!-- If both ramBufferSizeMB and maxBufferedDocs is set, then
146 Lucene will flush based on whichever limit is hit first.
147 -->
148 <!-- <maxBufferedDocs>1000</maxBufferedDocs> -->
149
150 <maxMergeDocs>2147483647</maxMergeDocs>
151 <maxFieldLength>100000</maxFieldLength>
152 <writeLockTimeout>1000</writeLockTimeout>
153
154 <!-- Expert: Merge Policy
155
156 The Merge Policy in Lucene controls how merging is handled by
157 Lucene. The default in Solr 3.3 is TieredMergePolicy.
158
159 The default in 2.3 was the LogByteSizeMergePolicy,
160 previous versions used LogDocMergePolicy.
161
162 LogByteSizeMergePolicy chooses segments to merge based on
163 their size. The Lucene 2.2 default, LogDocMergePolicy chose
164 when to merge based on number of documents
165
166 Other implementations of MergePolicy must have a no-argument
167 constructor
168 -->
169 <mergePolicy class="org.apache.lucene.index.LogByteSizeMergePolicy"/>
170
171 <!-- Expert: Merge Scheduler
172
173 The Merge Scheduler in Lucene controls how merges are
174 performed. The ConcurrentMergeScheduler (Lucene 2.3 default)
175 can perform merges in the background using separate threads.
176 The SerialMergeScheduler (Lucene 2.2 default) does not.
177 -->
178 <!--
179 <mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>
180 -->
181
182 <!-- LockFactory
183
184 This option specifies which Lucene LockFactory implementation
185 to use.
186
187 single = SingleInstanceLockFactory - suggested for a
188 read-only index or when there is no possibility of
189 another process trying to modify the index.
190 native = NativeFSLockFactory - uses OS native file locking.
191 Do not use when multiple solr webapps in the same
192 JVM are attempting to share a single index.
193 simple = SimpleFSLockFactory - uses a plain file for locking
194
195 (For backwards compatibility with Solr 1.2, 'simple' is the
196 default if not specified.)
197
198 More details on the nuances of each LockFactory...
199 http://wiki.apache.org/lucene-java/AvailableLockFactories
200 -->
201 <lockType>single</lockType>
202
203 <!-- Expert: Controls how often Lucene loads terms into memory
204 Default is 128 and is likely good for most everyone.
205 -->
206 <!-- <termIndexInterval>256</termIndexInterval> -->
207
208 <!-- Unlock On Startup
209
210 If true, unlock any held write or commit locks on startup.
211 This defeats the locking mechanism that allows multiple
212 processes to safely access a lucene index, and should be used
213 with care.
214
215 This is not needed if lock type is 'none' or 'single'
216 -->
217 <unlockOnStartup>false</unlockOnStartup>
218
219 <!-- If true, IndexReaders will be reopened (often more efficient)
220 instead of closed and then opened.
221 -->
222 <reopenReaders>true</reopenReaders>
223
224 <!-- Commit Deletion Policy
225
226 Custom deletion policies can specified here. The class must
227 implement org.apache.lucene.index.IndexDeletionPolicy.
228
229 http://lucene.apache.org/java/2_9_1/api/all/org/apache/lucene/index/IndexDeletionPolicy.html
230
231 The standard Solr IndexDeletionPolicy implementation supports
232 deleting index commit points on number of commits, age of
233 commit point and optimized status.
234
235 The latest commit point should always be preserved regardless
236 of the criteria.
237 -->
238 <deletionPolicy class="solr.SolrDeletionPolicy">
239 <!-- The number of commit points to be kept -->
240 <str name="maxCommitsToKeep">1</str>
241 <!-- The number of optimized commit points to be kept -->
242 <str name="maxOptimizedCommitsToKeep">0</str>
243 <!--
244 Delete all commit points once they have reached the given age.
245 Supports DateMathParser syntax e.g.
246 -->
247 <!--
248 <str name="maxCommitAge">30MINUTES</str>
249 <str name="maxCommitAge">1DAY</str>
250 -->
251 </deletionPolicy>
252
253 <!-- Lucene Infostream
254
255 To aid in advanced debugging, Lucene provides an "InfoStream"
256 of detailed information when indexing.
257
258 Setting The value to true will instruct the underlying Lucene
259 IndexWriter to write its debugging info the specified file
260 -->
261 <infoStream file="INFOSTREAM.txt">false</infoStream>
262
263 </indexConfig>
264
265 <!-- JMX
266
267 This example enables JMX if and only if an existing MBeanServer
268 is found, use this if you want to configure JMX through JVM
269 parameters. Remove this to disable exposing Solr configuration
270 and statistics to JMX.
271
272 For more details see http://wiki.apache.org/solr/SolrJmx
273 -->
274 <!-- <jmx /> -->
275 <!-- If you want to connect to a particular server, specify the
276 agentId
277 -->
278 <!-- <jmx agentId="myAgent" /> -->
279 <!-- If you want to start a new MBeanServer, specify the serviceUrl -->
280 <!-- <jmx serviceUrl="service:jmx:rmi:///jndi/rmi://localhost:9999/solr"/>
281 -->
282
283 <!-- The default high-performance update handler -->
284 <updateHandler class="solr.DirectUpdateHandler2">
285
286 <!-- AutoCommit
287
288 Perform a <commit/> automatically under certain conditions.
289 Instead of enabling autoCommit, consider using "commitWithin"
290 when adding documents.
291
292 http://wiki.apache.org/solr/UpdateXmlMessages
293
294 maxDocs - Maximum number of documents to add since the last
295 commit before automatically triggering a new commit.
296
297 maxTime - Maximum amount of time that is allowed to pass
298 since a document was added before automaticly
299 triggering a new commit.
300 -->
301 <autoCommit>
302 <maxDocs>${solr.autoCommit.MaxDocs:10000}</maxDocs>
303 <maxTime>${solr.autoCommit.MaxTime:120000}</maxTime>
304 </autoCommit>
305
306 <!-- softAutoCommit is like autoCommit except it causes a
307 'soft' commit which only ensures that changes are visible
308 but does not ensure that data is synced to disk. This is
309 faster and more near-realtime friendly than a hard commit.
310 -->
311 <autoSoftCommit>
312 <maxDocs>${solr.autoSoftCommit.MaxDocs:2000}</maxDocs>
313 <maxTime>${solr.autoSoftCommit.MaxTime:10000}</maxTime>
314 </autoSoftCommit>
315
316 <!-- Update Related Event Listeners
317
318 Various IndexWriter related events can trigger Listeners to
319 take actions.
320
321 postCommit - fired after every commit or optimize command
322 postOptimize - fired after every optimize command
323 -->
324 <!-- The RunExecutableListener executes an external command from a
325 hook such as postCommit or postOptimize.
326
327 exe - the name of the executable to run
328 dir - dir to use as the current working directory. (default=".")
329 wait - the calling thread waits until the executable returns.
330 (default="true")
331 args - the arguments to pass to the program. (default is none)
332 env - environment variables to set. (default is none)
333 -->
334 <!-- This example shows how RunExecutableListener could be used
335 with the script based replication...
336 http://wiki.apache.org/solr/CollectionDistribution
337 -->
338 <!--
339 <listener event="postCommit" class="solr.RunExecutableListener">
340 <str name="exe">solr/bin/snapshooter</str>
341 <str name="dir">.</str>
342 <bool name="wait">true</bool>
343 <arr name="args"> <str>arg1</str> <str>arg2</str> </arr>
344 <arr name="env"> <str>MYVAR=val1</str> </arr>
345 </listener>
346 -->
347 <!-- Enables a transaction log, currently used for real-time get.
348 "dir" - the target directory for transaction logs, defaults to the
349 solr data directory. -->
350 <updateLog>
351 <str name="dir">${solr.data.dir:}</str>
352 <!-- if you want to take control of the synchronization you may specify
353 the syncLevel as one of the following where ''flush'' is the default.
354 Fsync will reduce throughput.
355 <str name="syncLevel">flush|fsync|none</str>
356 -->
357 </updateLog>
358 </updateHandler>
359
360 <!-- IndexReaderFactory
361
362 Use the following format to specify a custom IndexReaderFactory,
363 which allows for alternate IndexReader implementations.
364
365 ** Experimental Feature **
366
367 Please note - Using a custom IndexReaderFactory may prevent
368 certain other features from working. The API to
369 IndexReaderFactory may change without warning or may even be
370 removed from future releases if the problems cannot be
371 resolved.
372
373
374 ** Features that may not work with custom IndexReaderFactory **
375
376 The ReplicationHandler assumes a disk-resident index. Using a
377 custom IndexReader implementation may cause incompatibility
378 with ReplicationHandler and may cause replication to not work
379 correctly. See SOLR-1366 for details.
380
381 -->
382 <!--
383 <indexReaderFactory name="IndexReaderFactory" class="package.class">
384 <str name="someArg">Some Value</str>
385 </indexReaderFactory >
386 -->
387 <!-- By explicitly declaring the Factory, the termIndexDivisor can
388 be specified.
389 -->
390 <!--
391 <indexReaderFactory name="IndexReaderFactory"
392 class="solr.StandardIndexReaderFactory">
393 <int name="setTermIndexDivisor">12</int>
394 </indexReaderFactory >
395 -->
396
397
398 <query>
399 <!-- Max Boolean Clauses
400
401 Maximum number of clauses in each BooleanQuery, an exception
402 is thrown if exceeded.
403
404 ** WARNING **
405
406 This option actually modifies a global Lucene property that
407 will affect all SolrCores. If multiple solrconfig.xml files
408 disagree on this property, the value at any given moment will
409 be based on the last SolrCore to be initialized.
410
411 -->
412 <maxBooleanClauses>1024</maxBooleanClauses>
413
414
415 <!-- Solr Internal Query Caches
416
417 There are two implementations of cache available for Solr,
418 LRUCache, based on a synchronized LinkedHashMap, and
419 FastLRUCache, based on a ConcurrentHashMap.
420
421 FastLRUCache has faster gets and slower puts in single
422 threaded operation and thus is generally faster than LRUCache
423 when the hit ratio of the cache is high (> 75%), and may be
424 faster under other scenarios on multi-cpu systems.
425 -->
426
427 <!-- Filter Cache
428
429 Cache used by SolrIndexSearcher for filters (DocSets),
430 unordered sets of *all* documents that match a query. When a
431 new searcher is opened, its caches may be prepopulated or
432 "autowarmed" using data from caches in the old searcher.
433 autowarmCount is the number of items to prepopulate. For
434 LRUCache, the autowarmed items will be the most recently
435 accessed items.
436
437 Parameters:
438 class - the SolrCache implementation LRUCache or
439 (LRUCache or FastLRUCache)
440 size - the maximum number of entries in the cache
441 initialSize - the initial capacity (number of entries) of
442 the cache. (see java.util.HashMap)
443 autowarmCount - the number of entries to prepopulate from
444 and old cache.
445 -->
446 <filterCache class="solr.FastLRUCache"
447 size="512"
448 initialSize="512"
449 autowarmCount="0"/>
450
451 <!-- Query Result Cache
452
453 Caches results of searches - ordered lists of document ids
454 (DocList) based on a query, a sort, and the range of documents requested.
455 -->
456 <queryResultCache class="solr.LRUCache"
457 size="512"
458 initialSize="512"
459 autowarmCount="32"/>
460
461 <!-- Document Cache
462
463 Caches Lucene Document objects (the stored fields for each
464 document). Since Lucene internal document ids are transient,
465 this cache will not be autowarmed.
466 -->
467 <documentCache class="solr.LRUCache"
468 size="512"
469 initialSize="512"
470 autowarmCount="0"/>
471
472 <!-- Field Value Cache
473
474 Cache used to hold field values that are quickly accessible
475 by document id. The fieldValueCache is created by default
476 even if not configured here.
477 -->
478 <!--
479 <fieldValueCache class="solr.FastLRUCache"
480 size="512"
481 autowarmCount="128"
482 showItems="32" />
483 -->
484
485 <!-- Custom Cache
486
487 Example of a generic cache. These caches may be accessed by
488 name through SolrIndexSearcher.getCache(),cacheLookup(), and
489 cacheInsert(). The purpose is to enable easy caching of
490 user/application level data. The regenerator argument should
491 be specified as an implementation of solr.CacheRegenerator
492 if autowarming is desired.
493 -->
494 <!--
495 <cache name="myUserCache"
496 class="solr.LRUCache"
497 size="4096"
498 initialSize="1024"
499 autowarmCount="1024"
500 regenerator="com.mycompany.MyRegenerator"
501 />
502 -->
503
504
505 <!-- Lazy Field Loading
506
507 If true, stored fields that are not requested will be loaded
508 lazily. This can result in a significant speed improvement
509 if the usual case is to not load all stored fields,
510 especially if the skipped fields are large compressed text
511 fields.
512 -->
513 <enableLazyFieldLoading>true</enableLazyFieldLoading>
514
515 <!-- Use Filter For Sorted Query
516
517 A possible optimization that attempts to use a filter to
518 satisfy a search. If the requested sort does not include
519 score, then the filterCache will be checked for a filter
520 matching the query. If found, the filter will be used as the
521 source of document ids, and then the sort will be applied to
522 that.
523
524 For most situations, this will not be useful unless you
525 frequently get the same search repeatedly with different sort
526 options, and none of them ever use "score"
527 -->
528 <!--
529 <useFilterForSortedQuery>true</useFilterForSortedQuery>
530 -->
531
532 <!-- Result Window Size
533
534 An optimization for use with the queryResultCache. When a search
535 is requested, a superset of the requested number of document ids
536 are collected. For example, if a search for a particular query
537 requests matching documents 10 through 19, and queryWindowSize is 50,
538 then documents 0 through 49 will be collected and cached. Any further
539 requests in that range can be satisfied via the cache.
540 -->
541 <queryResultWindowSize>20</queryResultWindowSize>
542
543 <!-- Maximum number of documents to cache for any entry in the
544 queryResultCache.
545 -->
546 <queryResultMaxDocsCached>200</queryResultMaxDocsCached>
547
548 <!-- Query Related Event Listeners
549
550 Various IndexSearcher related events can trigger Listeners to
551 take actions.
552
553 newSearcher - fired whenever a new searcher is being prepared
554 and there is a current searcher handling requests (aka
555 registered). It can be used to prime certain caches to
556 prevent long request times for certain requests.
557
558 firstSearcher - fired whenever a new searcher is being
559 prepared but there is no current registered searcher to handle
560 requests or to gain autowarming data from.
561
562
563 -->
564 <!-- QuerySenderListener takes an array of NamedList and executes a
565 local query request for each NamedList in sequence.
566 -->
567 <listener event="newSearcher" class="solr.QuerySenderListener">
568 <arr name="queries">
569 <!--
570 <lst><str name="q">solr</str><str name="sort">price asc</str></lst>
571 <lst><str name="q">rocks</str><str name="sort">weight asc</str></lst>
572 -->
573 </arr>
574 </listener>
575 <listener event="firstSearcher" class="solr.QuerySenderListener">
576 <arr name="queries">
577 <lst>
578 <str name="q">solr rocks</str><str name="start">0</str><str name="rows">10</str>
579 </lst>
580 </arr>
581 </listener>
582
583 <!-- Use Cold Searcher
584
585 If a search request comes in and there is no current
586 registered searcher, then immediately register the still
587 warming searcher and use it. If "false" then all requests
588 will block until the first searcher is done warming.
589 -->
590 <useColdSearcher>false</useColdSearcher>
591
592 <!-- Max Warming Searchers
593
594 Maximum number of searchers that may be warming in the
595 background concurrently. An error is returned if this limit
596 is exceeded.
597
598 Recommend values of 1-2 for read-only slaves, higher for
599 masters w/o cache warming.
600 -->
601 <maxWarmingSearchers>2</maxWarmingSearchers>
602
603 </query>
604
605
606 <!-- Request Dispatcher
607
608 This section contains instructions for how the SolrDispatchFilter
609 should behave when processing requests for this SolrCore.
610
611 handleSelect affects the behavior of requests such as /select?qt=XXX
612
613 handleSelect="true" will cause the SolrDispatchFilter to process
614 the request and will result in consistent error handling and
615 formatting for all types of requests.
616
617 handleSelect="false" will cause the SolrDispatchFilter to
618 ignore "/select" requests and fallback to using the legacy
619 SolrServlet and it's Solr 1.1 style error formatting
620 -->
621 <requestDispatcher handleSelect="true" >
622 <!-- Request Parsing
623
624 These settings indicate how Solr Requests may be parsed, and
625 what restrictions may be placed on the ContentStreams from
626 those requests
627
628 enableRemoteStreaming - enables use of the stream.file
629 and stream.url parameters for specifying remote streams.
630
631 multipartUploadLimitInKB - specifies the max size of
632 Multipart File Uploads that Solr will allow in a Request.
633
634 *** WARNING ***
635 The settings below authorize Solr to fetch remote files, You
636 should make sure your system has some authentication before
637 using enableRemoteStreaming="true"
638
639 -->
640 <requestParsers enableRemoteStreaming="true"
641 multipartUploadLimitInKB="2048000" />
642
643 <!-- HTTP Caching
644
645 Set HTTP caching related parameters (for proxy caches and clients).
646
647 The options below instruct Solr not to output any HTTP Caching
648 related headers
649 -->
650 <httpCaching never304="true" />
651 <!-- If you include a <cacheControl> directive, it will be used to
652 generate a Cache-Control header (as well as an Expires header
653 if the value contains "max-age=")
654
655 By default, no Cache-Control header is generated.
656
657 You can use the <cacheControl> option even if you have set
658 never304="true"
659 -->
660 <!--
661 <httpCaching never304="true" >
662 <cacheControl>max-age=30, public</cacheControl>
663 </httpCaching>
664 -->
665 <!-- To enable Solr to respond with automatically generated HTTP
666 Caching headers, and to response to Cache Validation requests
667 correctly, set the value of never304="false"
668
669 This will cause Solr to generate Last-Modified and ETag
670 headers based on the properties of the Index.
671
672 The following options can also be specified to affect the
673 values of these headers...
674
675 lastModFrom - the default value is "openTime" which means the
676 Last-Modified value (and validation against If-Modified-Since
677 requests) will all be relative to when the current Searcher
678 was opened. You can change it to lastModFrom="dirLastMod" if
679 you want the value to exactly correspond to when the physical
680 index was last modified.
681
682 etagSeed="..." is an option you can change to force the ETag
683 header (and validation against If-None-Match requests) to be
684 different even if the index has not changed (ie: when making
685 significant changes to your config file)
686
687 (lastModifiedFrom and etagSeed are both ignored if you use
688 the never304="true" option)
689 -->
690 <!--
691 <httpCaching lastModifiedFrom="openTime"
692 etagSeed="Solr">
693 <cacheControl>max-age=30, public</cacheControl>
694 </httpCaching>
695 -->
696 </requestDispatcher>
697
698 <!-- Request Handlers
699
700 http://wiki.apache.org/solr/SolrRequestHandler
701
702 incoming queries will be dispatched to the correct handler
703 based on the path or the qt (query type) param.
704
705 Names starting with a '/' are accessed with the a path equal to
706 the registered name. Names without a leading '/' are accessed
707 with: http://host/app/[core/]select?qt=name
708
709 If a /select request is processed with out a qt param
710 specified, the requestHandler that declares default="true" will
711 be used.
712
713 If a Request Handler is declared with startup="lazy", then it will
714 not be initialized until the first request that uses it.
715
716 -->
717 <!-- SearchHandler
718
719 http://wiki.apache.org/solr/SearchHandler
720
721 For processing Search Queries, the primary Request Handler
722 provided with Solr is "SearchHandler" It delegates to a sequent
723 of SearchComponents (see below) and supports distributed
724 queries across multiple shards
725 -->
726 <!--<requestHandler name="search" class="solr.SearchHandler" default="true">-->
727 <!-- default values for query parameters can be specified, these
728 will be overridden by parameters in the request
729 -->
730 <!--<lst name="defaults">
731 <str name="echoParams">explicit</str>
732 <int name="rows">10</int>
733 </lst>-->
734 <!-- In addition to defaults, "appends" params can be specified
735 to identify values which should be appended to the list of
736 multi-val params from the query (or the existing "defaults").
737 -->
738 <!-- In this example, the param "fq=instock:true" would be appended to
739 any query time fq params the user may specify, as a mechanism for
740 partitioning the index, independent of any user selected filtering
741 that may also be desired (perhaps as a result of faceted searching).
742
743 NOTE: there is *absolutely* nothing a client can do to prevent these
744 "appends" values from being used, so don't use this mechanism
745 unless you are sure you always want it.
746 -->
747 <!--
748 <lst name="appends">
749 <str name="fq">inStock:true</str>
750 </lst>
751 -->
752 <!-- "invariants" are a way of letting the Solr maintainer lock down
753 the options available to Solr clients. Any params values
754 specified here are used regardless of what values may be specified
755 in either the query, the "defaults", or the "appends" params.
756
757 In this example, the facet.field and facet.query params would
758 be fixed, limiting the facets clients can use. Faceting is
759 not turned on by default - but if the client does specify
760 facet=true in the request, these are the only facets they
761 will be able to see counts for; regardless of what other
762 facet.field or facet.query params they may specify.
763
764 NOTE: there is *absolutely* nothing a client can do to prevent these
765 "invariants" values from being used, so don't use this mechanism
766 unless you are sure you always want it.
767 -->
768 <!--
769 <lst name="invariants">
770 <str name="facet.field">cat</str>
771 <str name="facet.field">manu_exact</str>
772 <str name="facet.query">price:[* TO 500]</str>
773 <str name="facet.query">price:[500 TO *]</str>
774 </lst>
775 -->
776 <!-- If the default list of SearchComponents is not desired, that
777 list can either be overridden completely, or components can be
778 prepended or appended to the default list. (see below)
779 -->
780 <!--
781 <arr name="components">
782 <str>nameOfCustomComponent1</str>
783 <str>nameOfCustomComponent2</str>
784 </arr>
785 -->
786 <!--</requestHandler>-->
787
788 <!-- A Robust Example
789
790 This example SearchHandler declaration shows off usage of the
791 SearchHandler with many defaults declared
792
793 Note that multiple instances of the same Request Handler
794 (SearchHandler) can be registered multiple times with different
795 names (and different init parameters)
796 -->
797 <!--
798 <requestHandler name="/browse" class="solr.SearchHandler">
799 <lst name="defaults">
800 <str name="echoParams">explicit</str>-->
801
802 <!-- VelocityResponseWriter settings -->
803 <!--<str name="wt">velocity</str>
804
805 <str name="v.template">browse</str>
806 <str name="v.layout">layout</str>
807 <str name="title">Solritas</str>
808
809 <str name="defType">edismax</str>
810 <str name="q.alt">*:*</str>
811 <str name="rows">10</str>
812 <str name="fl">*,score</str>
813 <str name="mlt.qf">
814 text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
815 </str>
816 <str name="mlt.fl">text,features,name,sku,id,manu,cat</str>
817 <int name="mlt.count">3</int>
818
819 <str name="qf">
820 text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
821 </str>
822
823 <str name="facet">on</str>
824 <str name="facet.field">cat</str>
825 <str name="facet.field">manu_exact</str>
826 <str name="facet.query">ipod</str>
827 <str name="facet.query">GB</str>
828 <str name="facet.mincount">1</str>
829 <str name="facet.pivot">cat,inStock</str>
830 <str name="facet.range.other">after</str>
831 <str name="facet.range">price</str>
832 <int name="f.price.facet.range.start">0</int>
833 <int name="f.price.facet.range.end">600</int>
834 <int name="f.price.facet.range.gap">50</int>
835 <str name="facet.range">popularity</str>
836 <int name="f.popularity.facet.range.start">0</int>
837 <int name="f.popularity.facet.range.end">10</int>
838 <int name="f.popularity.facet.range.gap">3</int>
839 <str name="facet.range">manufacturedate_dt</str>
840 <str name="f.manufacturedate_dt.facet.range.start">NOW/YEAR-10YEARS</str>
841 <str name="f.manufacturedate_dt.facet.range.end">NOW</str>
842 <str name="f.manufacturedate_dt.facet.range.gap">+1YEAR</str>
843 <str name="f.manufacturedate_dt.facet.range.other">before</str>
844 <str name="f.manufacturedate_dt.facet.range.other">after</str>-->
845
846
847 <!-- Highlighting defaults -->
848 <!--<str name="hl">on</str>
849 <str name="hl.fl">text features name</str>
850 <str name="f.name.hl.fragsize">0</str>
851 <str name="f.name.hl.alternateField">name</str>
852 </lst>
853 <arr name="last-components">
854 <str>spellcheck</str>
855 </arr>-->
856 <!--
857 <str name="url-scheme">httpx</str>
858 -->
859 <!--</requestHandler>-->
860 <!-- trivia: the name pinkPony requestHandler was an agreement between the Search API and the
861 apachesolr maintainers. The decision was taken during the Drupalcon Munich codesprint.
862 -->
863 <requestHandler name="pinkPony" class="solr.SearchHandler" default="true">
864 <lst name="defaults">
865 <str name="defType">edismax</str>
866 <str name="echoParams">explicit</str>
867 <bool name="omitHeader">true</bool>
868 <float name="tie">0.01</float>
869 <!-- Don't abort searches for the pinkPony request handler (set in solrcore.properties) -->
870 <int name="timeAllowed">${solr.pinkPony.timeAllowed:-1}</int>
871 <str name="q.alt">*:*</str>
872
873 <!-- By default, don't spell check -->
874 <str name="spellcheck">false</str>
875 <!-- Defaults for the spell checker when used -->
876 <str name="spellcheck.onlyMorePopular">true</str>
877 <str name="spellcheck.extendedResults">false</str>
878 <!-- The number of suggestions to return -->
879 <str name="spellcheck.count">1</str>
880 </lst>
881 <arr name="last-components">
882 <str>spellcheck</str>
883 <str>elevator</str>
884 </arr>
885 </requestHandler>
886
887 <!-- The more like this handler offers many advantages over the standard handler,
888 when performing moreLikeThis requests.-->
889 <requestHandler name="mlt" class="solr.MoreLikeThisHandler">
890 <lst name="defaults">
891 <str name="mlt.mintf">1</str>
892 <str name="mlt.mindf">1</str>
893 <str name="mlt.minwl">3</str>
894 <str name="mlt.maxwl">15</str>
895 <str name="mlt.maxqt">20</str>
896 <str name="mlt.match.include">false</str>
897 <!-- Abort any searches longer than 2 seconds (set in solrcore.properties) -->
898 <int name="timeAllowed">${solr.mlt.timeAllowed:2000}</int>
899 </lst>
900 </requestHandler>
901
902 <!-- A minimal query type for doing luene queries -->
903 <requestHandler name="standard" class="solr.SearchHandler">
904 <lst name="defaults">
905 <str name="echoParams">explicit</str>
906 <bool name="omitHeader">true</bool>
907 </lst>
908 </requestHandler>
909
910 <!-- XML Update Request Handler.
911
912 http://wiki.apache.org/solr/UpdateXmlMessages
913
914 The canonical Request Handler for Modifying the Index through
915 commands specified using XML.
916
917 Note: Since solr1.1 requestHandlers requires a valid content
918 type header if posted in the body. For example, curl now
919 requires: -H 'Content-type:text/xml; charset=utf-8'
920 -->
921 <requestHandler name="/update"
922 class="solr.UpdateRequestHandler">
923 <!-- See below for information on defining
924 updateRequestProcessorChains that can be used by name
925 on each Update Request
926 -->
927 <!--
928 <lst name="defaults">
929 <str name="update.chain">dedupe</str>
930 </lst>
931 -->
932 </requestHandler>
933 <!-- Binary Update Request Handler
934 http://wiki.apache.org/solr/javabin
935 -->
936 <requestHandler name="/update/javabin"
937 class="solr.UpdateRequestHandler" />
938
939 <!-- CSV Update Request Handler
940 http://wiki.apache.org/solr/UpdateCSV
941 -->
942 <requestHandler name="/update/csv"
943 class="solr.CSVRequestHandler"
944 startup="lazy" />
945
946 <!-- JSON Update Request Handler
947 http://wiki.apache.org/solr/UpdateJSON
948 -->
949 <requestHandler name="/update/json"
950 class="solr.JsonUpdateRequestHandler"
951 startup="lazy" />
952
953 <!-- Solr Cell Update Request Handler
954
955 http://wiki.apache.org/solr/ExtractingRequestHandler
956
957 -->
958 <requestHandler name="/update/extract"
959 startup="lazy"
960 class="solr.extraction.ExtractingRequestHandler" >
961 <lst name="defaults">
962 <!-- All the main content goes into "text"... if you need to return
963 the extracted text or do highlighting, use a stored field. -->
964 <str name="fmap.content">text</str>
965 <str name="lowernames">true</str>
966 <str name="uprefix">ignored_</str>
967
968 <!-- capture link hrefs but ignore div attributes -->
969 <str name="captureAttr">true</str>
970 <str name="fmap.a">links</str>
971 <str name="fmap.div">ignored_</str>
972 </lst>
973 </requestHandler>
974
975 <!-- For Apache Solr and Search API Attachments modules -->
976 <requestHandler name="/extract/tika"
977 startup="lazy"
978 class="org.apache.solr.handler.extraction.ExtractingRequestHandler" >
979 <lst name="defaults">
980 </lst>
981 <!-- This path only extracts - never updates -->
982 <lst name="invariants">
983 <bool name="extractOnly">true</bool>
984 </lst>
985 </requestHandler>
986
987 <!-- XSLT Update Request Handler
988 Transforms incoming XML with stylesheet identified by tr=
989 -->
990 <requestHandler name="/update/xslt"
991 startup="lazy"
992 class="solr.XsltUpdateRequestHandler"/>
993
994 <!-- Field Analysis Request Handler
995
996 RequestHandler that provides much the same functionality as
997 analysis.jsp. Provides the ability to specify multiple field
998 types and field names in the same request and outputs
999 index-time and query-time analysis for each of them.
1000
1001 Request parameters are:
1002 analysis.fieldname - field name whose analyzers are to be used
1003
1004 analysis.fieldtype - field type whose analyzers are to be used
1005 analysis.fieldvalue - text for index-time analysis
1006 q (or analysis.q) - text for query time analysis
1007 analysis.showmatch (true|false) - When set to true and when
1008 query analysis is performed, the produced tokens of the
1009 field value analysis will be marked as "matched" for every
1010 token that is produces by the query analysis
1011 -->
1012 <requestHandler name="/analysis/field"
1013 startup="lazy"
1014 class="solr.FieldAnalysisRequestHandler" />
1015
1016
1017 <!-- Document Analysis Handler
1018
1019 http://wiki.apache.org/solr/AnalysisRequestHandler
1020
1021 An analysis handler that provides a breakdown of the analysis
1022 process of provided docuemnts. This handler expects a (single)
1023 content stream with the following format:
1024
1025 <docs>
1026 <doc>
1027 <field name="id">1</field>
1028 <field name="name">The Name</field>
1029 <field name="text">The Text Value</field>
1030 </doc>
1031 <doc>...</doc>
1032 <doc>...</doc>
1033 ...
1034 </docs>
1035
1036 Note: Each document must contain a field which serves as the
1037 unique key. This key is used in the returned response to associate
1038 an analysis breakdown to the analyzed document.
1039
1040 Like the FieldAnalysisRequestHandler, this handler also supports
1041 query analysis by sending either an "analysis.query" or "q"
1042 request parameter that holds the query text to be analyzed. It
1043 also supports the "analysis.showmatch" parameter which when set to
1044 true, all field tokens that match the query tokens will be marked
1045 as a "match".
1046 -->
1047 <requestHandler name="/analysis/document"
1048 class="solr.DocumentAnalysisRequestHandler"
1049 startup="lazy" />
1050
1051 <!-- Admin Handlers
1052
1053 Admin Handlers - This will register all the standard admin
1054 RequestHandlers.
1055 -->
1056 <requestHandler name="/admin/" class="solr.admin.AdminHandlers" />
1057 <!-- This single handler is equivalent to the following... -->
1058 <!--
1059 <requestHandler name="/admin/luke" class="solr.admin.LukeRequestHandler" />
1060 <requestHandler name="/admin/system" class="solr.admin.SystemInfoHandler" />
1061 <requestHandler name="/admin/plugins" class="solr.admin.PluginInfoHandler" />
1062 <requestHandler name="/admin/threads" class="solr.admin.ThreadDumpHandler" />
1063 <requestHandler name="/admin/properties" class="solr.admin.PropertiesRequestHandler" />
1064 <requestHandler name="/admin/file" class="solr.admin.ShowFileRequestHandler" >
1065 -->
1066 <!-- If you wish to hide files under ${solr.home}/conf, explicitly
1067 register the ShowFileRequestHandler using:
1068 -->
1069 <!--
1070 <requestHandler name="/admin/file"
1071 class="solr.admin.ShowFileRequestHandler" >
1072 <lst name="invariants">
1073 <str name="hidden">synonyms.txt</str>
1074 <str name="hidden">anotherfile.txt</str>
1075 </lst>
1076 </requestHandler>
1077 -->
1078
1079 <!-- ping/healthcheck -->
1080 <requestHandler name="/admin/ping" class="solr.PingRequestHandler">
1081 <lst name="invariants">
1082 <str name="qt">pinkPony</str>
1083 <str name="q">solrpingquery</str>
1084 <str name="omitHeader">false</str>
1085 </lst>
1086 <lst name="defaults">
1087 <str name="echoParams">all</str>
1088 </lst>
1089 <!-- An optional feature of the PingRequestHandler is to configure the
1090 handler with a "healthcheckFile" which can be used to enable/disable
1091 the PingRequestHandler.
1092 relative paths are resolved against the data dir
1093 -->
1094 <!-- <str name="healthcheckFile">server-enabled.txt</str> -->
1095 </requestHandler>
1096
1097 <!-- Echo the request contents back to the client -->
1098 <requestHandler name="/debug/dump" class="solr.DumpRequestHandler" >
1099 <lst name="defaults">
1100 <str name="echoParams">explicit</str>
1101 <str name="echoHandler">true</str>
1102 </lst>
1103 </requestHandler>
1104
1105 <!-- Solr Replication
1106
1107 The SolrReplicationHandler supports replicating indexes from a
1108 "master" used for indexing and "slaves" used for queries.
1109
1110 http://wiki.apache.org/solr/SolrReplication
1111
1112 In the example below, remove the <lst name="master"> section if
1113 this is just a slave and remove the <lst name="slave"> section
1114 if this is just a master.
1115 -->
1116 <requestHandler name="/replication" class="solr.ReplicationHandler" >
1117 <lst name="master">
1118 <str name="enable">${solr.replication.master:false}</str>
1119 <str name="replicateAfter">commit</str>
1120 <str name="replicateAfter">startup</str>
1121 <str name="confFiles">${solr.replication.confFiles:schema.xml,mapping-ISOLatin1Accent.txt,protwords.txt,stopwords.txt,synonyms.txt,elevate.xml}</str>
1122 </lst>
1123 <lst name="slave">
1124 <str name="enable">${solr.replication.slave:false}</str>
1125 <str name="masterUrl">${solr.replication.masterUrl:http://localhost:8983/solr}/replication</str>
1126 <str name="pollInterval">${solr.replication.pollInterval:00:00:60}</str>
1127 </lst>
1128 </requestHandler>
1129
1130 <!-- Realtime get handler, guaranteed to return the latest stored fields of
1131 any document, without the need to commit or open a new searcher. The
1132 current implementation relies on the updateLog feature being enabled.
1133 -->
1134 <requestHandler name="/get" class="solr.RealTimeGetHandler">
1135 <lst name="defaults">
1136 <str name="omitHeader">true</str>
1137 <str name="wt">json</str>
1138 <str name="indent">true</str>
1139 </lst>
1140 </requestHandler>
1141
1142 <!-- Search Components
1143
1144 Search components are registered to SolrCore and used by
1145 instances of SearchHandler (which can access them by name)
1146
1147 By default, the following components are available:
1148
1149 <searchComponent name="query" class="solr.QueryComponent" />
1150 <searchComponent name="facet" class="solr.FacetComponent" />
1151 <searchComponent name="mlt" class="solr.MoreLikeThisComponent" />
1152 <searchComponent name="highlight" class="solr.HighlightComponent" />
1153 <searchComponent name="stats" class="solr.StatsComponent" />
1154 <searchComponent name="debug" class="solr.DebugComponent" />
1155
1156 Default configuration in a requestHandler would look like:
1157
1158 <arr name="components">
1159 <str>query</str>
1160 <str>facet</str>
1161 <str>mlt</str>
1162 <str>highlight</str>
1163 <str>stats</str>
1164 <str>debug</str>
1165 </arr>
1166
1167 If you register a searchComponent to one of the standard names,
1168 that will be used instead of the default.
1169
1170 To insert components before or after the 'standard' components, use:
1171
1172 <arr name="first-components">
1173 <str>myFirstComponentName</str>
1174 </arr>
1175
1176 <arr name="last-components">
1177 <str>myLastComponentName</str>
1178 </arr>
1179
1180 NOTE: The component registered with the name "debug" will
1181 always be executed after the "last-components"
1182
1183 -->
1184
1185 <!-- A request handler for demonstrating the spellcheck component.
1186
1187 NOTE: This is purely as an example. The whole purpose of the
1188 SpellCheckComponent is to hook it into the request handler that
1189 handles your normal user queries so that a separate request is
1190 not needed to get suggestions.
1191
1192 IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW IS
1193 NOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!
1194
1195 See http://wiki.apache.org/solr/SpellCheckComponent for details
1196 on the request parameters.
1197 -->
1198 <requestHandler name="/spell" class="solr.SearchHandler" startup="lazy">
1199 <lst name="defaults">
1200 <str name="spellcheck.onlyMorePopular">false</str>
1201 <str name="spellcheck.extendedResults">false</str>
1202 <str name="spellcheck.count">1</str>
1203 </lst>
1204 <arr name="last-components">
1205 <str>spellcheck</str>
1206 </arr>
1207 </requestHandler>
1208
1209 <!-- Term Vector Component
1210
1211 http://wiki.apache.org/solr/TermVectorComponent
1212 -->
1213 <searchComponent name="tvComponent" class="solr.TermVectorComponent"/>
1214
1215 <!-- A request handler for demonstrating the term vector component
1216
1217 This is purely as an example.
1218
1219 In reality you will likely want to add the component to your
1220 already specified request handlers.
1221 -->
1222 <requestHandler name="tvrh" class="solr.SearchHandler" startup="lazy">
1223 <lst name="defaults">
1224 <bool name="tv">true</bool>
1225 </lst>
1226 <arr name="last-components">
1227 <str>tvComponent</str>
1228 </arr>
1229 </requestHandler>
1230
1231 <!-- Clustering Component
1232
1233 http://wiki.apache.org/solr/ClusteringComponent
1234
1235 This relies on third party jars which are notincluded in the
1236 release. To use this component (and the "/clustering" handler)
1237 Those jars will need to be downloaded, and you'll need to set
1238 the solr.cluster.enabled system property when running solr...
1239
1240 java -Dsolr.clustering.enabled=true -jar start.jar
1241 -->
1242 <!-- <searchComponent name="clustering"
1243 enable="${solr.clustering.enabled:false}"
1244 class="solr.clustering.ClusteringComponent" > -->
1245 <!-- Declare an engine -->
1246 <!--<lst name="engine">-->
1247 <!-- The name, only one can be named "default" -->
1248 <!--<str name="name">default</str>-->
1249
1250 <!-- Class name of Carrot2 clustering algorithm.
1251
1252 Currently available algorithms are:
1253
1254 * org.carrot2.clustering.lingo.LingoClusteringAlgorithm
1255 * org.carrot2.clustering.stc.STCClusteringAlgorithm
1256 * org.carrot2.clustering.kmeans.BisectingKMeansClusteringAlgorithm
1257
1258 See http://project.carrot2.org/algorithms.html for the
1259 algorithm's characteristics.
1260 -->
1261 <!--<str name="carrot.algorithm">org.carrot2.clustering.lingo.LingoClusteringAlgorithm</str>-->
1262
1263 <!-- Overriding values for Carrot2 default algorithm attributes.
1264
1265 For a description of all available attributes, see:
1266 http://download.carrot2.org/stable/manual/#chapter.components.
1267 Use attribute key as name attribute of str elements
1268 below. These can be further overridden for individual
1269 requests by specifying attribute key as request parameter
1270 name and attribute value as parameter value.
1271 -->
1272 <!--<str name="LingoClusteringAlgorithm.desiredClusterCountBase">20</str>-->
1273
1274 <!-- Location of Carrot2 lexical resources.
1275
1276 A directory from which to load Carrot2-specific stop words
1277 and stop labels. Absolute or relative to Solr config directory.
1278 If a specific resource (e.g. stopwords.en) is present in the
1279 specified dir, it will completely override the corresponding
1280 default one that ships with Carrot2.
1281
1282 For an overview of Carrot2 lexical resources, see:
1283 http://download.carrot2.org/head/manual/#chapter.lexical-resources
1284 -->
1285 <!--<str name="carrot.lexicalResourcesDir">clustering/carrot2</str>-->
1286
1287 <!-- The language to assume for the documents.
1288
1289 For a list of allowed values, see:
1290 http://download.carrot2.org/stable/manual/#section.attribute.lingo.MultilingualClustering.defaultLanguage
1291 -->
1292 <!--<str name="MultilingualClustering.defaultLanguage">ENGLISH</str>
1293 </lst>
1294 <lst name="engine">
1295 <str name="name">stc</str>
1296 <str name="carrot.algorithm">org.carrot2.clustering.stc.STCClusteringAlgorithm</str>
1297 </lst>
1298 </searchComponent>-->
1299
1300 <!-- A request handler for demonstrating the clustering component
1301
1302 This is purely as an example.
1303
1304 In reality you will likely want to add the component to your
1305 already specified request handlers.
1306 -->
1307 <!--<requestHandler name="/clustering"
1308 startup="lazy"
1309 enable="${solr.clustering.enabled:false}"
1310 class="solr.SearchHandler">
1311 <lst name="defaults">
1312 <bool name="clustering">true</bool>
1313 <str name="clustering.engine">default</str>
1314 <bool name="clustering.results">true</bool>-->
1315 <!-- The title field -->
1316 <!--<str name="carrot.title">name</str>-->
1317 <!--<str name="carrot.url">id</str>-->
1318 <!-- The field to cluster on -->
1319 <!--<str name="carrot.snippet">features</str>-->
1320 <!-- produce summaries -->
1321 <!--<bool name="carrot.produceSummary">true</bool>-->
1322 <!-- the maximum number of labels per cluster -->
1323 <!--<int name="carrot.numDescriptions">5</int>-->
1324 <!-- produce sub clusters -->
1325 <!--<bool name="carrot.outputSubClusters">false</bool>-->
1326
1327 <!--<str name="defType">edismax</str>
1328 <str name="qf">
1329 text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
1330 </str>
1331 <str name="q.alt">*:*</str>
1332 <str name="rows">10</str>
1333 <str name="fl">*,score</str>
1334 </lst>
1335 <arr name="last-components">
1336 <str>clustering</str>
1337 </arr>
1338 </requestHandler>-->
1339
1340 <!-- Terms Component
1341
1342 http://wiki.apache.org/solr/TermsComponent
1343
1344 A component to return terms and document frequency of those
1345 terms
1346 -->
1347 <searchComponent name="terms" class="solr.TermsComponent"/>
1348
1349 <!-- A request handler for demonstrating the terms component -->
1350 <requestHandler name="/terms" class="solr.SearchHandler" startup="lazy">
1351 <lst name="defaults">
1352 <bool name="terms">true</bool>
1353 </lst>
1354 <arr name="components">
1355 <str>terms</str>
1356 </arr>
1357 </requestHandler>
1358
1359
1360 <!-- Query Elevation Component
1361
1362 http://wiki.apache.org/solr/QueryElevationComponent
1363
1364 a search component that enables you to configure the top
1365 results for a given query regardless of the normal lucene
1366 scoring.
1367 -->
1368 <searchComponent name="elevator" class="solr.QueryElevationComponent" >
1369 <!-- pick a fieldType to analyze queries -->
1370 <str name="queryFieldType">string</str>
1371 <str name="config-file">elevate.xml</str>
1372 </searchComponent>
1373
1374 <!-- A request handler for demonstrating the elevator component -->
1375 <requestHandler name="/elevate" class="solr.SearchHandler" startup="lazy">
1376 <lst name="defaults">
1377 <str name="echoParams">explicit</str>
1378 </lst>
1379 <arr name="last-components">
1380 <str>elevator</str>
1381 </arr>
1382 </requestHandler>
1383
1384 <!-- Highlighting Component
1385
1386 http://wiki.apache.org/solr/HighlightingParameters
1387 -->
1388 <searchComponent class="solr.HighlightComponent" name="highlight">
1389 <highlighting>
1390 <!-- Configure the standard fragmenter -->
1391 <!-- This could most likely be commented out in the "default" case -->
1392 <fragmenter name="gap"
1393 default="true"
1394 class="solr.highlight.GapFragmenter">
1395 <lst name="defaults">
1396 <int name="hl.fragsize">100</int>
1397 </lst>
1398 </fragmenter>
1399
1400 <!-- A regular-expression-based fragmenter
1401 (for sentence extraction)
1402 -->
1403 <fragmenter name="regex"
1404 class="solr.highlight.RegexFragmenter">
1405 <lst name="defaults">
1406 <!-- slightly smaller fragsizes work better because of slop -->
1407 <int name="hl.fragsize">70</int>
1408 <!-- allow 50% slop on fragment sizes -->
1409 <float name="hl.regex.slop">0.5</float>
1410 <!-- a basic sentence pattern -->
1411 <str name="hl.regex.pattern">[-\w ,/\n\"']{20,200}</str>
1412 </lst>
1413 </fragmenter>
1414
1415 <!-- Configure the standard formatter -->
1416 <formatter name="html"
1417 default="true"
1418 class="solr.highlight.HtmlFormatter">
1419 <lst name="defaults">
1420 <str name="hl.simple.pre"><![CDATA[<strong>]]></str>
1421 <str name="hl.simple.post"><![CDATA[</strong>]]></str>
1422 </lst>
1423 </formatter>
1424
1425 <!-- Configure the standard encoder -->
1426 <encoder name="html"
1427 class="solr.highlight.HtmlEncoder" />
1428
1429 <!-- Configure the standard fragListBuilder -->
1430 <fragListBuilder name="simple"
1431 default="true"
1432 class="solr.highlight.SimpleFragListBuilder"/>
1433
1434 <!-- Configure the single fragListBuilder -->
1435 <fragListBuilder name="single"
1436 class="solr.highlight.SingleFragListBuilder"/>
1437
1438 <!-- default tag FragmentsBuilder -->
1439 <fragmentsBuilder name="default"
1440 default="true"
1441 class="solr.highlight.ScoreOrderFragmentsBuilder">
1442 <!--
1443 <lst name="defaults">
1444 <str name="hl.multiValuedSeparatorChar">/</str>
1445 </lst>
1446 -->
1447 </fragmentsBuilder>
1448
1449 <!-- multi-colored tag FragmentsBuilder -->
1450 <fragmentsBuilder name="colored"
1451 class="solr.highlight.ScoreOrderFragmentsBuilder">
1452 <lst name="defaults">
1453 <str name="hl.tag.pre"><![CDATA[
1454 <b style="background:yellow">,<b style="background:lawgreen">,
1455 <b style="background:aquamarine">,<b style="background:magenta">,
1456 <b style="background:palegreen">,<b style="background:coral">,
1457 <b style="background:wheat">,<b style="background:khaki">,
1458 <b style="background:lime">,<b style="background:deepskyblue">]]></str>
1459 <str name="hl.tag.post"><![CDATA[</b>]]></str>
1460 </lst>
1461 </fragmentsBuilder>
1462
1463 <boundaryScanner name="default"
1464 default="true"
1465 class="solr.highlight.SimpleBoundaryScanner">
1466 <lst name="defaults">
1467 <str name="hl.bs.maxScan">10</str>
1468 <str name="hl.bs.chars">.,!? 	 </str>
1469 </lst>
1470 </boundaryScanner>
1471
1472 <boundaryScanner name="breakIterator"
1473 class="solr.highlight.BreakIteratorBoundaryScanner">
1474 <lst name="defaults">
1475 <!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE -->
1476 <str name="hl.bs.type">WORD</str>
1477 <!-- language and country are used when constructing Locale object. -->
1478 <!-- And the Locale object will be used when getting instance of BreakIterator -->
1479 <str name="hl.bs.language">en</str>
1480 <str name="hl.bs.country">US</str>
1481 </lst>
1482 </boundaryScanner>
1483 </highlighting>
1484 </searchComponent>
1485
1486 <!-- Update Processors
1487
1488 Chains of Update Processor Factories for dealing with Update
1489 Requests can be declared, and then used by name in Update
1490 Request Processors
1491
1492 http://wiki.apache.org/solr/UpdateRequestProcessor
1493
1494 -->
1495 <!-- Deduplication
1496
1497 An example dedup update processor that creates the "id" field
1498 on the fly based on the hash code of some other fields. This
1499 example has overwriteDupes set to false since we are using the
1500 id field as the signatureField and Solr will maintain
1501 uniqueness based on that anyway.
1502
1503 -->
1504 <!--
1505 <updateRequestProcessorChain name="dedupe">
1506 <processor class="solr.processor.SignatureUpdateProcessorFactory">
1507 <bool name="enabled">true</bool>
1508 <str name="signatureField">id</str>
1509 <bool name="overwriteDupes">false</bool>
1510 <str name="fields">name,features,cat</str>
1511 <str name="signatureClass">solr.processor.Lookup3Signature</str>
1512 </processor>
1513 <processor class="solr.LogUpdateProcessorFactory" />
1514 <processor class="solr.RunUpdateProcessorFactory" />
1515 </updateRequestProcessorChain>
1516 -->
1517
1518 <!--
1519 This example update chain identifies the language of the incoming
1520 documents using the langid contrib. The detected language is
1521 written to field language_s. No field name mapping is done.
1522 The fields used for detection are text, title, subject and description,
1523 making this example suitable for detecting languages form full-text
1524 rich documents injected via ExtractingRequestHandler.
1525 See more about langId at http://wiki.apache.org/solr/LanguageDetection
1526 -->
1527 <!--
1528 <updateRequestProcessorChain name="langid">
1529 <processor class="org.apache.solr.update.processor.TikaLanguageIdentifierUpdateProcessorFactory">
1530 <str name="langid.fl">text,title,subject,description</str>
1531 <str name="langid.langField">language_s</str>
1532 <str name="langid.fallback">en</str>
1533 </processor>
1534 <processor class="solr.LogUpdateProcessorFactory" />
1535 <processor class="solr.RunUpdateProcessorFactory" />
1536 </updateRequestProcessorChain>
1537 -->
1538
1539 <!-- Response Writers
1540
1541 http://wiki.apache.org/solr/QueryResponseWriter
1542
1543 Request responses will be written using the writer specified by
1544 the 'wt' request parameter matching the name of a registered
1545 writer.
1546
1547 The "default" writer is the default and will be used if 'wt' is
1548 not specified in the request.
1549 -->
1550 <!-- The following response writers are implicitly configured unless
1551 overridden...
1552 -->
1553 <!--
1554 <queryResponseWriter name="xml"
1555 default="true"
1556 class="solr.XMLResponseWriter" />
1557 <queryResponseWriter name="json" class="solr.JSONResponseWriter"/>
1558 <queryResponseWriter name="python" class="solr.PythonResponseWriter"/>
1559 <queryResponseWriter name="ruby" class="solr.RubyResponseWriter"/>
1560 <queryResponseWriter name="php" class="solr.PHPResponseWriter"/>
1561 <queryResponseWriter name="phps" class="solr.PHPSerializedResponseWriter"/>
1562 <queryResponseWriter name="csv" class="solr.CSVResponseWriter"/>
1563 -->
1564
1565 <queryResponseWriter name="json" class="solr.JSONResponseWriter">
1566 <!-- For the purposes of the tutorial, JSON responses are written as
1567 plain text so that they are easy to read in *any* browser.
1568 If you expect a MIME type of "application/json" just remove this override.
1569 -->
1570 <str name="content-type">text/plain; charset=UTF-8</str>
1571 </queryResponseWriter>
1572
1573 <!--
1574 Custom response writers can be declared as needed...
1575 -->
1576 <!-- The solr.velocity.enabled flag is used by Solr's test cases so that this response writer is not
1577 loaded (causing an error if contrib/velocity has not been built fully) -->
1578 <!-- <queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" enable="${solr.velocity.enabled:true}"/> -->
1579
1580
1581 <!-- XSLT response writer transforms the XML output by any xslt file found
1582 in Solr's conf/xslt directory. Changes to xslt files are checked for
1583 every xsltCacheLifetimeSeconds.
1584 -->
1585 <queryResponseWriter name="xslt" class="solr.XSLTResponseWriter">
1586 <int name="xsltCacheLifetimeSeconds">5</int>
1587 </queryResponseWriter>
1588
1589 <!-- Query Parsers
1590
1591 http://wiki.apache.org/solr/SolrQuerySyntax
1592
1593 Multiple QParserPlugins can be registered by name, and then
1594 used in either the "defType" param for the QueryComponent (used
1595 by SearchHandler) or in LocalParams
1596 -->
1597 <!-- example of registering a query parser -->
1598 <!--
1599 <queryParser name="myparser" class="com.mycompany.MyQParserPlugin"/>
1600 -->
1601
1602 <!-- Function Parsers
1603
1604 http://wiki.apache.org/solr/FunctionQuery
1605
1606 Multiple ValueSourceParsers can be registered by name, and then
1607 used as function names when using the "func" QParser.
1608 -->
1609 <!-- example of registering a custom function parser -->
1610 <!--
1611 <valueSourceParser name="myfunc"
1612 class="com.mycompany.MyValueSourceParser" />
1613 -->
1614
1615 <!-- Legacy config for the admin interface -->
1616 <admin>
1617 <defaultQuery>*:*</defaultQuery>
1618
1619 <!-- configure a healthcheck file for servers behind a
1620 loadbalancer
1621 -->
1622 <!--
1623 <healthcheck type="file">server-enabled</healthcheck>
1624 -->
1625 </admin>
1626
1627 <!-- Following is a dynamic way to include other components or any customized solrconfig.xml stuff, added by other contrib modules -->
1628 <xi:include href="solrconfig_extra.xml" xmlns:xi="http://www.w3.org/2001/XInclude">
1629 <xi:fallback>
1630 <!-- Spell Check
1631
1632 The spell check component can return a list of alternative spelling
1633 suggestions. This component must be defined in
1634 solrconfig_extra.xml if present, since it's used in the search handler.
1635
1636 http://wiki.apache.org/solr/SpellCheckComponent
1637 -->
1638 <searchComponent name="spellcheck" class="solr.SpellCheckComponent">
1639
1640 <str name="queryAnalyzerFieldType">textSpell</str>
1641
1642 <!-- a spellchecker built from a field of the main index -->
1643 <lst name="spellchecker">
1644 <str name="name">default</str>
1645 <str name="field">spell</str>
1646 <str name="spellcheckIndexDir">spellchecker</str>
1647 <str name="buildOnOptimize">true</str>
1648 </lst>
1649 </searchComponent>
1650 </xi:fallback>
1651 </xi:include>
1652
1653</config>