Hi Ahmet, Thanks for the pointer. I have similar thoughts on the subject. The risk assumptions are based on not testing your stuff before taking it in. That risk is still valid with similarity configuration. And sometimes, it may not be possible to use multiple similarities (custom or otherwise). But overall, it seems like a nice feature to have.
Parvesh Garg, Head of Engineering http://www.zettata.com On Thu, Mar 10, 2016 at 3:05 PM, Ahmet Arslan <iori...@yahoo.com.invalid> wrote: > Hi Parvesh, > > Please see the similar discussion : > http://search-lucene.com/m/eHNlijx91I7etm1 > > Ahmet > > > On Thursday, March 10, 2016 6:57 AM, Parvesh Garg <parv...@zettata.com> > wrote: > > > > Thanks Markus. We will look at other options. May I ask what can be the > reasons for not supporting this ever? > > > Parvesh Garg, > > http://www.zettata.com > > > On Tue, Mar 8, 2016 at 8:59 PM, Markus Jelsma <markus.jel...@openindex.io> > wrote: > > > Hello, you can not change similarities per request, and this is likely > > never going to be supported for good reasons. You need multiple cores, or > > multiple fields with different similarity defined in the same core. > > Markus > > > > -----Original message----- > > > From:Parvesh Garg <parv...@zettata.com> > > > Sent: Tuesday 8th March 2016 5:36 > > > To: solr-user@lucene.apache.org > > > Subject: Multiple custom Similarity implementations > > > > > > Hi, > > > > > > We have a requirement where we want to run an A/B test over multiple > > > Similarity implementations. Is it possible to define multiple > similarity > > > tags in schema.xml file and chose one using the URL parameter? We are > > using > > > solr 4.7 > > > > > > Currently, we are planning to have different cores with different > > > similarity configured and split traffic based on core names. This is > > > leading to index duplication and un-necessary resource usage. > > > > > > Any help is highly appreciated. > > > > > > Parvesh Garg, > > > > > > http://www.zettata.com > > > > > >
