Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The "SolrTerminology" page has been changed by domtheo: http://wiki.apache.org/solr/SolrTerminology?action=diff&rev1=17&rev2=18 This is the place to define terms that are specific to Solr or that have meanings in the Solr community that differ from their meanings in the general populace. When adding to this page, please list terms in alphabetical order. + - [[http://www.propertykita.com/rumah.html|Rumah Dijual]] + - [[http://www.pintuvariasi.com|Pintu Aluminium]] + - [[http://vamostech.com/gps-tracking|GPS Tracker]] * '''''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 - * '''''Constraint''''': A viable method of limiting a set of objects ([[http://www.nabble.com/What-is-facet--tf4524494.html|*]]) + * '''''Constraint''''': A viable method of limiting a set of objects * '''''Core''''': See Solr Core below. * '''''DisMax''''': Typically a reference to the [[DisMaxQParserPlugin]] but in older contexts may be referring to the DisMaxRequestHandler. - * '''''Facet''''': A distinct feature or aspect of a set of objects; "a way in which a resource can be classified" ([[http://www.nabble.com/What-is-facet--tf4524494.html|*]]) + * '''''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 [[FieldCollapsing|Result Grouping]] where the groups are dictated by the value of a field. * '''''Filter''''': depending on context, may be: 1. Another word for "Constraint" @@ -21, +24 @@ * '''''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. * '''''Slop''''': As in "phrase slop": the number of positions two tokens need to be moved in order to match a phrase in a query. * '''''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 [[CoreAdmin|creating and managing multiple Cores]] on the fly, the class was refactored to no longer be a Singleton, but the name stuck. - * '''''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 [[http://svn.apache.org/repos/asf/lucene/dev/trunk/solr/example/solr/|example Solr Home]] is included in Solr releases and contains a [[http://svn.apache.org/repos/asf/lucene/dev/trunk/solr/example/solr/README.txt|README.txt]] explaining the directory structure. For more information on ways to override the default Solr Home, please read SolrInstall. + * '''''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 is included in Solr releases and contains a explaining the directory structure. For more information on ways to override the default Solr Home, please read SolrInstall. * '''''Static warming''''': What users can do using newSearcher and firstSearcher event listeners to force explicit 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
