Re: searching exact phrase with stop word returns bad results

2013-03-13 Thread Ahmet Arslan
" I would go with custom tokenizer in your case but it could be simulated using MappingCharFilter with WhitespaceTokenizer. "." => " " "@" => " @ " --- On Wed, 3/13/13, adfel70 wrote:

Re: searching exact phrase with stop word returns bad results

2013-03-13 Thread adfel70
ld first describe in simple English what your token/term >> > rules >> > are, and then it would be more clear what tokenizer and filters would >> be >> > most appropriate. >> > >> > -- Jack Krupansky >> > >> >

Re: searching exact phrase with stop word returns bad results

2013-03-13 Thread Upayavira
describe in simple English what your token/term > > rules > > are, and then it would be more clear what tokenizer and filters would be > > most appropriate. > > > > -- Jack Krupansky > > > > -Original Message- > > F

Re: searching exact phrase with stop word returns bad results

2013-03-13 Thread adfel70
sh what your token/term > rules > are, and then it would be more clear what tokenizer and filters would be > most appropriate. > > -- Jack Krupansky > > -----Original Message- > From: adfel70 > Sent: Tuesday, March 12, 2013 3:14 AM > To: > solr-user@.apache

Re: searching exact phrase with stop word returns bad results

2013-03-12 Thread Jack Krupansky
Message- From: adfel70 Sent: Tuesday, March 12, 2013 3:14 AM To: solr-user@lucene.apache.org Subject: Re: searching exact phrase with stop word returns bad results I see that there is not token with @. the question is why. this is my field type: any idea

Re: searching exact phrase with stop word returns bad results

2013-03-12 Thread adfel70
I see that there is not token with @. the question is why. this is my field type: any idea? Erick Erickson wrote > Take a look at admin/analysis for the field in question, feed it values > and > see how they are tokenized. My guess is that th

Re: searching exact phrase with stop word returns bad results

2013-03-07 Thread Erick Erickson
Take a look at admin/analysis for the field in question, feed it values and see how they are tokenized. My guess is that the token in the index is a...@gmail.com (single token), which of course won't match the fragment "@ gmail.com" (assuming gmail.com@ is a typo)... Best Erick On Wed, Mar 6, 20