HI,
"Only return suggestions that result in more hits for the query
than the existing query"
What does it means "the existing query" in above sentence for
"spellcheck.onlymorepopular"?
what happens when I make true to "spellcheck.onlymorepopular"
t; Setting onlyMorePopular=true and using the parameters
>
> spellcheck=true&spellcheck.q=gran&q=gran&spellcheck.onlyMorePopular=true
>
> I get the result
>
>
>
>
> 1
> 0
> 4
> 13
>
> 32
> gr
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
s that there will
> be no results at all when using onlyMorePopular=false. Without
> onlyMorePopular there are suggestions for both terms, so there are
> suggestions close enough to the original word(s). Have you tested your
> example case?
>
> Anyway, if you look at it from the
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
gestions close enough to the original word(s). Have you tested your
> example case?
>
I am confused by this. Did you mean "With onlyMorePopular=true there are
suggestions for both terms"?
> Anyway, if you look at it from the user's point of view: The wiki says
> "s
lar there are suggestions for both terms, so there are
suggestions close enough to the original word(s). Have you tested your
example case?
Anyway, if you look at it from the user's point of view: The wiki says
"spellcheck.onlyMorePopular -- Only return suggestions that result in
more
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
7;t verify.
-Grant
On Feb 12, 2009, at 8:07 AM, Marcus Stratmann wrote:
Hello,
I have another question concerning the spell checking mechanism.
Setting onlyMorePopular=true and using the parameters
spellcheck
=true&spellcheck.q=gran&q=gran&spellcheck.onlyMorePopular=true
I get the r
Hello,
I have another question concerning the spell checking mechanism.
Setting onlyMorePopular=true and using the parameters
spellcheck=true&spellcheck.q=gran&q=gran&spellcheck.onlyMorePopular=true
I get the result
1
0
4
13
32
grand
true
03
n...@skiviez.com
-Original Message-
From: Mark Miller [mailto:markrmil...@gmail.com]
Sent: Thursday, January 29, 2009 2:47 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr 1.3 and spellcheck.onlyMorePopular=true
Let me try that again. I think my email client is going nuts:
I am
7;that would be silly'). So you will likely see bad
suggestions for correct words with this setting.
- Mark
Nicholas Piasecki wrote:
Hello All,
I'm new to Solr, so forgive me if I'm overlooking something obvious. My
observation is that the spellcheck.onlyMorePopular property of
ns for correct words with this setting.
- Mark
Nicholas Piasecki wrote:
Hello All,
I'm new to Solr, so forgive me if I'm overlooking something obvious. My
observation is that the spellcheck.onlyMorePopular property of the
SpellCheckComponent seems to not do what I expect.
If I send
Hello All,
I'm new to Solr, so forgive me if I'm overlooking something obvious. My
observation is that the spellcheck.onlyMorePopular property of the
SpellCheckComponent seems to not do what I expect.
If I send the query "calvin klien" to my data store, then the spell
checke
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.onlyMore
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
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 spelling
suggestion response. I am not sure if I simply do not understand what it is
intended to
25 matches
Mail list logo
