wordpress 图片自动加/win10必做的优化

最新项目中有个需求，需要检索上传的word文档，并给出提示，本博客使用solr+tika完成，之前solr的搭建已经详细的写过，有不清楚的参考上篇博客solr5.5搭建,在上篇的基础上需要改动如下配置文件 修改solrconfig.xml

<?xml version="1.0" encoding="UTF-8" ?>
<!--Licensed to the Apache Software Foundation (ASF) under one or morecontributor license agreements.  See the NOTICE file distributed withthis work for additional information regarding copyright ownership.The ASF licenses this file to You under the Apache License, Version 2.0(the "License"); you may not use this file except in compliance withthe License.  You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.See the License for the specific language governing permissions andlimitations under the License.
--><!-- For more details about configurations options that may appear inthis file, see http://wiki.apache.org/solr/SolrConfigXml. 
-->
<config><!-- In all configuration below, a prefix of "solr." for class namesis an alias that causes solr to search appropriate packages,including org.apache.solr.(search|update|request|core|analysis)You may also specify a fully qualified Java classname if youhave your own custom plugins.--><!-- Controls what version of Lucene various components of Solradhere to.  Generally, you want to use the latest version toget all bug fixes and improvements. It is highly recommendedthat you fully re-index after changing this setting as it canaffect both how text is indexed and queried.--><luceneMatchVersion>5.5.0</luceneMatchVersion><!-- <lib/> directives can be used to instruct Solr to load any Jarsidentified and use them to resolve any "plugins" specified inyour solrconfig.xml or schema.xml (ie: Analyzers, RequestHandlers, etc...).All directories and paths are resolved relative to theinstanceDir.Please note that <lib/> directives are processed in the orderthat they appear in your solrconfig.xml file, and are "stacked" on top of each other when building a ClassLoader - so if you have plugin jars with dependencies on other jars, the "lower level" dependency jars should be loaded first.If a "./lib" directory exists in your instanceDir, all filesfound in it are included as if you had used the followingsyntax...<lib dir="./lib" />--><!-- A 'dir' option by itself adds any files found in the directory to the classpath, this is useful for including all jars in adirectory.When a 'regex' is specified in addition to a 'dir', only thefiles in that directory which completely match the regex(anchored on both ends) will be included.If a 'dir' option (with or without a regex) is used and nothingis found that matches, a warning will be logged.The examples below can be used to load some solr-contribs along with their external dependencies.--><lib dir="${solr.install.dir:../../../..}/contrib/dataimporthandler/lib/" regex=".*\.jar" /><lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-dataimporthandler-.*\.jar" /><lib dir="${solr.install.dir:../../../..}/contrib/extraction/lib" regex=".*\.jar" /><lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-cell-\d.*\.jar" /><lib dir="${solr.install.dir:../../../..}/contrib/langid/lib/" regex=".*\.jar" /><lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-langid-\d.*\.jar" /><lib dir="${solr.install.dir:../../../..}/contrib/velocity/lib" regex=".*\.jar" /><lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-velocity-\d.*\.jar" /><!-- an exact 'path' can be used instead of a 'dir' to specify a specific jar file.  This will cause a serious error to be logged if it can't be loaded.--><!--<lib path="../a-jar-that-does-not-exist.jar" /> --><!-- Data DirectoryUsed to specify an alternate directory to hold all index dataother than the default ./data under the Solr home.  Ifreplication is in use, this should match the replicationconfiguration.--><dataDir>${solr.data.dir:}</dataDir><!-- The DirectoryFactory to use for indexes.solr.StandardDirectoryFactory is filesystembased and tries to pick the best implementation for the currentJVM and platform.  solr.NRTCachingDirectoryFactory, the default,wraps solr.StandardDirectoryFactory and caches small files in memoryfor better NRT performance.One can force a particular implementation via solr.MMapDirectoryFactory,solr.NIOFSDirectoryFactory, or solr.SimpleFSDirectoryFactory.solr.RAMDirectoryFactory is memory based, notpersistent, and doesn't work with replication.--><directoryFactory name="DirectoryFactory" class="${solr.directoryFactory:solr.NRTCachingDirectoryFactory}"><!-- These will be used if you are using the solr.HdfsDirectoryFactory,otherwise they will be ignored. If you don't plan on using hdfs,you can safely remove this section. -->      <!-- The root directory that collection data should be written to. -->     <str name="solr.hdfs.home">${solr.hdfs.home:}</str><!-- The hadoop configuration files to use for the hdfs client. -->    <str name="solr.hdfs.confdir">${solr.hdfs.confdir:}</str><!-- Enable/Disable the hdfs cache. -->    <str name="solr.hdfs.blockcache.enabled">${solr.hdfs.blockcache.enabled:true}</str><!-- Enable/Disable using one global cache for all SolrCores. The settings used will be from the first HdfsDirectoryFactory created. -->    <str name="solr.hdfs.blockcache.global">${solr.hdfs.blockcache.global:true}</str></directoryFactory> <!-- The CodecFactory for defining the format of the inverted index.The default implementation is SchemaCodecFactory, which is the official Luceneindex format, but hooks into the schema to provide per-field customization ofthe postings lists and per-document values in the fieldType element(postingsFormat/docValuesFormat). Note that most of the alternative implementationsare experimental, so if you choose to customize the index format, it's a goodidea to convert back to the official format e.g. via IndexWriter.addIndexes(IndexReader)before upgrading to a newer version to avoid unnecessary reindexing.--><codecFactory class="solr.SchemaCodecFactory"/><!-- To disable dynamic schema REST APIs, use the following for <schemaFactory>:<schemaFactory class="ClassicIndexSchemaFactory"/>When ManagedIndexSchemaFactory is specified instead, Solr will load the schema fromthe resource named in 'managedSchemaResourceName', rather than from schema.xml.Note that the managed schema resource CANNOT be named schema.xml.  If the managedschema does not exist, Solr will create it after reading schema.xml, then rename'schema.xml' to 'schema.xml.bak'.Do NOT hand edit the managed schema - external modifications will be ignored andoverwritten as a result of schema modification REST API calls.When ManagedIndexSchemaFactory is specified with mutable = true, schemamodification REST API calls will be allowed; otherwise, error responses will besent back for these requests.--><schemaFactory class="ManagedIndexSchemaFactory"><bool name="mutable">true</bool><str name="managedSchemaResourceName">managed-schema</str></schemaFactory><!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Index Config - These settings control low-level behavior of indexingMost example settings here show the default value, but are commentedout, to more easily see where customizations have been made.Note: This replaces <indexDefaults> and <mainIndex> from older versions~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --><indexConfig><!-- maxFieldLength was removed in 4.0. To get similar behavior, include a LimitTokenCountFilterFactory in your fieldType definition. E.g. <filter class="solr.LimitTokenCountFilterFactory" maxTokenCount="10000"/>--><!-- Maximum time to wait for a write lock (ms) for an IndexWriter. Default: 1000 --><!-- <writeLockTimeout>1000</writeLockTimeout>  --><!-- Expert: Enabling compound file will use less files for the index, using fewer file descriptors on the expense of performance decrease. Default in Lucene is "true". Default in Solr is "false" (since 3.6) --><!-- <useCompoundFile>false</useCompoundFile> --><!-- ramBufferSizeMB sets the amount of RAM that may be used by Luceneindexing for buffering added documents and deletions before they areflushed to the Directory.maxBufferedDocs sets a limit on the number of documents bufferedbefore flushing.If both ramBufferSizeMB and maxBufferedDocs is set, thenLucene will flush based on whichever limit is hit first.The default is 100 MB.  --><!-- <ramBufferSizeMB>100</ramBufferSizeMB> --><!-- <maxBufferedDocs>1000</maxBufferedDocs> --><!-- Expert: Merge Policy The Merge Policy in Lucene controls how merging of segments is done.The default since Solr/Lucene 3.3 is TieredMergePolicy.The default since Lucene 2.3 was the LogByteSizeMergePolicy,Even older versions of Lucene used LogDocMergePolicy.--><!--<mergePolicyFactory class="solr.TieredMergePolicyFactory"><int name="maxMergeAtOnce">10</int><int name="segmentsPerTier">10</int></mergePolicyFactory>--><!-- Expert: Merge SchedulerThe Merge Scheduler in Lucene controls how merges areperformed.  The ConcurrentMergeScheduler (Lucene 2.3 default)can perform merges in the background using separate threads.The SerialMergeScheduler (Lucene 2.2 default) does not.--><!-- <mergeScheduler class="org.apache.lucene.index.ConcurrentMergeScheduler"/>--><!-- LockFactory This option specifies which Lucene LockFactory implementationto use.single = SingleInstanceLockFactory - suggested for aread-only index or when there is no possibility ofanother process trying to modify the index.native = NativeFSLockFactory - uses OS native file locking.Do not use when multiple solr webapps in the sameJVM are attempting to share a single index.simple = SimpleFSLockFactory  - uses a plain file for lockingDefaults: 'native' is default for Solr3.6 and later, otherwise'simple' is the defaultMore details on the nuances of each LockFactory...http://wiki.apache.org/lucene-java/AvailableLockFactories--><lockType>${solr.lock.type:native}</lockType><!-- Commit Deletion PolicyCustom deletion policies can be specified here. The class mustimplement org.apache.lucene.index.IndexDeletionPolicy.The default Solr IndexDeletionPolicy implementation supportsdeleting index commit points on number of commits, age ofcommit point and optimized status.The latest commit point should always be preserved regardlessof the criteria.--><!-- <deletionPolicy class="solr.SolrDeletionPolicy">--><!-- The number of commit points to be kept --><!-- <str name="maxCommitsToKeep">1</str> --><!-- The number of optimized commit points to be kept --><!-- <str name="maxOptimizedCommitsToKeep">0</str> --><!--Delete all commit points once they have reached the given age.Supports DateMathParser syntax e.g.--><!--<str name="maxCommitAge">30MINUTES</str><str name="maxCommitAge">1DAY</str>--><!-- </deletionPolicy>--><!-- Lucene InfostreamTo aid in advanced debugging, Lucene provides an "InfoStream"of detailed information when indexing.Setting the value to true will instruct the underlying LuceneIndexWriter to write its info stream to solr's log. By default,this is enabled here, and controlled through log4j.properties.--><infoStream>true</infoStream></indexConfig><!-- JMXThis example enables JMX if and only if an existing MBeanServeris found, use this if you want to configure JMX through JVMparameters. Remove this to disable exposing Solr configurationand statistics to JMX.For more details see http://wiki.apache.org/solr/SolrJmx--><jmx /><!-- If you want to connect to a particular server, specify theagentId --><!-- <jmx agentId="myAgent" /> --><!-- If you want to start a new MBeanServer, specify the serviceUrl --><!-- <jmx serviceUrl="service:jmx:rmi:///jndi/rmi://localhost:9999/solr"/>--><!-- The default high-performance update handler --><updateHandler class="solr.DirectUpdateHandler2"><!-- Enables a transaction log, used for real-time get, durability, andand solr cloud replica recovery.  The log can grow as big asuncommitted changes to the index, so use of a hard autoCommitis recommended (see below)."dir" - the target directory for transaction logs, defaults to thesolr data directory.  --> <!--<updateLog><str name="dir">${solr.ulog.dir:}</str></updateLog>--><!-- AutoCommitPerform a hard commit automatically under certain conditions.Instead of enabling autoCommit, consider using "commitWithin"when adding documents. http://wiki.apache.org/solr/UpdateXmlMessagesmaxDocs - Maximum number of documents to add since the lastcommit before automatically triggering a new commit.maxTime - Maximum amount of time in ms that is allowed to passsince a document was added before automaticallytriggering a new commit. openSearcher - if false, the commit causes recent index changesto be flushed to stable storage, but does not cause a newsearcher to be opened to make those changes visible.If the updateLog is enabled, then it's highly recommended tohave some sort of hard autoCommit to limit the log size.--><autoCommit> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime> <openSearcher>false</openSearcher> </autoCommit><!-- softAutoCommit is like autoCommit except it causes a'soft' commit which only ensures that changes are visiblebut does not ensure that data is synced to disk.  This isfaster and more near-realtime friendly than a hard commit.--><autoSoftCommit> <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime> </autoSoftCommit><!-- Update Related Event ListenersVarious IndexWriter related events can trigger Listeners totake actions.postCommit - fired after every commit or optimize commandpostOptimize - fired after every optimize command--><!-- The RunExecutableListener executes an external command from ahook such as postCommit or postOptimize.exe - the name of the executable to rundir - dir to use as the current working directory. (default=".")wait - the calling thread waits until the executable returns. (default="true")args - the arguments to pass to the program.  (default is none)env - environment variables to set.  (default is none)--><!-- This example shows how RunExecutableListener could be usedwith the script based replication...http://wiki.apache.org/solr/CollectionDistribution--><!--<listener event="postCommit" class="solr.RunExecutableListener"><str name="exe">solr/bin/snapshooter</str><str name="dir">.</str><bool name="wait">true</bool><arr name="args"> <str>arg1</str> <str>arg2</str> </arr><arr name="env"> <str>MYVAR=val1</str> </arr></listener>--></updateHandler><!-- IndexReaderFactoryUse the following format to specify a custom IndexReaderFactory,which allows for alternate IndexReader implementations.** Experimental Feature **Please note - Using a custom IndexReaderFactory may preventcertain other features from working. The API toIndexReaderFactory may change without warning or may even beremoved from future releases if the problems cannot beresolved.** Features that may not work with custom IndexReaderFactory **The ReplicationHandler assumes a disk-resident index. Using acustom IndexReader implementation may cause incompatibilitywith ReplicationHandler and may cause replication to not workcorrectly. See SOLR-1366 for details.--><!--<indexReaderFactory name="IndexReaderFactory" class="package.class"><str name="someArg">Some Value</str></indexReaderFactory >--><!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Query section - these settings control query time things like caches~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --><query><!-- Max Boolean ClausesMaximum number of clauses in each BooleanQuery,  an exceptionis thrown if exceeded.** WARNING **This option actually modifies a global Lucene property thatwill affect all SolrCores.  If multiple solrconfig.xml filesdisagree on this property, the value at any given moment willbe based on the last SolrCore to be initialized.--><maxBooleanClauses>1024</maxBooleanClauses><!-- Solr Internal Query CachesThere are two implementations of cache available for Solr,LRUCache, based on a synchronized LinkedHashMap, andFastLRUCache, based on a ConcurrentHashMap.  FastLRUCache has faster gets and slower puts in singlethreaded operation and thus is generally faster than LRUCachewhen the hit ratio of the cache is high (> 75%), and may befaster under other scenarios on multi-cpu systems.--><!-- Filter CacheCache used by SolrIndexSearcher for filters (DocSets),unordered sets of *all* documents that match a query.  When anew searcher is opened, its caches may be prepopulated or"autowarmed" using data from caches in the old searcher.autowarmCount is the number of items to prepopulate.  ForLRUCache, the autowarmed items will be the most recentlyaccessed items.Parameters:class - the SolrCache implementation LRUCache or(LRUCache or FastLRUCache)size - the maximum number of entries in the cacheinitialSize - the initial capacity (number of entries) ofthe cache.  (see java.util.HashMap)autowarmCount - the number of entries to prepopulate fromand old cache.  --><filterCache class="solr.FastLRUCache"size="512"initialSize="512"autowarmCount="0"/><!-- Query Result CacheCaches results of searches - ordered lists of document ids(DocList) based on a query, a sort, and the range of documents requested.  --><queryResultCache class="solr.LRUCache"size="512"initialSize="512"autowarmCount="0"/><!-- Document CacheCaches Lucene Document objects (the stored fields for eachdocument).  Since Lucene internal document ids are transient,this cache will not be autowarmed.  --><documentCache class="solr.LRUCache"size="512"initialSize="512"autowarmCount="0"/><!-- custom cache currently used by block join --> <cache name="perSegFilter"class="solr.search.LRUCache"size="10"initialSize="0"autowarmCount="10"regenerator="solr.NoOpRegenerator" /><!-- Field Value CacheCache used to hold field values that are quickly accessibleby document id.  The fieldValueCache is created by defaulteven if not configured here.--><!--<fieldValueCache class="solr.FastLRUCache"size="512"autowarmCount="128"showItems="32" />--><!-- Custom CacheExample of a generic cache.  These caches may be accessed byname through SolrIndexSearcher.getCache(),cacheLookup(), andcacheInsert().  The purpose is to enable easy caching ofuser/application level data.  The regenerator argument shouldbe specified as an implementation of solr.CacheRegenerator if autowarming is desired.  --><!--<cache name="myUserCache"class="solr.LRUCache"size="4096"initialSize="1024"autowarmCount="1024"regenerator="com.mycompany.MyRegenerator"/>--><!-- Lazy Field LoadingIf true, stored fields that are not requested will be loadedlazily.  This can result in a significant speed improvementif the usual case is to not load all stored fields,especially if the skipped fields are large compressed textfields.--><enableLazyFieldLoading>true</enableLazyFieldLoading><!-- Use Filter For Sorted QueryA possible optimization that attempts to use a filter tosatisfy a search.  If the requested sort does not includescore, then the filterCache will be checked for a filtermatching the query. If found, the filter will be used as thesource of document ids, and then the sort will be applied tothat.For most situations, this will not be useful unless youfrequently get the same search repeatedly with different sortoptions, and none of them ever use "score"--><!--<useFilterForSortedQuery>true</useFilterForSortedQuery>--><!-- Result Window SizeAn optimization for use with the queryResultCache.  When a searchis requested, a superset of the requested number of document idsare collected.  For example, if a search for a particular queryrequests matching documents 10 through 19, and queryWindowSize is 50,then documents 0 through 49 will be collected and cached.  Any furtherrequests in that range can be satisfied via the cache.  --><queryResultWindowSize>20</queryResultWindowSize><!-- Maximum number of documents to cache for any entry in thequeryResultCache. --><queryResultMaxDocsCached>200</queryResultMaxDocsCached><!-- Query Related Event ListenersVarious IndexSearcher related events can trigger Listeners totake actions.newSearcher - fired whenever a new searcher is being preparedand there is a current searcher handling requests (akaregistered).  It can be used to prime certain caches toprevent long request times for certain requests.firstSearcher - fired whenever a new searcher is beingprepared but there is no current registered searcher to handlerequests or to gain autowarming data from.--><!-- QuerySenderListener takes an array of NamedList and executes alocal query request for each NamedList in sequence. --><listener event="newSearcher" class="solr.QuerySenderListener"><arr name="queries"><!--<lst><str name="q">solr</str><str name="sort">price asc</str></lst><lst><str name="q">rocks</str><str name="sort">weight asc</str></lst>--></arr></listener><listener event="firstSearcher" class="solr.QuerySenderListener"><arr name="queries"><lst><str name="q">static firstSearcher warming in solrconfig.xml</str></lst></arr></listener><!-- Use Cold SearcherIf a search request comes in and there is no currentregistered searcher, then immediately register the stillwarming searcher and use it.  If "false" then all requestswill block until the first searcher is done warming.--><useColdSearcher>false</useColdSearcher><!-- Max Warming SearchersMaximum number of searchers that may be warming in thebackground concurrently.  An error is returned if this limitis exceeded.Recommend values of 1-2 for read-only slaves, higher formasters w/o cache warming.--><maxWarmingSearchers>2</maxWarmingSearchers></query><!-- Request DispatcherThis section contains instructions for how the SolrDispatchFiltershould behave when processing requests for this SolrCore.handleSelect is a legacy option that affects the behavior of requestssuch as /select?qt=XXXhandleSelect="true" will cause the SolrDispatchFilter to processthe request and dispatch the query to a handler specified by the "qt" param, assuming "/select" isn't already registered.handleSelect="false" will cause the SolrDispatchFilter toignore "/select" requests, resulting in a 404 unless a handleris explicitly registered with the name "/select"handleSelect="true" is not recommended for new users, but is the defaultfor backwards compatibility--><requestDispatcher handleSelect="false" ><!-- Request ParsingThese settings indicate how Solr Requests may be parsed, andwhat restrictions may be placed on the ContentStreams fromthose requestsenableRemoteStreaming - enables use of the stream.fileand stream.url parameters for specifying remote streams.multipartUploadLimitInKB - specifies the max size (in KiB) ofMultipart File Uploads that Solr will allow in a Request.formdataUploadLimitInKB - specifies the max size (in KiB) ofform data (application/x-www-form-urlencoded) sent viaPOST. You can use POST to pass request parameters notfitting into the URL.addHttpRequestToContext - if set to true, it will instructthe requestParsers to include the original HttpServletRequestobject in the context map of the SolrQueryRequest under the key "httpRequest". It will not be used by any of the existingSolr components, but may be useful when developing custom plugins.*** WARNING ***The settings below authorize Solr to fetch remote files, Youshould make sure your system has some authentication beforeusing enableRemoteStreaming="true"--> <requestParsers enableRemoteStreaming="true" multipartUploadLimitInKB="2048000"formdataUploadLimitInKB="2048"addHttpRequestToContext="false"/><!-- HTTP CachingSet HTTP caching related parameters (for proxy caches and clients).The options below instruct Solr not to output any HTTP Cachingrelated headers--><httpCaching never304="true" /><!-- If you include a <cacheControl> directive, it will be used togenerate a Cache-Control header (as well as an Expires headerif the value contains "max-age=")By default, no Cache-Control header is generated.You can use the <cacheControl> option even if you have setnever304="true"--><!--<httpCaching never304="true" ><cacheControl>max-age=30, public</cacheControl> </httpCaching>--><!-- To enable Solr to respond with automatically generated HTTPCaching headers, and to response to Cache Validation requestscorrectly, set the value of never304="false"This will cause Solr to generate Last-Modified and ETagheaders based on the properties of the Index.The following options can also be specified to affect thevalues of these headers...lastModFrom - the default value is "openTime" which means theLast-Modified value (and validation against If-Modified-Sincerequests) will all be relative to when the current Searcherwas opened.  You can change it to lastModFrom="dirLastMod" ifyou want the value to exactly correspond to when the physicalindex was last modified.etagSeed="..." is an option you can change to force the ETagheader (and validation against If-None-Match requests) to bedifferent even if the index has not changed (ie: when makingsignificant changes to your config file)(lastModifiedFrom and etagSeed are both ignored if you usethe never304="true" option)--><!--<httpCaching lastModifiedFrom="openTime"etagSeed="Solr"><cacheControl>max-age=30, public</cacheControl> </httpCaching>--></requestDispatcher><!-- Request Handlers http://wiki.apache.org/solr/SolrRequestHandlerIncoming queries will be dispatched to a specific handler by namebased on the path specified in the request.Legacy behavior: If the request path uses "/select" but no RequestHandler has that name, and if handleSelect="true" has been specified inthe requestDispatcher, then the Request Handler is dispatched based onthe qt parameter.  Handlers without a leading '/' are accessed this waylike so: http://host/app/[core/]select?qt=name  If no qt isgiven, then the requestHandler that declares default="true" will beused or the one named "standard".If a Request Handler is declared with startup="lazy", then it willnot be initialized until the first request that uses it.--><requestHandler name="/dataimport" class="solr.DataImportHandler"><lst name="defaults"><str name="config">tika-data-config.xml</str></lst></requestHandler><!-- SearchHandlerhttp://wiki.apache.org/solr/SearchHandlerFor processing Search Queries, the primary Request Handlerprovided with Solr is "SearchHandler" It delegates to a sequentof SearchComponents (see below) and supports distributedqueries across multiple shards--><requestHandler name="/select" class="solr.SearchHandler"><!-- default values for query parameters can be specified, thesewill be overridden by parameters in the request--><lst name="defaults"><str name="echoParams">explicit</str><int name="rows">10</int><str name="df">text</str></lst><!-- In addition to defaults, "appends" params can be specifiedto identify values which should be appended to the list ofmulti-val params from the query (or the existing "defaults").--><!-- In this example, the param "fq=instock:true" would be appended toany query time fq params the user may specify, as a mechanism forpartitioning the index, independent of any user selected filteringthat may also be desired (perhaps as a result of faceted searching).NOTE: there is *absolutely* nothing a client can do to prevent these"appends" values from being used, so don't use this mechanismunless you are sure you always want it.--><!--<lst name="appends"><str name="fq">inStock:true</str></lst>--><!-- "invariants" are a way of letting the Solr maintainer lock downthe options available to Solr clients.  Any params valuesspecified here are used regardless of what values may be specifiedin either the query, the "defaults", or the "appends" params.In this example, the facet.field and facet.query params wouldbe fixed, limiting the facets clients can use.  Faceting isnot turned on by default - but if the client does specifyfacet=true in the request, these are the only facets theywill be able to see counts for; regardless of what otherfacet.field or facet.query params they may specify.NOTE: there is *absolutely* nothing a client can do to prevent these"invariants" values from being used, so don't use this mechanismunless you are sure you always want it.--><!--<lst name="invariants"><str name="facet.field">cat</str><str name="facet.field">manu_exact</str><str name="facet.query">price:[* TO 500]</str><str name="facet.query">price:[500 TO *]</str></lst>--><!-- If the default list of SearchComponents is not desired, thatlist can either be overridden completely, or components can beprepended or appended to the default list.  (see below)--><!--<arr name="components"><str>nameOfCustomComponent1</str><str>nameOfCustomComponent2</str></arr>--></requestHandler><!-- A request handler that returns indented JSON by default --><requestHandler name="/query" class="solr.SearchHandler"><lst name="defaults"><str name="echoParams">explicit</str><str name="wt">json</str><str name="indent">true</str><str name="df">text</str></lst></requestHandler><!-- A Robust ExampleThis example SearchHandler declaration shows off usage of theSearchHandler with many defaults declaredNote that multiple instances of the same Request Handler(SearchHandler) can be registered multiple times with differentnames (and different init parameters)--><requestHandler name="/browse" class="solr.SearchHandler"><lst name="defaults"><str name="echoParams">explicit</str><!-- VelocityResponseWriter settings --><str name="wt">velocity</str><str name="v.template">browse</str><str name="v.layout">layout</str><!-- Query settings --><str name="defType">edismax</str><str name="q.alt">*:*</str><str name="rows">10</str><str name="fl">*,score</str><!-- Faceting defaults --><str name="facet">on</str><str name="facet.mincount">1</str></lst></requestHandler><initParams path="/update/**,/query,/select,/tvrh,/elevate,/spell,/browse"><lst name="defaults"><str name="df">text</str></lst></initParams><!-- Solr Cell Update Request Handlerhttp://wiki.apache.org/solr/ExtractingRequestHandler --><requestHandler name="/update/extract" startup="lazy"class="solr.extraction.ExtractingRequestHandler" ><lst name="defaults"><str name="lowernames">true</str><str name="uprefix">ignored_</str><!-- capture link hrefs but ignore div attributes --><str name="captureAttr">true</str><str name="fmap.a">links</str><str name="fmap.div">ignored_</str></lst></requestHandler><!-- Field Analysis Request HandlerRequestHandler that provides much the same functionality asanalysis.jsp. Provides the ability to specify multiple fieldtypes and field names in the same request and outputsindex-time and query-time analysis for each of them.Request parameters are:analysis.fieldname - field name whose analyzers are to be usedanalysis.fieldtype - field type whose analyzers are to be usedanalysis.fieldvalue - text for index-time analysisq (or analysis.q) - text for query time analysisanalysis.showmatch (true|false) - When set to true and whenquery analysis is performed, the produced tokens of thefield value analysis will be marked as "matched" for everytoken that is produces by the query analysis--><requestHandler name="/analysis/field" startup="lazy"class="solr.FieldAnalysisRequestHandler" /><!-- Document Analysis Handlerhttp://wiki.apache.org/solr/AnalysisRequestHandlerAn analysis handler that provides a breakdown of the analysisprocess of provided documents. This handler expects a (single)content stream with the following format:<docs><doc><field name="id">1</field><field name="name">The Name</field><field name="text">The Text Value</field></doc><doc>...</doc><doc>...</doc>...</docs>Note: Each document must contain a field which serves as theunique key. This key is used in the returned response to associatean analysis breakdown to the analyzed document.Like the FieldAnalysisRequestHandler, this handler also supportsquery analysis by sending either an "analysis.query" or "q"request parameter that holds the query text to be analyzed. Italso supports the "analysis.showmatch" parameter which when set totrue, all field tokens that match the query tokens will be markedas a "match". --><requestHandler name="/analysis/document" class="solr.DocumentAnalysisRequestHandler" startup="lazy" /><!-- Echo the request contents back to the client --><requestHandler name="/debug/dump" class="solr.DumpRequestHandler" ><lst name="defaults"><str name="echoParams">explicit</str> <str name="echoHandler">true</str></lst></requestHandler><!-- Search ComponentsSearch components are registered to SolrCore and used by instances of SearchHandler (which can access them by name)By default, the following components are available:<searchComponent name="query"     class="solr.QueryComponent" /><searchComponent name="facet"     class="solr.FacetComponent" /><searchComponent name="mlt"       class="solr.MoreLikeThisComponent" /><searchComponent name="highlight" class="solr.HighlightComponent" /><searchComponent name="stats"     class="solr.StatsComponent" /><searchComponent name="debug"     class="solr.DebugComponent" />Default configuration in a requestHandler would look like:<arr name="components"><str>query</str><str>facet</str><str>mlt</str><str>highlight</str><str>stats</str><str>debug</str></arr>If you register a searchComponent to one of the standard names, that will be used instead of the default.To insert components before or after the 'standard' components, use:<arr name="first-components"><str>myFirstComponentName</str></arr><arr name="last-components"><str>myLastComponentName</str></arr>NOTE: The component registered with the name "debug" willalways be executed after the "last-components" --><!-- Spell CheckThe spell check component can return a list of alternative spellingsuggestions.  http://wiki.apache.org/solr/SpellCheckComponent--><searchComponent name="spellcheck" class="solr.SpellCheckComponent"><str name="queryAnalyzerFieldType">text_general</str><!-- Multiple "Spell Checkers" can be declared and used by thiscomponent--><!-- a spellchecker built from a field of the main index --><lst name="spellchecker"><str name="name">default</str><str name="field">text</str><str name="classname">solr.DirectSolrSpellChecker</str><!-- the spellcheck distance measure used, the default is the internal levenshtein --><str name="distanceMeasure">internal</str><!-- minimum accuracy needed to be considered a valid spellcheck suggestion --><float name="accuracy">0.5</float><!-- the maximum #edits we consider when enumerating terms: can be 1 or 2 --><int name="maxEdits">2</int><!-- the minimum shared prefix when enumerating terms --><int name="minPrefix">1</int><!-- maximum number of inspections per result. --><int name="maxInspections">5</int><!-- minimum length of a query term to be considered for correction --><int name="minQueryLength">4</int><!-- maximum threshold of documents a query term can appear to be considered for correction --><float name="maxQueryFrequency">0.01</float><!-- uncomment this to require suggestions to occur in 1% of the documents<float name="thresholdTokenFrequency">.01</float>--></lst><!-- a spellchecker that can break or combine words.  See "/spell" handler below for usage --><lst name="spellchecker"><str name="name">wordbreak</str><str name="classname">solr.WordBreakSolrSpellChecker</str>      <str name="field">name</str><str name="combineWords">true</str><str name="breakWords">true</str><int name="maxChanges">10</int></lst><!-- a spellchecker that uses a different distance measure --><!--<lst name="spellchecker"><str name="name">jarowinkler</str><str name="field">spell</str><str name="classname">solr.DirectSolrSpellChecker</str><str name="distanceMeasure">org.apache.lucene.search.spell.JaroWinklerDistance</str></lst>--><!-- a spellchecker that use an alternate comparator comparatorClass be one of:1. score (default)2. freq (Frequency first, then score)3. A fully qualified class name--><!--<lst name="spellchecker"><str name="name">freq</str><str name="field">lowerfilt</str><str name="classname">solr.DirectSolrSpellChecker</str><str name="comparatorClass">freq</str>--><!-- A spellchecker that reads the list of words from a file --><!--<lst name="spellchecker"><str name="classname">solr.FileBasedSpellChecker</str><str name="name">file</str><str name="sourceLocation">spellings.txt</str><str name="characterEncoding">UTF-8</str><str name="spellcheckIndexDir">spellcheckerFile</str></lst>--></searchComponent><!-- A request handler for demonstrating the spellcheck component.  NOTE: This is purely as an example.  The whole purpose of theSpellCheckComponent is to hook it into the request handler thathandles your normal user queries so that a separate request isnot needed to get suggestions.IN OTHER WORDS, THERE IS REALLY GOOD CHANCE THE SETUP BELOW ISNOT WHAT YOU WANT FOR YOUR PRODUCTION SYSTEM!See http://wiki.apache.org/solr/SpellCheckComponent for detailson the request parameters.--><requestHandler name="/spell" class="solr.SearchHandler" startup="lazy"><lst name="defaults"><str name="df">text</str><!-- Solr will use suggestions from both the 'default' spellcheckerand from the 'wordbreak' spellchecker and combine them.collations (re-written queries) can include a combination ofcorrections from both spellcheckers --><str name="spellcheck.dictionary">default</str><str name="spellcheck.dictionary">wordbreak</str><str name="spellcheck">on</str><str name="spellcheck.extendedResults">true</str>       <str name="spellcheck.count">10</str><str name="spellcheck.alternativeTermCount">5</str><str name="spellcheck.maxResultsForSuggest">5</str>       <str name="spellcheck.collate">true</str><str name="spellcheck.collateExtendedResults">true</str>  <str name="spellcheck.maxCollationTries">10</str><str name="spellcheck.maxCollations">5</str>         </lst><arr name="last-components"><str>spellcheck</str></arr></requestHandler><searchComponent name="suggest" class="solr.SuggestComponent"><lst name="suggester"><str name="name">mySuggester</str><str name="lookupImpl">FuzzyLookupFactory</str>      <!-- org.apache.solr.spelling.suggest.fst --><str name="dictionaryImpl">DocumentDictionaryFactory</str>     <!-- org.apache.solr.spelling.suggest.HighFrequencyDictionaryFactory --> <str name="field">cat</str><str name="weightField">price</str><str name="suggestAnalyzerFieldType">string</str></lst></searchComponent><requestHandler name="/suggest" class="solr.SearchHandler" startup="lazy"><lst name="defaults"><str name="suggest">true</str><str name="suggest.count">10</str></lst><arr name="components"><str>suggest</str></arr></requestHandler><!-- Term Vector Componenthttp://wiki.apache.org/solr/TermVectorComponent--><searchComponent name="tvComponent" class="solr.TermVectorComponent"/><!-- A request handler for demonstrating the term vector componentThis is purely as an example.In reality you will likely want to add the component to your already specified request handlers. --><requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy"><lst name="defaults"><str name="df">text</str><bool name="tv">true</bool></lst><arr name="last-components"><str>tvComponent</str></arr></requestHandler><!-- Terms Componenthttp://wiki.apache.org/solr/TermsComponentA component to return terms and document frequency of thoseterms--><searchComponent name="terms" class="solr.TermsComponent"/><!-- A request handler for demonstrating the terms component --><requestHandler name="/terms" class="solr.SearchHandler" startup="lazy"><lst name="defaults"><bool name="terms">true</bool><bool name="distrib">false</bool></lst>     <arr name="components"><str>terms</str></arr></requestHandler><!-- Highlighting Componenthttp://wiki.apache.org/solr/HighlightingParameters--><searchComponent class="solr.HighlightComponent" name="highlight"><highlighting><!-- Configure the standard fragmenter --><!-- This could most likely be commented out in the "default" case --><fragmenter name="gap" default="true"class="solr.highlight.GapFragmenter"><lst name="defaults"><int name="hl.fragsize">100</int></lst></fragmenter><!-- A regular-expression-based fragmenter (for sentence extraction) --><fragmenter name="regex" class="solr.highlight.RegexFragmenter"><lst name="defaults"><!-- slightly smaller fragsizes work better because of slop --><int name="hl.fragsize">70</int><!-- allow 50% slop on fragment sizes --><float name="hl.regex.slop">0.5</float><!-- a basic sentence pattern --><str name="hl.regex.pattern">[-\w ,/\n\&quot;&apos;]{20,200}</str></lst></fragmenter><!-- Configure the standard formatter --><formatter name="html" default="true"class="solr.highlight.HtmlFormatter"><lst name="defaults"><str name="hl.simple.pre"><![CDATA[<em>]]></str><str name="hl.simple.post"><![CDATA[</em>]]></str></lst></formatter><!-- Configure the standard encoder --><encoder name="html" class="solr.highlight.HtmlEncoder" /><!-- Configure the standard fragListBuilder --><fragListBuilder name="simple" class="solr.highlight.SimpleFragListBuilder"/><!-- Configure the single fragListBuilder --><fragListBuilder name="single" class="solr.highlight.SingleFragListBuilder"/><!-- Configure the weighted fragListBuilder --><fragListBuilder name="weighted" default="true"class="solr.highlight.WeightedFragListBuilder"/><!-- default tag FragmentsBuilder --><fragmentsBuilder name="default" default="true"class="solr.highlight.ScoreOrderFragmentsBuilder"><!-- <lst name="defaults"><str name="hl.multiValuedSeparatorChar">/</str></lst>--></fragmentsBuilder><!-- multi-colored tag FragmentsBuilder --><fragmentsBuilder name="colored" class="solr.highlight.ScoreOrderFragmentsBuilder"><lst name="defaults"><str name="hl.tag.pre"><![CDATA[<b style="background:yellow">,<b style="background:lawgreen">,<b style="background:aquamarine">,<b style="background:magenta">,<b style="background:palegreen">,<b style="background:coral">,<b style="background:wheat">,<b style="background:khaki">,<b style="background:lime">,<b style="background:deepskyblue">]]></str><str name="hl.tag.post"><![CDATA[</b>]]></str></lst></fragmentsBuilder><boundaryScanner name="default" default="true"class="solr.highlight.SimpleBoundaryScanner"><lst name="defaults"><str name="hl.bs.maxScan">10</str><str name="hl.bs.chars">.,!? &#9;&#10;&#13;</str></lst></boundaryScanner><boundaryScanner name="breakIterator" class="solr.highlight.BreakIteratorBoundaryScanner"><lst name="defaults"><!-- type should be one of CHARACTER, WORD(default), LINE and SENTENCE --><str name="hl.bs.type">WORD</str><!-- language and country are used when constructing Locale object.  --><!-- And the Locale object will be used when getting instance of BreakIterator --><str name="hl.bs.language">en</str><str name="hl.bs.country">US</str></lst></boundaryScanner></highlighting></searchComponent><!-- Update ProcessorsChains of Update Processor Factories for dealing with UpdateRequests can be declared, and then used by name in UpdateRequest Processorshttp://wiki.apache.org/solr/UpdateRequestProcessor--> <!-- DeduplicationAn example dedup update processor that creates the "id" fieldon the fly based on the hash code of some other fields.  Thisexample has overwriteDupes set to false since we are using theid field as the signatureField and Solr will maintainuniqueness based on that anyway.  --><!--<updateRequestProcessorChain name="dedupe"><processor class="solr.processor.SignatureUpdateProcessorFactory"><bool name="enabled">true</bool><str name="signatureField">id</str><bool name="overwriteDupes">false</bool><str name="fields">name,features,cat</str><str name="signatureClass">solr.processor.Lookup3Signature</str></processor><processor class="solr.LogUpdateProcessorFactory" /><processor class="solr.RunUpdateProcessorFactory" /></updateRequestProcessorChain>--><!-- Language identificationThis example update chain identifies the language of the incomingdocuments using the langid contrib. The detected language iswritten to field language_s. No field name mapping is done.The fields used for detection are text, title, subject and description,making this example suitable for detecting languages form full-textrich documents injected via ExtractingRequestHandler.See more about langId at http://wiki.apache.org/solr/LanguageDetection--><!--<updateRequestProcessorChain name="langid"><processor class="org.apache.solr.update.processor.TikaLanguageIdentifierUpdateProcessorFactory"><str name="langid.fl">text,title,subject,description</str><str name="langid.langField">language_s</str><str name="langid.fallback">en</str></processor><processor class="solr.LogUpdateProcessorFactory" /><processor class="solr.RunUpdateProcessorFactory" /></updateRequestProcessorChain>--><!-- Script update processorThis example hooks in an update processor implemented using JavaScript.See more about the script update processor at http://wiki.apache.org/solr/ScriptUpdateProcessor--><!--<updateRequestProcessorChain name="script"><processor class="solr.StatelessScriptUpdateProcessorFactory"><str name="script">update-script.js</str><lst name="params"><str name="config_param">example config parameter</str></lst></processor><processor class="solr.RunUpdateProcessorFactory" /></updateRequestProcessorChain>--><!-- Response Writershttp://wiki.apache.org/solr/QueryResponseWriterRequest responses will be written using the writer specified bythe 'wt' request parameter matching the name of a registeredwriter.The "default" writer is the default and will be used if 'wt' isnot specified in the request.--><!-- The following response writers are implicitly configured unlessoverridden...--><!--<queryResponseWriter name="xml" default="true"class="solr.XMLResponseWriter" /><queryResponseWriter name="json" class="solr.JSONResponseWriter"/><queryResponseWriter name="python" class="solr.PythonResponseWriter"/><queryResponseWriter name="ruby" class="solr.RubyResponseWriter"/><queryResponseWriter name="php" class="solr.PHPResponseWriter"/><queryResponseWriter name="phps" class="solr.PHPSerializedResponseWriter"/><queryResponseWriter name="csv" class="solr.CSVResponseWriter"/><queryResponseWriter name="schema.xml" class="solr.SchemaXmlResponseWriter"/>--><queryResponseWriter name="json" class="solr.JSONResponseWriter"><!-- For the purposes of the tutorial, JSON responses are written asplain text so that they are easy to read in *any* browser.If you expect a MIME type of "application/json" just remove this override.--><str name="content-type">text/plain; charset=UTF-8</str></queryResponseWriter><!--Custom response writers can be declared as needed...--><queryResponseWriter name="velocity" class="solr.VelocityResponseWriter" startup="lazy"><str name="template.base.dir">${velocity.template.base.dir:}</str></queryResponseWriter><!-- XSLT response writer transforms the XML output by any xslt file foundin Solr's conf/xslt directory.  Changes to xslt files are checked forevery xsltCacheLifetimeSeconds.  --><queryResponseWriter name="xslt" class="solr.XSLTResponseWriter"><int name="xsltCacheLifetimeSeconds">5</int></queryResponseWriter><!-- Query Parsershttp://wiki.apache.org/solr/SolrQuerySyntaxMultiple QParserPlugins can be registered by name, and thenused in either the "defType" param for the QueryComponent (usedby SearchHandler) or in LocalParams--><!-- example of registering a query parser --><!--<queryParser name="myparser" class="com.mycompany.MyQParserPlugin"/>--><!-- Function Parsershttp://wiki.apache.org/solr/FunctionQueryMultiple ValueSourceParsers can be registered by name, and thenused as function names when using the "func" QParser.--><!-- example of registering a custom function parser  --><!--<valueSourceParser name="myfunc" class="com.mycompany.MyValueSourceParser" />--><!-- Document Transformershttp://wiki.apache.org/solr/DocTransformers--><!--Could be something like:<transformer name="db" class="com.mycompany.LoadFromDatabaseTransformer" ><int name="connection">jdbc://....</int></transformer>To add a constant value to all docs, use:<transformer name="mytrans2" class="org.apache.solr.response.transform.ValueAugmenterFactory" ><int name="value">5</int></transformer>If you want the user to still be able to change it with _value:something_ use this:<transformer name="mytrans3" class="org.apache.solr.response.transform.ValueAugmenterFactory" ><double name="defaultValue">5</double></transformer>If you are using the QueryElevationComponent, you may wish to mark documents that get boosted.  TheEditorialMarkerFactory will do exactly that:<transformer name="qecBooster" class="org.apache.solr.response.transform.EditorialMarkerFactory" />--><!-- Legacy config for the admin interface --><admin><defaultQuery>*:*</defaultQuery></admin></config>

修改tika-data-config.xml如下

<dataConfig><dataSource type="BinFileDataSource" /><document><entity name="files" dataSource="null" rootEntity="false"processor="FileListEntityProcessor"baseDir="/usr/local/docs" fileName=".*\.(doc)|(pdf)|(docx)"onError="skip"recursive="true"><field column="fileAbsolutePath" name="id" /><field column="fileSize" name="size" /><field column="fileLastModified" name="lastModified" /><entity name="tika-test" processor="TikaEntityProcessor"url="${files.fileAbsolutePath}" format="text"><field column="Author" name="author" meta="true"/><field column="title" name="title" meta="true"/><field column="text" name="text"/><field column="file" name="fileName"/></entity></entity></document>
</dataConfig>

修改managed-schema配置

<?xml version="1.0" encoding="UTF-8" ?>
<!--Licensed to the Apache Software Foundation (ASF) under one or morecontributor license agreements.  See the NOTICE file distributed withthis work for additional information regarding copyright ownership.The ASF licenses this file to You under the Apache License, Version 2.0(the "License"); you may not use this file except in compliance withthe License.  You may obtain a copy of the License athttp://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.See the License for the specific language governing permissions andlimitations under the License.
--><!--  This is the Solr schema file. This file should be named "schema.xml" andshould be in the conf directory under the solr home(i.e. ./solr/conf/schema.xml by default) or located where the classloader for the Solr webapp can find it.This example schema is the recommended starting point for users.It should be kept correct and concise, usable out-of-the-box.For more information, on how to customize this file, please seehttp://wiki.apache.org/solr/SchemaXmlPERFORMANCE NOTE: this schema includes many optional features and should notbe used for benchmarking.  To improve performance one could- set stored="false" for all fields possible (esp large fields) when youonly need to search on the field but don't need to return the originalvalue.- set indexed="false" if you don't need to search on the field, but onlyreturn the field as a result of searching on other indexed fields.- remove all unneeded copyField statements- for best index size and searching performance, set "index" to falsefor all general text fields, use copyField to copy them to thecatchall "text" field, and use that for searching.- For maximum indexing performance, use the ConcurrentUpdateSolrServerjava client.- Remember to run the JVM in server mode, and use a higher logging levelthat avoids logging every request
--><schema name="example-DIH-tika" version="1.6"><!-- attribute "name" is the name of this schema and is only used for display purposes.version="x.y" is Solr's version number for the schema syntax and semantics.  It should not normally be changed by applications.1.0: multiValued attribute did not exist, all fields are multiValued by nature1.1: multiValued attribute introduced, false by default 1.2: omitTermFreqAndPositions attribute introduced, true by default except for text fields.1.3: removed optional field compress feature1.4: autoGeneratePhraseQueries attribute introduced to drive QueryParserbehavior when a single string produces multiple tokens.  Defaults to off for version >= 1.41.5: omitNorms defaults to true for primitive field types (int, float, boolean, string...)1.6: useDocValuesAsStored defaults to true.            --><!-- Valid attributes for fields:name: mandatory - the name for the fieldtype: mandatory - the name of a field type from the <types> fieldType sectionindexed: true if this field should be indexed (searchable or sortable)stored: true if this field should be retrievabledocValues: true if this field should have doc values. Doc values areuseful for faceting, grouping, sorting and function queries. Although notrequired, doc values will make the index faster to load, moreNRT-friendly and more memory-efficient. They however come with somelimitations: they are currently only supported by StrField, UUIDFieldand all Trie*Fields, and depending on the field type, they mightrequire the field to be single-valued, be required or have a defaultvalue (check the documentation of the field type you're interested infor more information)multiValued: true if this field may contain multiple values per documentomitNorms: (expert) set to true to omit the norms associated withthis field (this disables length normalization and index-timeboosting for the field, and saves some memory).  Only full-textfields or fields that need an index-time boost need norms.Norms are omitted for primitive (non-analyzed) types by default.termVectors: [false] set to true to store the term vector for agiven field.When using MoreLikeThis, fields used for similarity should bestored for best performance.termPositions: Store position information with the term vector.  This will increase storage costs.termOffsets: Store offset information with the term vector. This will increase storage costs.required: The field is required.  It will throw an error if thevalue does not existdefault: a value that should be used if no value is specifiedwhen adding a document.--><!-- field names should consist of alphanumeric or underscore characters only andnot start with a digit.  This is not currently strictly enforced,but other field names will not have first class support from all componentsand back compatibility is not guaranteed.  Names with both leading andtrailing underscores (e.g. _version_) are reserved.--><field name="title" type="text_general" indexed="true" stored="true" multiValued="true"/><field name="author" type="text_general" indexed="true" stored="true"/><field name="text" type="text_general" indexed="true" stored="true" multiValued="true"/><field name="fileName" type="string" indexed="true" stored="true" /><field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" /><field name="size" type="tlong" indexed="true" stored="true" /><field name="lastModified" type="tdate" indexed="true" stored="true" /><!-- Dynamic field definitions allow using convention over configurationfor fields via the specification of patterns to match field names. EXAMPLE:  name="*_i" will match any field ending in _i (like myid_i, z_i)RESTRICTION: the glob-like pattern in the name attribute must havea "*" only at the start or the end.  --><dynamicField name="*_i"  type="int"    indexed="true"  stored="true"/><dynamicField name="*_is" type="int"    indexed="true"  stored="true"  multiValued="true"/><dynamicField name="*_s"  type="string"  indexed="true"  stored="true" /><dynamicField name="*_ss" type="string"  indexed="true"  stored="true" multiValued="true"/><dynamicField name="*_l"  type="long"   indexed="true"  stored="true"/><dynamicField name="*_ls" type="long"   indexed="true"  stored="true"  multiValued="true"/><dynamicField name="*_t"  type="text_general"    indexed="true"  stored="true"/><dynamicField name="*_txt" type="text_general"   indexed="true"  stored="true" multiValued="true"/><dynamicField name="*_en"  type="text_en"    indexed="true"  stored="true" multiValued="true"/><dynamicField name="*_b"  type="boolean" indexed="true" stored="true"/><dynamicField name="*_bs" type="boolean" indexed="true" stored="true"  multiValued="true"/><dynamicField name="*_f"  type="float"  indexed="true"  stored="true"/><dynamicField name="*_fs" type="float"  indexed="true"  stored="true"  multiValued="true"/><dynamicField name="*_d"  type="double" indexed="true"  stored="true"/><dynamicField name="*_ds" type="double" indexed="true"  stored="true"  multiValued="true"/><!-- Type used to index the lat and lon components for the "location" FieldType --><dynamicField name="*_coordinate"  type="tdouble" indexed="true"  stored="false" /><dynamicField name="*_dt"  type="date"    indexed="true"  stored="true"/><dynamicField name="*_dts" type="date"    indexed="true"  stored="true" multiValued="true"/><dynamicField name="*_p"  type="location" indexed="true" stored="true"/><!-- some trie-coded dynamic fields for faster range queries --><dynamicField name="*_ti" type="tint"    indexed="true"  stored="true"/><dynamicField name="*_tl" type="tlong"   indexed="true"  stored="true"/><dynamicField name="*_tf" type="tfloat"  indexed="true"  stored="true"/><dynamicField name="*_td" type="tdouble" indexed="true"  stored="true"/><dynamicField name="*_tdt" type="tdate"  indexed="true"  stored="true"/><dynamicField name="ignored_*" type="ignored" multiValued="true"/><dynamicField name="attr_*" type="text_general" indexed="true" stored="true" multiValued="true"/><dynamicField name="random_*" type="random" /><!-- uncomment the following to ignore any fields that don't already match an existing field name or dynamic field, rather than reporting them as an error. alternately, change the type="ignored" to some other type e.g. "text" if you want unknown fields indexed and/or stored by default --> <!--dynamicField name="*" type="ignored" multiValued="true" /--><!-- Field to use to determine and enforce document uniqueness. Unless this field is marked with required="false", it will be a required field--><!-- <uniqueKey>id</uniqueKey> --><!-- DEPRECATED: The defaultSearchField is consulted by various query parsers whenparsing a query string that isn't explicit about the field.  Machine (non-user)generated queries are best made explicit, or they can use the "df" request parameterwhich takes precedence over this.Note: Un-commenting defaultSearchField will be insufficient if your request handlerin solrconfig.xml defines "df", which takes precedence. That would need to be removed.<defaultSearchField>text</defaultSearchField> --><!-- DEPRECATED: The defaultOperator (AND|OR) is consulted by various query parserswhen parsing a query string to determine if a clause of the query should be marked asrequired or optional, assuming the clause isn't already marked by some operator.The default is OR, which is generally assumed so it is not a good idea to change itglobally here.  The "q.op" request parameter takes precedence over this.<solrQueryParser defaultOperator="OR"/> --><!-- field type definitions. The "name" attribute isjust a label to be used by field definitions.  The "class"attribute and any other attributes determine the realbehavior of the fieldType.Class names starting with "solr" refer to java classes in astandard package such as org.apache.solr.analysis--><!-- The StrField type is not analyzed, but indexed/stored verbatim.It supports doc values but in that case the field needs to besingle-valued and either required or have a default value.--><fieldType name="string" class="solr.StrField" sortMissingLast="true" /><!-- boolean type: "true" or "false" --><fieldType name="boolean" class="solr.BoolField" sortMissingLast="true"/><!-- sortMissingLast and sortMissingFirst attributes are optional attributes arecurrently supported on types that are sorted internally as stringsand on numeric types.This includes "string","boolean", and, as of 3.5 (and 4.x),int, float, long, date, double, including the "Trie" variants.- If sortMissingLast="true", then a sort on this field will cause documentswithout the field to come after documents with the field,regardless of the requested sort order (asc or desc).- If sortMissingFirst="true", then a sort on this field will cause documentswithout the field to come before documents with the field,regardless of the requested sort order.- If sortMissingLast="false" and sortMissingFirst="false" (the default),then default lucene sorting will be used which places docs without thefield first in an ascending sort and last in a descending sort.-->    <!--Default numeric field types. For faster range queries, consider the tint/tfloat/tlong/tdouble types.These fields support doc values, but they require the field to besingle-valued and either be required or have a default value.--><fieldType name="int" class="solr.TrieIntField" precisionStep="0" positionIncrementGap="0"/><fieldType name="float" class="solr.TrieFloatField" precisionStep="0" positionIncrementGap="0"/><fieldType name="long" class="solr.TrieLongField" precisionStep="0" positionIncrementGap="0"/><fieldType name="double" class="solr.TrieDoubleField" precisionStep="0" positionIncrementGap="0"/><!--Numeric field types that index each value at various levels of precisionto accelerate range queries when the number of values between the rangeendpoints is large. See the javadoc for NumericRangeQuery for internalimplementation details.Smaller precisionStep values (specified in bits) will lead to more tokensindexed per value, slightly larger index size, and faster range queries.A precisionStep of 0 disables indexing at different precision levels.--><fieldType name="tint" class="solr.TrieIntField" precisionStep="8" positionIncrementGap="0"/><fieldType name="tfloat" class="solr.TrieFloatField" precisionStep="8" positionIncrementGap="0"/><fieldType name="tlong" class="solr.TrieLongField" precisionStep="8" positionIncrementGap="0"/><fieldType name="tdouble" class="solr.TrieDoubleField" precisionStep="8" positionIncrementGap="0"/><!-- The format for this date field is of the form 1995-12-31T23:59:59Z, andis a more restricted form of the canonical representation of dateTimehttp://www.w3.org/TR/xmlschema-2/#dateTime    The trailing "Z" designates UTC time and is mandatory.Optional fractional seconds are allowed: 1995-12-31T23:59:59.999ZAll other components are mandatory.Expressions can also be used to denote calculations that should beperformed relative to "NOW" to determine the value, ie...NOW/HOUR... Round to the start of the current hourNOW-1DAY... Exactly 1 day prior to nowNOW/DAY+6MONTHS+3DAYS... 6 months and 3 days in the future from the start ofthe current dayConsult the TrieDateField javadocs for more information.Note: For faster range queries, consider the tdate type--><fieldType name="date" class="solr.TrieDateField" precisionStep="0" positionIncrementGap="0"/><!-- A Trie based date field for faster date range queries and date faceting. --><fieldType name="tdate" class="solr.TrieDateField" precisionStep="6" positionIncrementGap="0"/><!--Binary data type. The data should be sent/retrieved in as Base64 encoded Strings --><fieldType name="binary" class="solr.BinaryField"/><!-- The "RandomSortField" is not used to store or search anydata.  You can declare fields of this type it in your schemato generate pseudo-random orderings of your docs for sorting or function purposes.  The ordering is generated based on the fieldname and the version of the index. As long as the index versionremains unchanged, and the same field name is reused,the ordering of the docs will be consistent.  If you want different psuedo-random orderings of documents,for the same version of the index, use a dynamicField andchange the field name in the request.--><fieldType name="random" class="solr.RandomSortField" indexed="true" /><!-- solr.TextField allows the specification of custom text analyzersspecified as a tokenizer and a list of token filters. Differentanalyzers may be specified for indexing and querying.The optional positionIncrementGap puts space between multiple fields ofthis type on the same document, with the purpose of preventing false phrasematching across fields.For more info on customizing your analyzer chain, please seehttp://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters--><!-- One can also specify an existing Analyzer class that has adefault constructor via the class attribute on the analyzer element.Example:<fieldType name="text_greek" class="solr.TextField"><analyzer class="org.apache.lucene.analysis.el.GreekAnalyzer"/></fieldType>--><!-- A text field that only splits on whitespace for exact matching of words --><fieldType name="text_ws" class="solr.TextField" positionIncrementGap="100"><analyzer><tokenizer class="solr.WhitespaceTokenizerFactory"/></analyzer></fieldType><!-- A general text field that has reasonable, genericcross-language defaults: it tokenizes with StandardTokenizer,and down cases. --><fieldType name="text_general" class="solr.TextField" positionIncrementGap="100"><analyzer type="index"><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/></analyzer><analyzer type="query"><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/></analyzer></fieldType><!-- A text field with defaults appropriate for English: ittokenizes with StandardTokenizer, down cases, andfinally applies Porter's stemming. --><fieldType name="text_en" class="solr.TextField" positionIncrementGap="100"><analyzer type="index"><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.EnglishPossessiveFilterFactory"/><!-- Optionally you may want to use this less aggressive stemmer instead of PorterStemFilterFactory:<filter class="solr.EnglishMinimalStemFilterFactory"/>--><filter class="solr.PorterStemFilterFactory"/></analyzer><analyzer type="query"><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.EnglishPossessiveFilterFactory"/><!-- Optionally you may want to use this less aggressive stemmer instead of PorterStemFilterFactory:<filter class="solr.EnglishMinimalStemFilterFactory"/>--><filter class="solr.PorterStemFilterFactory"/></analyzer></fieldType><!-- A text field with defaults appropriate for English, plusaggressive word-splitting and autophrase features enabled.This field is just like text_en, except it addsWordDelimiterFilter to enable splitting and matching ofwords on case-change, alpha numeric boundaries, andnon-alphanumeric chars.  This means certain compound wordcases will work, for example query "wi fi" will matchdocument "WiFi" or "wi-fi".--><fieldType name="text_en_splitting" class="solr.TextField" positionIncrementGap="100" autoGeneratePhraseQueries="true"><analyzer type="index"><tokenizer class="solr.WhitespaceTokenizerFactory"/><filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.PorterStemFilterFactory"/></analyzer><analyzer type="query"><tokenizer class="solr.WhitespaceTokenizerFactory"/><filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="0" catenateNumbers="0" catenateAll="0" splitOnCaseChange="1"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.PorterStemFilterFactory"/></analyzer></fieldType><!-- Less flexible matching, but less false matches.  Probably not ideal for product names,but may be good for SKUs.  Can insert dashes in the wrong place and still match. --><fieldType name="text_en_splitting_tight" class="solr.TextField" positionIncrementGap="100" autoGeneratePhraseQueries="true"><analyzer><tokenizer class="solr.WhitespaceTokenizerFactory"/><filter class="solr.WordDelimiterFilterFactory" generateWordParts="0" generateNumberParts="0" catenateWords="1" catenateNumbers="1" catenateAll="0"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.EnglishMinimalStemFilterFactory"/><!-- this filter can remove any duplicate tokens that appear at the same position - sometimespossible with WordDelimiterFilter in conjuncton with stemming. --><filter class="solr.RemoveDuplicatesTokenFilterFactory"/></analyzer></fieldType><!-- Just like text_general except it reverses the characters ofeach token, to enable more efficient leading wildcard queries. --><fieldType name="text_general_rev" class="solr.TextField" positionIncrementGap="100"><analyzer type="index"><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.ReversedWildcardFilterFactory" withOriginal="true"maxPosAsterisk="3" maxPosQuestion="2" maxFractionAsterisk="0.33"/></analyzer><analyzer type="query"><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/></analyzer></fieldType><!-- charFilter + WhitespaceTokenizer  --><!--<fieldType name="text_char_norm" class="solr.TextField" positionIncrementGap="100" ><analyzer><charFilter class="solr.MappingCharFilterFactory" mapping="mapping-ISOLatin1Accent.txt"/><tokenizer class="solr.WhitespaceTokenizerFactory"/></analyzer></fieldType>--><!-- This is an example of using the KeywordTokenizer alongWith various TokenFilterFactories to produce a sortable fieldthat does not include some properties of the source text--><fieldType name="alphaOnlySort" class="solr.TextField" sortMissingLast="true" omitNorms="true"><analyzer><!-- KeywordTokenizer does no actual tokenizing, so the entireinput string is preserved as a single token--><tokenizer class="solr.KeywordTokenizerFactory"/><!-- The LowerCase TokenFilter does what you expect, which can bewhen you want your sorting to be case insensitive--><filter class="solr.LowerCaseFilterFactory" /><!-- The TrimFilter removes any leading or trailing whitespace --><filter class="solr.TrimFilterFactory" /><!-- The PatternReplaceFilter gives you the flexibility to useJava Regular expression to replace any sequence of charactersmatching a pattern with an arbitrary replacement string, which may include back references to portions of the originalstring matched by the pattern.See the Java Regular Expression documentation for moreinformation on pattern and replacement string syntax.http://docs.oracle.com/javase/7/docs/api/java/util/regex/package-summary.html--><filter class="solr.PatternReplaceFilterFactory"pattern="([^a-z])" replacement="" replace="all"/></analyzer></fieldType><fieldType name="phonetic" stored="false" indexed="true" class="solr.TextField" ><analyzer><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.DoubleMetaphoneFilterFactory" inject="false"/></analyzer></fieldType><fieldType name="payloads" stored="false" indexed="true" class="solr.TextField" ><analyzer><tokenizer class="solr.WhitespaceTokenizerFactory"/><!--The DelimitedPayloadTokenFilter can put payloads on tokens... for example,a token of "foo|1.4"  would be indexed as "foo" with a payload of 1.4fAttributes of the DelimitedPayloadTokenFilterFactory : "delimiter" - a one character delimiter. Default is | (pipe)"encoder" - how to encode the following value into a playloadfloat -> org.apache.lucene.analysis.payloads.FloatEncoder,integer -> o.a.l.a.p.IntegerEncoderidentity -> o.a.l.a.p.IdentityEncoderFully Qualified class name implementing PayloadEncoder, Encoder must have a no arg constructor.--><filter class="solr.DelimitedPayloadTokenFilterFactory" encoder="float"/></analyzer></fieldType><!-- lowercases the entire field value, keeping it as a single token.  --><fieldType name="lowercase" class="solr.TextField" positionIncrementGap="100"><analyzer><tokenizer class="solr.KeywordTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory" /></analyzer></fieldType><!-- Example of using PathHierarchyTokenizerFactory at index time, soqueries for paths match documents at that path, or in descendent paths--><fieldType name="descendent_path" class="solr.TextField"><analyzer type="index"><tokenizer class="solr.PathHierarchyTokenizerFactory" delimiter="/" /></analyzer><analyzer type="query"><tokenizer class="solr.KeywordTokenizerFactory" /></analyzer></fieldType><!-- Example of using PathHierarchyTokenizerFactory at query time, soqueries for paths match documents at that path, or in ancestor paths--><fieldType name="ancestor_path" class="solr.TextField"><analyzer type="index"><tokenizer class="solr.KeywordTokenizerFactory" /></analyzer><analyzer type="query"><tokenizer class="solr.PathHierarchyTokenizerFactory" delimiter="/" /></analyzer></fieldType><!-- since fields of this type are by default not stored or indexed,any data added to them will be ignored outright.  --> <fieldType name="ignored" stored="false" indexed="false" multiValued="true" class="solr.StrField" /><!-- This point type indexes the coordinates as separate fields (subFields)If subFieldType is defined, it references a type, and a dynamic fielddefinition is created matching *___<typename>.  Alternately, if subFieldSuffix is defined, that is used to create the subFields.Example: if subFieldType="double", then the coordinates would beindexed in fields myloc_0___double,myloc_1___double.Example: if subFieldSuffix="_d" then the coordinates would be indexedin fields myloc_0_d,myloc_1_dThe subFields are an implementation detail of the fieldType, and endusers normally should not need to know about them.--><fieldType name="point" class="solr.PointType" dimension="2" subFieldSuffix="_d"/><!-- A specialized field for geospatial search. If indexed, this fieldType must not be multivalued. --><fieldType name="location" class="solr.LatLonType" subFieldSuffix="_coordinate"/><!-- An alternative geospatial field type new to Solr 4.  It supports multiValued and polygon shapes.For more information about this and other Spatial fields new to Solr 4, see:http://wiki.apache.org/solr/SolrAdaptersForLuceneSpatial4--><fieldType name="location_rpt" class="solr.SpatialRecursivePrefixTreeFieldType"geo="true" distErrPct="0.025" maxDistErr="0.001" distanceUnits="kilometers" /><!-- some examples for different languages (generally ordered by ISO code) --><!-- Arabic --><fieldType name="text_ar" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><!-- for any non-arabic --><filter class="solr.LowerCaseFilterFactory"/><!-- normalizes ﻯ to ﻱ, etc --><filter class="solr.ArabicNormalizationFilterFactory"/><filter class="solr.ArabicStemFilterFactory"/></analyzer></fieldType><!-- Bulgarian --><fieldType name="text_bg" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/> <filter class="solr.LowerCaseFilterFactory"/><filter class="solr.BulgarianStemFilterFactory"/></analyzer></fieldType><!-- Catalan --><fieldType name="text_ca" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Catalan"/></analyzer></fieldType><!-- CJK bigram (see text_ja for a Japanese configuration using morphological analysis) --><fieldType name="text_cjk" class="solr.TextField" positionIncrementGap="100"><analyzer><tokenizer class="solr.StandardTokenizerFactory"/><!-- normalize width before bigram, as e.g. half-width dakuten combine  --><filter class="solr.CJKWidthFilterFactory"/><!-- for any non-CJK --><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.CJKBigramFilterFactory"/></analyzer></fieldType><!-- Kurdish --><fieldType name="text_ckb" class="solr.TextField" positionIncrementGap="100"><analyzer><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.SoraniNormalizationFilterFactory"/><!-- for any latin text --><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SoraniStemFilterFactory"/></analyzer></fieldType><!-- Czech --><fieldType name="text_cz" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.CzechStemFilterFactory"/></analyzer></fieldType><!-- Danish --><fieldType name="text_da" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Danish"/></analyzer></fieldType><!-- German --><fieldType name="text_de" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.GermanNormalizationFilterFactory"/><filter class="solr.GermanLightStemFilterFactory"/><!-- less aggressive: <filter class="solr.GermanMinimalStemFilterFactory"/> --><!-- more aggressive: <filter class="solr.SnowballPorterFilterFactory" language="German2"/> --></analyzer></fieldType><!-- Greek --><fieldType name="text_el" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><!-- greek specific lowercase for sigma --><filter class="solr.GreekLowerCaseFilterFactory"/><filter class="solr.GreekStemFilterFactory"/></analyzer></fieldType><!-- Spanish --><fieldType name="text_es" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SpanishLightStemFilterFactory"/><!-- more aggressive: <filter class="solr.SnowballPorterFilterFactory" language="Spanish"/> --></analyzer></fieldType><!-- Basque --><fieldType name="text_eu" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Basque"/></analyzer></fieldType><!-- Persian --><fieldType name="text_fa" class="solr.TextField" positionIncrementGap="100"><analyzer><!-- for ZWNJ --><charFilter class="solr.PersianCharFilterFactory"/><tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.ArabicNormalizationFilterFactory"/><filter class="solr.PersianNormalizationFilterFactory"/></analyzer></fieldType><!-- Finnish --><fieldType name="text_fi" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Finnish"/><!-- less aggressive: <filter class="solr.FinnishLightStemFilterFactory"/> --></analyzer></fieldType><!-- French --><fieldType name="text_fr" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.FrenchLightStemFilterFactory"/><!-- less aggressive: <filter class="solr.FrenchMinimalStemFilterFactory"/> --><!-- more aggressive: <filter class="solr.SnowballPorterFilterFactory" language="French"/> --></analyzer></fieldType><!-- Irish --><fieldType name="text_ga" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.IrishLowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Irish"/></analyzer></fieldType><!-- Galician --><fieldType name="text_gl" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.GalicianStemFilterFactory"/><!-- less aggressive: <filter class="solr.GalicianMinimalStemFilterFactory"/> --></analyzer></fieldType><!-- Hindi --><fieldType name="text_hi" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><!-- normalizes unicode representation --><filter class="solr.IndicNormalizationFilterFactory"/><!-- normalizes variation in spelling --><filter class="solr.HindiNormalizationFilterFactory"/><filter class="solr.HindiStemFilterFactory"/></analyzer></fieldType><!-- Hungarian --><fieldType name="text_hu" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Hungarian"/><!-- less aggressive: <filter class="solr.HungarianLightStemFilterFactory"/> -->   </analyzer></fieldType><!-- Armenian --><fieldType name="text_hy" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Armenian"/></analyzer></fieldType><!-- Indonesian --><fieldType name="text_id" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><!-- for a less aggressive approach (only inflectional suffixes), set stemDerivational to false --><filter class="solr.IndonesianStemFilterFactory" stemDerivational="true"/></analyzer></fieldType><!-- Italian --><fieldType name="text_it" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.ItalianLightStemFilterFactory"/><!-- more aggressive: <filter class="solr.SnowballPorterFilterFactory" language="Italian"/> --></analyzer></fieldType><!-- Japanese using morphological analysis (see text_cjk for a configuration using bigramming)NOTE: If you want to optimize search for precision, use default operator AND in your queryparser config with <solrQueryParser defaultOperator="AND"/> further down in this file.  Use OR if you would like to optimize for recall (default).--><fieldType name="text_ja" class="solr.TextField" positionIncrementGap="100" autoGeneratePhraseQueries="false"><analyzer><!-- Kuromoji Japanese morphological analyzer/tokenizer (JapaneseTokenizer)Kuromoji has a search mode (default) that does segmentation useful for search.  A heuristicis used to segment compounds into its parts and the compound itself is kept as synonym.Valid values for attribute mode are:normal: regular segmentationsearch: segmentation useful for search with synonyms compounds (default)extended: same as search mode, but unigrams unknown words (experimental)For some applications it might be good to use search mode for indexing and normal mode forqueries to reduce recall and prevent parts of compounds from being matched and highlighted.Use <analyzer type="index"> and <analyzer type="query"> for this and mode normal in query.Kuromoji also has a convenient user dictionary feature that allows overriding the statisticalmodel with your own entries for segmentation, part-of-speech tags and readings without a needto specify weights.  Notice that user dictionaries have not been subject to extensive testing.User dictionary attributes are:userDictionary: user dictionary filenameuserDictionaryEncoding: user dictionary encoding (default is UTF-8)Punctuation characters are discarded by default.  Use discardPunctuation="false" to keep them.See http://wiki.apache.org/solr/JapaneseLanguageSupport for more on Japanese language support.--><tokenizer class="solr.JapaneseTokenizerFactory" mode="search"/><!-- Reduces inflected verbs and adjectives to their base/dictionary forms (辞書形) --><filter class="solr.JapaneseBaseFormFilterFactory"/><!-- Normalizes full-width romaji to half-width and half-width kana to full-width (Unicode NFKC subset) --><filter class="solr.CJKWidthFilterFactory"/><!-- Normalizes common katakana spelling variations by removing any last long sound character (U+30FC) --><filter class="solr.JapaneseKatakanaStemFilterFactory" minimumLength="4"/><!-- Lower-cases romaji characters --><filter class="solr.LowerCaseFilterFactory"/></analyzer></fieldType><!-- Latvian --><fieldType name="text_lv" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.LatvianStemFilterFactory"/></analyzer></fieldType><!-- Dutch --><fieldType name="text_nl" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Dutch"/></analyzer></fieldType><!-- Norwegian --><fieldType name="text_no" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Norwegian"/><!-- less aggressive: <filter class="solr.NorwegianLightStemFilterFactory" variant="nb"/> --><!-- singular/plural: <filter class="solr.NorwegianMinimalStemFilterFactory" variant="nb"/> --><!-- The "light" and "minimal" stemmers support variants: nb=Bokmål, nn=Nynorsk, no=Both --></analyzer></fieldType><!-- Portuguese --><fieldType name="text_pt" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.PortugueseLightStemFilterFactory"/><!-- less aggressive: <filter class="solr.PortugueseMinimalStemFilterFactory"/> --><!-- more aggressive: <filter class="solr.SnowballPorterFilterFactory" language="Portuguese"/> --><!-- most aggressive: <filter class="solr.PortugueseStemFilterFactory"/> --></analyzer></fieldType><!-- Romanian --><fieldType name="text_ro" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Romanian"/></analyzer></fieldType><!-- Russian --><fieldType name="text_ru" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Russian"/><!-- less aggressive: <filter class="solr.RussianLightStemFilterFactory"/> --></analyzer></fieldType><!-- Swedish --><fieldType name="text_sv" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Swedish"/><!-- less aggressive: <filter class="solr.SwedishLightStemFilterFactory"/> --></analyzer></fieldType><!-- Thai --><fieldType name="text_th" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.LowerCaseFilterFactory"/><filter class="solr.ThaiWordFilterFactory"/></analyzer></fieldType><!-- Turkish --><fieldType name="text_tr" class="solr.TextField" positionIncrementGap="100"><analyzer> <tokenizer class="solr.StandardTokenizerFactory"/><filter class="solr.ApostropheFilterFactory"/><filter class="solr.TurkishLowerCaseFilterFactory"/><filter class="solr.SnowballPorterFilterFactory" language="Turkish"/></analyzer></fieldType><!-- Similarity is the scoring routine for each document vs. a query.A custom Similarity or SimilarityFactory may be specified here, but the default is fine for most applications.  For more info: http://wiki.apache.org/solr/SchemaXml#Similarity--><!--<similarity class="com.example.solr.CustomSimilarityFactory"><str name="paramkey">param value</str></similarity>--></schema>

配置文件中主要用到BinFiledataSource 数据源，BinFiledataSource 用来获取文件的一些基础属性，包括文件大小 名称等,它的文档实例叫做“files”，因为不是给它做索引，所以需要设置rootEntity=”false”,实例中用到的几个属性如下：

1.fileAbsolutePath: 文档的唯一索引
2.fileSize: 文档的大小
3.fileLastModified: 文档的最后修改时间

接下来使用TikaEntityProcessor处理器来分析文档中的内容，并做索引，用到的几个属性如下：

1.file:文件名称，与上面写的fileAbsolutePath不同
2.Autor、Title:都是文档的meta属性
3.text:文档的文本内容