SolrTerminology_术语

This is the place to define terms that are specific to Solr or that havemeanings in the Solr community that differ from their meanings in the generalpopulace.

这里定义Solr中特定的或者在Solr社区中有不同于通常意义的术语。

When adding to this page, please list terms in alphabetical order.

加入到这个页面时，请将术语按字母顺序列出。

• Auto-warming: What Solr does when it opens a new cache, and seeds it with key/val pairs based on the "top" keys from the old instance of the cache 当Solr打开一个新的缓存时，基于旧实例缓存中顶层键编排它的键值对。
• Constraint: A viable method of limiting a set of objects (*) 限制一组对象的可行方法。
• Core: See Solr Core below. 请查看下面的Solr Core。
• DisMax: Typically a reference to the DisMaxQParserPlugin but in older contexts may be referring to the DisMaxRequestHandler. 通常指的是DisMaxQParserPlugin，但是在老的上下文中可能指的是DisMaxRequestHandler。
• Facet: A distinct feature or aspect of a set of objects; "a way in which a resource can be classified" (*) 一组对象的独特特征或外貌；“可以分类资源的方式”
• Field Collapsing: A specific use case of Result Grouping where the groups are dictated by the value of a field. 可以通过字段值描述的Result Grouping的特殊使用案例
• Filter: depending on context, may be: 依赖于上下文，可能
  1. Another word for "Constraint" 约束的另外一种称谓。
  2. The "fq" param which constrains the results from a query without influencing the scores. “fq”参数，限制查询结果，对scores没有影响。
  3. Specifically referring to the Lucene "Filter" class 特指Lucene “Filter”类
• NRT: Near Real Time: This refers to the general concept of wanting document updates to be "immediately" visible to search clients. 近实时：这里指的是希望文档更新后对搜索客户端及时可见的一般概念。
• Request Handler: A Solr component that processes requests. For example, the DisMaxRequestHandler processes search queries by calling the DisMax Query Parser. Request Handlers can perform other functions, as well. 处理请求的Solr组件。例如，DisMaxRequestHandler通过DisMax Query Parser处理搜索查询。Request Handlers也可以完成其他功能。
• QTime: The elapsed time (in milliseconds) between the arrival of the request (when the SolrQueryRequest object is created) and the completion of the request handler. It does not include time spent in the response writer formatting/streaming the response to the client. 请求到达（当SolrQueryRequestd对象创建）到请求处理器完成的运行时间（毫秒级）。不包括响应写入器格式化/streaming 相应到客户端的时间。
• Query Parser: A Solr component that parses the parameters and search terms submitted in a search query.分析搜索查询提交的参数和搜索词的Solr组件。
• Searcher: In Solr parlance, the term "Searcher" tends to refer to an instance of the SolrIndexSearcher class. This class is responsible for executing all searches done against the index, and manages several caches. There is typically one Searcher per SolrCore at any given time, and that searcher is used to execute all queries against that SolrCore, but there may be additional Searchers open at a time during cache warming (in which and "old Searcher" is still serving live requests while a "new Searcher" is being warmed up). 在Solr的说法中，“Searcher”这个词常常指的是SolrIndexSearcher类的实例。这个类负责对索引执行搜索，并且管理一些缓存。通常每个SolrCore在任意给定时间都有一个Searcher，并且这个Searcher用来执行SolrCore上的所有查询，但是可能有附加的Searcher在缓存warming期间打开（当一个“新的Searcher”warmed up时“旧的Searcher”仍然为活动的请求服务）。
• Shard: A distributed index is partitioned into "shards". Each shard corresponds to a Lucene instance and contains a disjoint subset of the documents in the index. 一个分布式的索引被分割成“shards”。每一个shard相当于一个Lucene实例并且包含索引中文档的不相交子集。
• Slop: As in "phrase slop": the number of positions two tokens need to be moved in order to match a phrase in a query. 像“phrase slop”：定位两个令牌的数量需要移动，以在查询匹配短语。
• Solr Core: Also referred to as just a "Core". This is a running instance of a Solr index along with all of its configuration (SolrConfigXml, SchemaXml, etc...). A single Solr application can contain 0 or more cores which are run largely in isolation but can communicate with each other if necessary via the CoreContainer. From a historical perspective: Solr initially only supported one index, and the SolrCore class was a singleton for coordinating the low-level functionality at the "core" of Solr. When support was added for creating and managing multiple Cores on the fly, the class was refactored to no longer be a Singleton, but the name stuck. 也被称为一个“Core”。是一个连同Solr索引和所有的配置文件的正在运行的实例(SolrConfigXml, SchemaXml, etc...)。单一的Solr应用包含0或者更多大量独立运行但是可以在必要时经由CoreContainer沟通的核心。从历史角度：Solr最初只支持一个索引，SolrCore类是单实例在Solr的“core”协调底层功能。当很快加入对创建和管理多核的支持，这个类被重构了，不再是单实例，但是名字没有变。
• Solr Home Dir: Also referred to as the "Solr Home Directory" or just "Solr Home" this is the main directory where Solr will look for configuration files, data, and plugins. Knowing which directory to use as the Solr Home is the one piece of information that Solr must either assume (the default is "./solr") or be configured using some mechanism beyond Solr's normal configuration files. An example Solr Home is included in Solr releases and contains a README.txt explaining the directory structure. For more information on ways to override the default Solr Home, please read SolrInstall. 也被称作是“Solr Home Directory”或者只叫“Solr Home”，这是Solr查找配置文件，数据和插件的主要目录。知道使用哪个目录作为Solr Home是其中的一个信息，Solr必须假定（默认是"./solr"）或者被配置使用一些超出Solr的标准配置文件的途径。Solr releases中的Solr Home例子包含解释目录结构的Readme.txt。获取更多重写默认Solr Home的信息，请阅读SolrInstall。

Static warming: Whatusers can do using newSearcher and firstSearcher event listeners to forceexplicit warming actions to be taken when one of these events happens --frequently it involves seeding one or more caches with values from"static" queries hard coded in the solrconfig.xml