Giving OpenSearcher as false

[Prasi S <pr...@gmail.com>]

Hi,
1. What is the impact , use of giving opensearcher as true

 <autoCommit>
       <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
       <openSearcher>true</openSearcher>

2. Giving the value as "false" , does this create index in the temp file
and then commit?


Regards,
Prasi

Re: Giving OpenSearcher as false

[Shalin Shekhar Mangar <sh...@gmail.com>]

Comments inline:

On Mon, Aug 19, 2013 at 12:20 PM, Prasi S <pr...@gmail.com> wrote:
> Hi,
> 1. What is the impact , use of giving opensearcher as true
>
>  <autoCommit>
>        <maxTime>${solr.autoCommit.maxTime:15000}</maxTime>
>        <openSearcher>true</openSearcher>
>

>From the Solr reference guide:

"Whether to open a new searcher when performing a commit. If this is
false, the default, the commit will flush recent index changes to
stable storage, but does not cause a new searcher to be opened to make
those changes visible"

https://cwiki.apache.org/confluence/display/solr/UpdateHandlers+in+SolrConfig

If openSearcher is true, then all your updates until the commit are
made visible to searchers.

> 2. Giving the value as "false" , does this create index in the temp file
> and then commit?
>

Nope, the new index segments are still written to the index directory
however, the new segments are not used for searches. Your clients will
not see any changes to the index until a commit with openSearcher=true
is invoked.

>
> Regards,
> Prasi



-- 
Regards,
Shalin Shekhar Mangar.