Hi Barry, Thanks for chiming in. Then javadocs needs correction, right?
"multiple threads can call any of its methods, concurrently" Ahmet On Monday, January 5, 2015 3:28 PM, Barry Coughlan <[email protected]> wrote: 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 <[email protected]> wrote: > > > anyone? > > > > On Thursday, December 25, 2014 4:42 PM, Ahmet Arslan > <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
