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 ma...@apache.org on 2009/08/19 16:22:03 UTC
svn commit: r805815 - /lucene/java/trunk/CHANGES.txt
Author: markrmiller
Date: Wed Aug 19 14:22:03 2009
New Revision: 805815
URL: http://svn.apache.org/viewvc?rev=805815&view=rev
Log:
add a runtime changes entry for 1483
Modified:
lucene/java/trunk/CHANGES.txt
Modified: lucene/java/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/lucene/java/trunk/CHANGES.txt?rev=805815&r1=805814&r2=805815&view=diff
==============================================================================
--- lucene/java/trunk/CHANGES.txt (original)
+++ lucene/java/trunk/CHANGES.txt Wed Aug 19 14:22:03 2009
@@ -187,6 +187,15 @@
AttributeSource.clearAttributes() to work identical for Token as one for all
AttributeImpl and the 6 separate AttributeImpls. (Uwe Schindler, Michael Busch)
+13. LUCENE-1483: When searching over multiple segments, a new Scorer is now created
+ for each segment. The Weight is created only once for the top level Searcher.
+ Each Scorer is passed the per-segment IndexReader. This will result in docids
+ in the Scorer being internal to the per-segment IndexReader. If a custom Scorer
+ implementation uses any caches/filters that rely on being based on the top level
+ IndexReader, it will need to be updated to use caches/filters on a per segment
+ basis. There is currently no way provided to rebase the docids in the Scorer to
+ the top level IndexReader. (Mark Miller, Mike McCandless)
+
API Changes
1. LUCENE-1419: Add expert API to set custom indexing chain. This API is