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).
Hi Parvesh,
Please see the similar discussion : http://search-lucene.com/m/eHNlijx91I7etm1
Ahmet
On Thursday, March 10, 2016 6:57 AM, Parvesh Garg 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
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
wrote:
> Hello, you can not change similarities per request, and this is likely
> never going to be
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
> Sent: Tuesday 8th March 2
