Just had a glance at the IndexSearcher code. Changing the similarity would not cause any failures. However the change may not be immediately seen by all threads because the variable is non-volatile (I'm open to correction on that...).
If you need multiple threads to have different Similarity implementations then you will need separate IndexSearcher instances. You can use a single IndexReader for the IndexSearchers Barry On Mon, Jan 5, 2015 at 1:10 PM, Ahmet Arslan <iori...@yahoo.com.invalid> wrote: > > > anyone? > > > > On Thursday, December 25, 2014 4:42 PM, Ahmet Arslan > <iori...@yahoo.com.INVALID> wrote: > Hi all, > > Javadocs says "IndexSearcher instances are completely thread safe, meaning > multiple threads can call any of its > methods, concurrently" > > Is this true for setSimilarity() method? > > What happens when every thread uses different similarity implementations? > > Thanks, > Ahmet > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
