lucene-java-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-java Wiki] Update of "LuceneCaveats" by RenaudWaldura
Date Fri, 29 Jun 2007 22:03:50 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" for change notification.

The following page has been changed by RenaudWaldura:
http://wiki.apache.org/lucene-java/LuceneCaveats

The comment on the change is:
fixed links at last

------------------------------------------------------------------------------
  to generate the proper queries. 
  
  Dissimilar or incompatible analyzers lead to mysterious search
- behavior. See: LuceneFAQ, "Why am I getting no hits / incorrect hits?".
+ behavior. See: ["LuceneFAQ"], "Why am I getting no hits / incorrect hits?".
  
  === Large documents are truncated by default ===
  
@@ -54, +54 @@

  You should keep the index open as long as possible. Both 
  [http://lucene.apache.org/java/docs/api/org/apache/lucene/index/IndexReader.html IndexReader]
  and
- [http://lucene.apache.org/java/docs/api/org/apache/lucene/index/IndexSearcher.html IndexSearcher]
+ [http://lucene.apache.org/java/docs/api/org/apache/lucene/search/IndexSearcher.html IndexSearcher]
  are thread-safe and don't require additional
  synchronization. One could cache the index searcher e.g. in the application 
  context. 
  
- See also: LuceneFAQ, "Is the IndexSearcher thread-safe?".
+ See also: ["LuceneFAQ"], "Is the IndexSearcher thread-safe?".
  
  === No need to cache search results ===
  
@@ -67, +67 @@

  and paging through them, merely re-executing the query is almost always 
  fast enough. 
  
- See: LuceneFAQ, "How do I implement paging, i.e. showing result from 1-10, 11-20 etc?".
+ See: ["LuceneFAQ"], "How do I implement paging, i.e. showing result from 1-10, 11-20 etc?".
  
  When doing sub-searches (searching the results of a previous search),
  it's easier (and fast enough) to add the first query as a conditional
  to the second. 
  
- But if you really need to do this, see: LuceneFAQ, "Can I cache search results with Lucene?".

+ But if you really need to do this, see: ["LuceneFAQ"], "Can I cache search results with
Lucene?". 
- See also: LuceneFAQ, "Can Lucene do a "search within search", so that the second search
is constrained by the results of the first query?".
+ See also: ["LuceneFAQ"], "Can Lucene do a "search within search", so that the second search
is constrained by the results of the first query?".
  
  
  === Use RangeFilter instead of RangeQuery ===
@@ -85, +85 @@

  
  [http://lucene.apache.org/java/docs/api/org/apache/lucene/search/RangeFilter.html RangeFilter]
doesn't suffer from this limitation.
  
- See: LuceneFAQ, "Why am I getting a TooManyClauses exception?".
+ See: ["LuceneFAQ"], "Why am I getting a TooManyClauses exception?".
  
  == Querying ==
  
@@ -117, +117 @@

  === Iterating over all hits takes a long time ===
  
  This is by design. Try using a 
- [http://lucene.apache.org/java/docs/api/org/apache/lucene/search/HitsCollector.html HitsCollector]
+ [http://lucene.apache.org/java/docs/api/org/apache/lucene/search/HitCollector.html HitCollector]
  instead if you need access to
  all the hits for a search.
  
@@ -126, +126 @@

  The Lucene-contributed highlighter does the best it can, but it doesn't have 
  the information it really needs to correctly highlight the search results.
  
- See: LuceneFAQ, "Is there a way to get a text summary of an indexed document with Lucene
(a.k.a. a "snippet" or "fragment") to display along with the search result?".
+ See: ["LuceneFAQ"], "Is there a way to get a text summary of an indexed document with Lucene
(a.k.a. a "snippet" or "fragment") to display along with the search result?".
  

Mime
View raw message