That's what I suspected.  Want to paste the relevant tokenizer+filters sections 
of your schema?  The index-time and query-time analysis has to be the same or 
compatible enough, and that's not the case here.

Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch



----- Original Message ----
> From: Kurt Nordstrom <knordst...@library.unt.edu>
> To: solr-user@lucene.apache.org
> Sent: Wednesday, March 25, 2009 1:07:23 PM
> Subject: Re: Strange anomaly(?) with string matching in query
> 
> 
> Otis:
> 
> Okay, I'm not sure whether I should be including the quotes in the query
> when using the analyzer, so I've run it both ways (no quotes on the index
> value).  I'll try to approximate the final "tables" returned for each term:
> 
> The field is dc_subject in both cases, being of type "text"
> 
> ***
> 
> Version 1 (With Quotes)
> Index Value: Abilene Christian College -- Students -- Yearbooks
> Query Value: "Abilene Christian College -- Students -- Yearbooks"
> 
> Index final "table":
> 
> 1             2               3              4               5
> abilene      christian     college       students     yearbooks
> 
> Query final "table":
> 
> 1              2               3              4              6
> abilene      christian     college       students    yearbooks
> 
> 
> Version 2 (Without Quotes)
> Index Value: Abilene Christian College -- Students -- Yearbooks
> Query Value: Abilene Christian College -- Students -- Yearbooks
> 
> 
> Index final "table":
> 
> 1             2               3              4               5
> abilene      christian     college       students     yearbooks
> 
> Query final "table":
> 
> 1             2               3              4               5
> abilene      christian     college       students     yearbooks
> 
> 
> ***
> 
> The main difference seems to be that there is no "5" index when I surround
> the string with quotes, and instead it skips to 6.  This happens at the
> WordDelimiterFilterFactory step. It seems to me like those tokens should be
> returning a match, but either way, apparently they're not?  Any suggestions
> at this point?
> 
> 
> Otis Gospodnetic wrote:
> > 
> > 
> > Hi,
> > 
> > Take the whole string to your Solr Admin -> Analysis page and analyze it. 
> > Does it get analyzed the way you'd expect it to be analyzed?
> > 
> > Otis
> > --
> > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
> > 
> > 
> > 
> -- 
> View this message in context: 
> http://www.nabble.com/Strange-anomaly%28-%29-with-string-matching-in-query-tp22704639p22706495.html
> Sent from the Solr - User mailing list archive at Nabble.com.

Reply via email to