lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jason rutherglen <jasonhus...@yahoo.com>
Subject Re: Possible bug in copyField
Date Mon, 28 Aug 2006 17:41:24 GMT
Ok... Looks like its related to using SpanQueries (I hacked on the XML query code).  I remember
a discussion about this issue.  Not something Solr specifically supports so my apologies.
 However if anyone knows about this feel free to post something to the Lucene User list. 
I will probably manually analyze the terms of the span query and create a stemmed span query.
 Is that a good idea?

----- Original Message ----
From: Yonik Seeley <yonik@apache.org>
To: solr-user@lucene.apache.org
Cc: jason rutherglen <jasonhusong@yahoo.com>
Sent: Monday, August 28, 2006 7:33:48 AM
Subject: Re: Possible bug in copyField

On 8/28/06, Chris Hostetter <hossman_lucene@fucit.org> wrote:
>
> : By looking at what is stored.  Has this worked for others?
>
> the "stored" value of a field is allways going to be the pre-analyzed text
> -- that's why the stored values in your "text" fields still have upper
> case characters and stop words.

And since the stored values will always be the same, it normally
doesn't make sense to store the targets of copyField if the sources
are also stored.

Youy can test if stemming was done by searching for a different tense
of a word in the field.

-Yonik





Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message