Re: KeywordTokenizer for faceting gives too many results

2010-03-15 Thread Chris Hostetter
: > defaultSearchField stuff is correct but I just realized that you need : to use quotes in your case. Because query parser splits on white-spaces. : &fq=label:"Aces of London" > Or you need to escape spaces: : &fq=label:Aces\ of\ London this is what the "field" QParserPlugin was invented for

Re: KeywordTokenizer for faceting gives too many results

2010-03-12 Thread Michael Kuhlmann
On 03/12/10 17:51, Ahmet Arslan wrote: > >> >> try using Parenthesis with queries that contain more than >> one term. &fq=label:(Aces+of+London) >> Otherwise >> jumps >> in. > > defaultSearchField stuff is correct but I just realized that you need to use > quotes in your case. Because query p

Re: KeywordTokenizer for faceting gives too many results

2010-03-12 Thread Ahmet Arslan
> > try using Parenthesis with queries that contain more than > one term. &fq=label:(Aces+of+London) > Otherwise  > jumps > in. defaultSearchField stuff is correct but I just realized that you need to use quotes in your case. Because query parser splits on white-spaces. &fq=label:"Aces of Lo

Re: KeywordTokenizer for faceting gives too many results

2010-03-12 Thread Ahmet Arslan
> I have some fields that are only used for faceting, so > they're only > queried by facet results. No modification is needed, no > lowercase, > nothing. So the KeywordTokenizerFactory seems to be perfect > for them. You can use plain string type definition (comes in schema.xml) for that purpose.

KeywordTokenizer for faceting gives too many results

2010-03-12 Thread Michael Kuhlmann
Hi, I have some fields that are only used for faceting, so they're only queried by facet results. No modification is needed, no lowercase, nothing. So the KeywordTokenizerFactory seems to be perfect for them. Alas, when the value contains spaces, I'm still getting too many results. I have a field