1483 - indexsearcher pulls out a readers subreaders (segmentreaders)
and sends a collector over them one by one, rather than using the
multireader. So only fc for seg readers that change need to be reloaded.
- Mark
http://www.lucidimagination.com (mobile)
On Sep 22, 2009, at 1:27 AM, John Wang <john.w...@gmail.com> wrote:
Hi Yonik:
Actually that is what I am looking for. Can you please point me
to where/how sorting is done per-segment?
When heaving indexing introduces or modifies segments, would it
cause reloading of FieldCache at query time and thus would impact
search performance?
thanks
-John
On Tue, Sep 22, 2009 at 1:05 PM, Yonik Seeley <yo...@lucidimagination.com
> wrote:
On Tue, Sep 22, 2009 at 12:56 AM, John Wang <john.w...@gmail.com>
wrote:
> Looking at the code, seems there is a disconnect between how/when
field
> cache is loaded when IndexWriter.getReader() is called.
I'm not sure what you mean by "disconnect"
> Is FieldCache updated?
FieldCache entries are populated on demand, as they always have been.
> Otherwise, are we reloading FieldCache for each
> reader instance?
Searching/sorting is now per-segment, and so is the use of the
FieldCache. Segments that don't change shouldn't have to reload their
FieldCache entries.
-Yonik
http://www.lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
