hi :)
I've noticed that (with solr 1.2) the returned order (as well as the
actual matched set) is affected by the number of matches you ask for:
q=hannasuggestionCount=1
suggestions:[Yanna]
q=hannasuggestionCount=2
suggestions:[Manna,
Yanna]
q=hannasuggestionCount=5
Hi Geoffrey,
Yes, this is a caveat in the lucene contrib spellchecker which Solr uses.
From the lucene spell checker javadocs:
* pAs the Lucene similarity that is used to fetch the most relevant
n-grammed terms
* is not the same as the edit distance strategy used to calculate the
best
*
Shalin Shekhar Mangar wrote:
Hi Geoffrey,
Yes, this is a caveat in the lucene contrib spellchecker which Solr uses.
From the lucene spell checker javadocs:
* pAs the Lucene similarity that is used to fetch the most relevant
n-grammed terms
* is not the same as the edit distance strategy
I have successfully setup a Solr multicore configuration on Apache Tomcat
5.5 (Solaris 9, JDK 5). I used the 4/21/2008 nightly build for this purpose.
At present, I have two cores defined. I can index and search documents on
both these cores using the java client.
I'm having a minor issue on the
So I just ran into this bug:
https://issues.apache.org/jira/browse/SOLR-470
and read about this related one:
https://issues.apache.org/jira/browse/SOLR-544
Here is the relevant trace:
Apr 22, 2008 10:59:01 PM org.apache.solr.common.SolrException log
SEVERE: java.lang.RuntimeException:
On 22-Apr-08, at 6:00 PM, Christian Wittern wrote:
Mike Klaas wrote:
On 19-Apr-08, at 3:02 AM, Christian Wittern wrote:
So it could be that the match is not part of the fragment? This
sounds a bit strange. Is there a way to make sure the fragment
contains the match other than returning
This is a patch I made to be able to boost the terms with a specific factor
beside the relevancy returned by MoreLikeThis. This is helpful when having
more then 1 MoreLikeThis in the query, so words in the field A (i.e. Title)
can be boosted more than words in the field B (i.e. Description).
Any
Hi Jonathan,
Could you put this in a new JIRA issue? Do you also have a unit test one could
run to see how/that this works?
Thanks,
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Jonathan Ariel [EMAIL PROTECTED]
To:
Otis, Thanks for the reply. Is there a list of words that have special
meaning?
Thanks
Xuesong
Re: Got parseException when search keyword AND on a text field
Otis Gospodnetic
Fri, 18 Apr 2008 18:39:45 -0700
Xuesong,
AND has a special meaning - it is a boolean AND when capitalized. That
Yes. Sure. I'll do that. Just wanted some feedback before posting it. As
soon as I do it I'll post the issue number.
Thanks!
On Wed, Apr 23, 2008 at 6:39 PM, Otis Gospodnetic
[EMAIL PROTECTED] wrote:
Hi Jonathan,
Could you put this in a new JIRA issue? Do you also have a unit test one
could
Not in one place and documented. The place to look are query parsers, but
things like AND OR NOT TO are the ones to look out for.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Xuesong Luo [EMAIL PROTECTED]
To:
Oh come on Otis, give our Solr wiki and Lucene documentation some
kudos here! :) I think this stuff is pretty well documented starting
here:
http://wiki.apache.org/solr/SolrQuerySyntax
Not to mention that dusty ol' book on Lucene...
Erik
On Apr 23, 2008, at 9:28 PM, Otis
12 matches
Mail list logo