Mailing-List: contact solr-commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 13 Apr 2010 14:15:13 -0000
Message-ID: <20100413141513.4828.26866@eos.apache.org>
Subject: 
 =?utf-8?q?=5BSolr_Wiki=5D_Update_of_=22SolrTerminology=22_by_RobertMuir?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for chan=
ge notification.

The "SolrTerminology" page has been changed by RobertMuir.
The comment on this change is: update trunk location.
http://wiki.apache.org/solr/SolrTerminology?action=3Ddiff&rev1=3D13&rev2=3D=
14

--------------------------------------------------

   * '''''Shard''''': A distributed index is partitioned into "shards". Eac=
h 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 token=
s 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 perspect=
ive: Solr initially only supported one index, and the !SolrCore class was a=
 singleton for coordinating the low-level functionality at the "core" of So=
lr.  When support was added for [[CoreAdmin|creating and managing multiple =
Cores]] on the fly, the class was refactored to no longer be a Singleton, b=
ut the name stuck.
-  * '''''Solr Home Dir''''': Also referred to as the "'''''Solr Home Direc=
tory'''''" or just "'''''Solr Home'''''" this is the main directory where S=
olr will look for configuration files, data, and plugins.  Knowing which di=
rectory to use as the Solr Home is the one piece of information that Solr m=
ust either assume (the default is "./solr") or be configured using some mec=
hanism beyond Solr's normal configuration files.  An [[http://svn.apache.or=
g/repos/asf/lucene/solr/trunk/example/solr/|example Solr Home]] is included=
 in Solr releases and contains a [[http://svn.apache.org/repos/asf/lucene/s=
olr/trunk/example/solr/README.txt|README.txt]] explaining the directory str=
ucture.  For more information on ways to override the default Solr Home, pl=
ease read SolrInstall.
+  * '''''Solr Home Dir''''': Also referred to as the "'''''Solr Home Direc=
tory'''''" or just "'''''Solr Home'''''" this is the main directory where S=
olr will look for configuration files, data, and plugins.  Knowing which di=
rectory to use as the Solr Home is the one piece of information that Solr m=
ust either assume (the default is "./solr") or be configured using some mec=
hanism beyond Solr's normal configuration files.  An [[http://svn.apache.or=
g/repos/asf/lucene/dev/trunk/solr/example/solr/|example Solr Home]] is incl=
uded in Solr releases and contains a [[http://svn.apache.org/repos/asf/luce=
ne/dev/trunk/solr/example/solr/README.txt|README.txt]] explaining the direc=
tory structure.  For more information on ways to override the default Solr =
Home, please read SolrInstall.
   * '''''Static warming''''': What users can do using newSearcher and firs=
tSearcher event listeners to force explicit warming actions to be taken whe=
n one of these events happens -- frequently it involves seeding one or more=
 caches with values from "static" queries hard coded in the solrconfig.xml
  =

  =20