not really. I usually don't go into the long scoring output for questions
like yours. The parsed_query entries are where a lot of problems
come to light. In this particular case, I'm not quite sure what fields
you're searching against (and dismax can be really confusing). But,
your query didn't spe
hi erick,
thx,..
Any good doc on undestand debug/explain out put u would recommend? I tried
couple of places but doesnt seem to good enf
--
View this message in context:
http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3308362.html
Sent from the Solr - User ma
quot;/>
> words="stopwords.txt"/>
> generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0"
> splitOnCaseChange="1"/>
>
>
>
>
>
>
> wh
ot; and only "iphone"
Synonyms.txt
iphone 4, itouch
thanks
abhay
Date: Wed, 31 Aug 2011 16:57:48 -0700
From: ml-node+3299919-1944219593-210...@n3.nabble.com
To: ajdabhol...@hotmail.com
Subject: RE: word proximity and queryoperator OR
You might want to check your analyzers in s
You might want to check your analyzers in schema.xml. It appears numbers are
filtered out.
So basically you are searching for "iphone" instead of "iphone 4"
--
View this message in context:
http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3299919.html
Sent from
Debug output of a few would help. There can be other factors that produce more
weight than pf/ps. Most of the time it's tf and norms that play a big part.
> hi
>
> I have some issues with search result relevancy.
>
> default query operator is OR
> i search for iphone 4. I m not sure how would i
