That's under the covers implementation. Unless you are doing extensions, you probably don't need to worry.
Where it connects to the userland is - for example - the commits. Until you commit, your records are not visible. Even though Solr already has them. This is because the 'index searcher' does not see new items. When commit is done, a searcher is closed/reopened and you see those changes. Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Fri, Mar 7, 2014 at 2:04 PM, search engn dev <sachinyadav0...@gmail.com> wrote: > I am reading apache solr reference guide and it has lines as below > > "..... Solr caches are associated with a specific instance of an Index > Searcher, a specific view of an index that doesn't change during the > lifetime of that > searcher. As long as that Index Searcher is being used, any items in its > cache will be valid and available for reuse...." > > What is the concept of index searcher. ? basically what is mean by index > searcher here? is it user or something else.? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/What-is-mean-by-Index-Searcher-tp4121898.html > Sent from the Solr - User mailing list archive at Nabble.com.
