I know your issue has already been addressed but you may want to consider
"gran" being a synonym for "grand" and then analyzing it as such.
~ David Smiley
Marcus Stratmann wrote:
>
> Hello,
>
> I have another question concerning the spell checking mechanism.
> Setting onlyMorePopular=true and
Shalin Shekhar Mangar wrote:
The implementation is a bit more complicated.
1. Read all tokens from the specified field in the solr index.
2. Create n-grams of the terms read in #1 and index them into a separate
Lucene index (spellcheck index).
3. When asked for suggestions, create n-grams of the
On Sun, Feb 15, 2009 at 10:00 PM, Mark Miller wrote:
> But if we make it past that line (onlyMorePopular=true), later there is:
>
> // don't suggest a word for itself, that would be silly
> if (sugWord.string.equals(word)) {
> continue;
> }
>
> So you end up only getting all of
Shalin Shekhar Mangar wrote:
On Sun, Feb 15, 2009 at 8:56 AM, Mark Miller wrote:
I think thats the problem with it. People do think of it this way, and it
ends up being very confusing.
If you dont use onlyMorePopular, and you ask for suggestions for a word
that happens to be in the index,
On Sun, Feb 15, 2009 at 8:56 AM, Mark Miller wrote:
> I think thats the problem with it. People do think of it this way, and it
> ends up being very confusing.
>
> If you dont use onlyMorePopular, and you ask for suggestions for a word
> that happens to be in the index, you get the word back.
>
>
Shalin Shekhar Mangar wrote:
No. Think of onlyMorePopular as a toggle between whether to consider
frequency or not. When you say onlyMorePopular=true, higher frequency terms
are considered. When you say onlyMorePopular=false, frequency plays no role
at all and "gran" is returned because according
On Fri, Feb 13, 2009 at 8:46 PM, Marcus Stratmann wrote:
>
> Okay, this is a bit weird, but I think I got it now. Let me try to explain
> it using my example. When I search for "gran" (frequency 10) I get the
> suggestion "grand" (frequency 17) when using onlyMorePopular=true. When I
> use onlyMo
Fuzzy search should match "grand turismo" to "gran turismo" without
using spelling suggestions. At Netflix, the first hit for the
query "grand turismo" is the movie "Gran Torino" and we use fuzzy
with Solr.
wunder
On 2/13/09 3:35 AM, "Marcus Stratmann" wrote:
> Shalin Shekhar Mangar wrote:
>>>
Shalin Shekhar Mangar wrote:
If onlyMorePopular=true, then the algorithm finds tokens which have greater
frequency than the searched term. Among these terms, the one which is
closest (by edit distance) is returned.
Okay, this is a bit weird, but I think I got it now. Let me try to
explain it u
On Fri, Feb 13, 2009 at 5:05 PM, Marcus Stratmann wrote:
> Hm, when I try searching for "grand" using onlyMorePopular=false I do not
> get any results. Same when trying "gran". It seems that there will be no
> results at all when using onlyMorePopular=false.
When onlyMorePopular is false and th
Shalin Shekhar Mangar wrote:
And to come back to my last question: There seems to be no case in which
"onlyMorePopular=false" makes sense (provided Grant's assumption is
correct). Do you see one?
Here's a use-case -- you provide a mis-spelled word and you want the closest
suggestion by edit dis
On Fri, Feb 13, 2009 at 2:51 PM, Marcus Stratmann wrote:
> Shalin Shekhar Mangar wrote:
>
>> The end goal is to give spelling suggestions. Even if it gave less
>> frequently occurring spelling suggestions, what would you do with it?
>>
> To give you an example:
> We have an index for computer gam
Shalin Shekhar Mangar wrote:
The end goal is to give spelling suggestions. Even if it gave less
frequently occurring spelling suggestions, what would you do with it?
To give you an example:
We have an index for computer games. One title is "gran turismo". The
word "gran" is less frequent in the
On Fri, Feb 13, 2009 at 2:16 PM, Marcus Stratmann wrote:
> Grant Ingersoll wrote:
>
>> I believe the reason is b/c when onlyMP is false, if the word itself is
>> already in the index, it short circuits out. When onlyMP is true, it checks
>> to see if there are more frequently occurring variation
Grant Ingersoll wrote:
I believe the reason is b/c when onlyMP is false, if the word itself is
already in the index, it short circuits out. When onlyMP is true, it
checks to see if there are more frequently occurring variations.
This would mean that onlyMorePopular=false isn't useful at all. If
I believe the reason is b/c when onlyMP is false, if the word itself
is already in the index, it short circuits out. When onlyMP is true,
it checks to see if there are more frequently occurring variations.
However, I don't have the code in front of me at the moment, so I
can't verify.
-G
I have tried it in all sorts of ways including spellcheck.onlyMorePopular
and spellcheck.onlymorepopular to no avail. It still suggests things that
are way lower than the main query.
On 11/14/08 5:59 PM, "Grant Ingersoll" <[EMAIL PROTECTED]> wrote:
> Try spellcheck.onlyMorePopular.
>
>
> On N
Try spellcheck.onlyMorePopular.
On Nov 14, 2008, at 1:53 PM, Jeff Newburn wrote:
I am trying to get the onlyMorePopular variable to function
correctly. I
have tried adding both spellchecker.onlyMorePopular as well as
sp.query.onlyMorePopular yet neither of these seem to change the
spellin
18 matches
Mail list logo
