Re: Proximity searching in percentage

2015-05-08 Thread Zheng Lin Edwin Yeo
Hi Alessandro, Thank you so much for the info. Will try that out. Regards, Edwin On 8 May 2015 17:27, "Alessandro Benedetti" wrote: > 2015-05-08 10:14 GMT+01:00 Zheng Lin Edwin Yeo : > > > Hi Alessandro, > > > > I'm using Solr 5.0.0, but it is still able to work. Actually I found this > > to be

Re: Proximity searching in percentage

2015-05-08 Thread Alessandro Benedetti
2015-05-08 10:14 GMT+01:00 Zheng Lin Edwin Yeo : > Hi Alessandro, > > I'm using Solr 5.0.0, but it is still able to work. Actually I found this > to be better than ~1 or ~2, as it can automatically detect > and allow the 20% error rate that I want. > I don't think that the "double" param is suppor

Re: Proximity searching in percentage

2015-05-08 Thread Zheng Lin Edwin Yeo
Hi Alessandro, I'm using Solr 5.0.0, but it is still able to work. Actually I found this to be better than ~1 or ~2, as it can automatically detect and allow the 20% error rate that I want. For this ~1 or ~2, does it mean that I'll have to manually detect how many characters did I enter, before I

Re: Proximity searching in percentage

2015-05-08 Thread Alessandro Benedetti
Hi Zheng, actually that version of the fuzzy search is deprecated! Currently the fuzzy search syntax is : ~1 or ~2 The ~(tilde) param is the number of edit we provide to generate all the expanded query to run. Can I ask you which version of Solr are you using ? This article from 2011 shows the bi

Re: Proximity searching in percentage

2015-05-07 Thread Zheng Lin Edwin Yeo
Thank you for the information. I've currently using the fuzzy search and set the edit distance value to ~0.79, and this has allowed a 20% error rate. (ie for words with 5 characters, it allows 1 mis-spelled character, and for words with 10 characters, it allows 2 mis-speed characters). However, f

Re: Proximity searching in percentage

2015-05-07 Thread Alessandro Benedetti
Hi ! Currently Solr builds FST to provide proper fuzzy search or spellcheck suggestions based on the string distance . The current default algorithm is the Levenstein distance ( that returns the number of edit as distance metric). In your case you should calculate client side, the edit you want to

Proximity searching in percentage

2015-05-05 Thread Zheng Lin Edwin Yeo
Hi, Would like to check, how do we implement character proximity searching that's in terms of percentage with regards to the length of the word, instead of a fixed number of edit distance (characters)? For example, if we have a proximity of 20%, a word with 5 characters will have an edit distance