There are now two excellent books: "Lucene In Action 2" and "Solr 1.4 Enterprise Search Server" the describe the inners workings of these technologies and how they fit together.
Otherwise Solr and Lucene knowledge are only available in a fragmented form across many wiki pages, bug reports and email discussions. But the direct answer is: before you commit your changes you will not seem them in queries. When you commit them, all caches are thrown away and rebuilt when you do the same queries you did before. This rebuilding process has various tools to control it in solrconfig.xml. On Wed, Sep 23, 2009 at 8:27 PM, satya <tosatyaj...@gmail.com> wrote: > Is there any way to analyze or see that which documents are getting cached > by documentCache - > > <documentCache > class="solr.LRUCache" > size="512" > initialSize="512" > autowarmCount="0"/> > > > > On Wed, Sep 23, 2009 at 8:10 AM, satya <tosatyaj...@gmail.com> wrote: > >> First of all , thanks a lot for the clarification.Is there any way to see, >> how this cache is working internally and what are the objects being stored >> and how much memory its consuming,so that we can get a clear picture in >> mind.And how to test the performance through cache. >> >> >> On Tue, Sep 22, 2009 at 11:19 PM, Fuad Efendi <f...@efendi.ca> wrote: >> >>> > 1)Then do you mean , if we delete a perticular doc ,then that is going >>> to >>> be >>> > deleted from >>> > cache also. >>> >>> When you delete document, and then COMMIT your changes, new caches will be >>> warmed up (and prepopulated by some key-value pairs from old instances), >>> etc: >>> >>> <!-- documentCache caches Lucene Document objects (the stored fields for >>> each document). >>> Since Lucene internal document ids are transient, this cache will >>> not >>> be autowarmed. --> >>> <documentCache >>> class="solr.LRUCache" >>> size="512" >>> initialSize="512" >>> autowarmCount="0"/> >>> >>> - this one won't be 'prepopulated'. >>> >>> >>> >>> >>> > 2)In solr,is cache storing the entire document in memory or only the >>> > references to >>> > documents in memory. >>> >>> There are many different cache instances, DocumentCache should store <ID, >>> Document> pairs, etc.... >>> >>> >>> >> > -- Lance Norskog goks...@gmail.com
