You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-commits@lucene.apache.org by mi...@apache.org on 2008/12/04 18:13:41 UTC

svn commit: r723375 - /lucene/java/trunk/CHANGES.txt

Author: mikemccand
Date: Thu Dec  4 09:13:40 2008
New Revision: 723375

URL: http://svn.apache.org/viewvc?rev=723375&view=rev
Log:
LUCENE-1461: fix single term per document -> single term for a given field

Modified:
    lucene/java/trunk/CHANGES.txt

Modified: lucene/java/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/java/trunk/CHANGES.txt?rev=723375&r1=723374&r2=723375&view=diff
==============================================================================
--- lucene/java/trunk/CHANGES.txt (original)
+++ lucene/java/trunk/CHANGES.txt Thu Dec  4 09:13:40 2008
@@ -98,12 +98,12 @@
 
  7. LUCENE-1461: Added FieldCacheRangeFilter, a RangeFilter for
     single-term fields that uses FieldCache to compute the filter.  If
-    your field has a single term per document, and you need to create
-    many RangeFilters with varying lower/upper bounds, then this is
-    likely a much faster way to create the filters than RangeFilter.
-    However, it comes at the expense of added RAM consumption and
-    slower first-time usage due to populating the FieldCache.  (Tim
-    Sturge via Mike McCandless)
+    your documents all have a single term for a given field, and you
+    need to create many RangeFilters with varying lower/upper bounds,
+    then this is likely a much faster way to create the filters than
+    RangeFilter.  However, it comes at the expense of added RAM
+    consumption and slower first-time usage due to populating the
+    FieldCache.  (Tim Sturge via Mike McCandless)
 
  8. LUCENE-1296: add protected method CachingWrapperFilter.docIdSetToCache 
     to allow subclasses to choose which DocIdSet implementation to use