Each request thread may return updated results. Each component may also
in certain cases return updated results. The algorithm is designed to
handle these. The granularity of the returned results can be controlled
through a visible parameter.
Regards,
Nagendra Nagarajayya
http://solr-ra.tgels.org
http://rankingalgorithm.tgels.org
On 7/24/2012 5:36 AM, Yonik Seeley wrote:
On Tue, Jul 24, 2012 at 8:24 AM, Nagendra Nagarajayya
<nnagaraja...@transaxtions.com> wrote:
SolrIndexSearcher is a heavy object with caches, etc.
As I've said, the caches are configurable, and it's trivial to disable
all caching (to the point where the cache objects are not even
created).
The reader member is not replaced in the existing SolrIndexSearcher object.
The IndexSearcher.getIndexReader() method has been overriden in
SolrIndexSearcher and all direct reader member access has been replaced with
a getIndexReader() method call allowing a NRT reader to be supplied when
realtime is enabled.
In a single Solr request (that runs through multiple components like
query, highlight, facet, and response writing),
does IndexSearcher.getIndexReader() always return the same reader? If
not, this breaks pretty much every standard solr component - but it
will only be apparent under load, and if you are carefully sanity
checking the results.
-Yonik
http://lucidimagination.com
