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: Mon, 05 Oct 2009 17:29:49 -0000
Message-ID: <20091005172949.11445.32336@eos.apache.org>
Subject: 
 =?utf-8?q?=5BSolr_Wiki=5D_Update_of_=22AnalyzersTokenizersTokenFilters=22?=
 =?utf-8?q?_by_ChristianZambrano?=

Dear Wiki user,

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

The "AnalyzersTokenizersTokenFilters" page has been changed by ChristianZam=
brano:
http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters?action=3Ddiff&r=
ev1=3D60&rev2=3D61

  =3D=3D Analyzers =3D=3D
  =

  Analyzers are components that pre-process input text at index time and/or=
 at  search time.  It's important to use the same or similar analyzers that=
 process text in a compatible manner at index and query time.  For example,=
 if an indexing analyzer lowercases words, then the query analyzer should d=
o the same to enable finding the indexed words.
+ =

+ On wildcard and fuzzy searches, no text analysis is performed on the sear=
ch word.
  =

  The Analyzer class is an abstract class, but Lucene comes with a few conc=
rete Analyzers that pre-process their input in different ways. If you need =
to pre-process input text and queries in a way that is not provided by any =
of Lucene's built-in Analyzers, you will need to specify a custom Analyzer =
in the Solr schema.
 =20