lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta Lucene Wiki] Updated: LuceneFAQ
Date Wed, 16 Feb 2005 10:29:00 GMT
   Date: 2005-02-16T02:29:00
   Editor: LucVanlerberghe
   Wiki: Jakarta Lucene Wiki
   Page: LuceneFAQ

   Added warning about handling untokenized fields in Analyzers

Change Log:

@@ -373,6 +373,8 @@
 '''NOTE:''' It's not a rule that the same analyzer be used for both indexing and searching,
and there are cases where it makes sense to use different ones (ie: when dealing with Synonyms).
 The analyzers must be compatible though.
+Also be careful with Fields that are not tokenized (like Keywords). During indexation, the
Analyzer won't be called for these fields, but for a search, the !QueryParser can't know this
and will pass all search strings through the selected Analyzer.  Usually searches for Keywords
are constructed in code, but during development it can be handy to use general purpose tools
(e.g. Luke) to examine your index.  Those tools won't know which fields are tokenized either.
 In the contrib/analyzers area there's a !KeywordTokenizer with an example !KeywordAnalyzer
for cases like this.
 ==== What is index optimization and when should I use it? ====
 The !IndexWriter class supports an optimize() method that compacts the index database and
speedup queries. You may want to use this method after performing a complete indexing of your
document set or after incremental updates of the index. If your incremental update adds documents
frequently, you want to perform the optimization only once in a while to avoid the extra overhead
of the optimization.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message