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 get iphone 4 results to show
first.

I tried
?q=iphone+4&start=0&wt=json&indent=on&fl=displayName,score&qt=dismax&fq=productType:Device&debug=true&pf=displayName&ps=3

proximity  pf and ps but still no use.
{
  "responseHeader":{
    "status":0,
    "QTime":62,
    "params":{
      "fl":"displayName,score",
      "wt":"json",
      "ps":"3",
      "fq":"productType:Device",
      "rows":"10",
      "indent":"on",
      "pf":"displayName",
      "qt":"dismax",
      "debug":"true",
      "start":"0",
      "q":"iphone 4"}},
  "response":{"numFound":25,"start":0,"maxScore":1.1627537,"docs":[
      {
        "displayName":"Apple iPhone 3GS - 32 GB - Black",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 3GS - 8 GB - Black",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 4 - 16 GB - White",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 4 - 16 GB - Black",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 4 - 32 GB - White",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 4 - 32 GB - Black",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 3GS - 8 GB - Black (Refurb)",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 3GS (Refurb Cosmetic Blemish) - 8GB",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 4 - 32 GB - Black (Refurb)",
        "score":1.1627537},
      {
        "displayName":"Apple iPhone 4 (Refurb Cosmetic Blemish) - 16GB -
Black",
        "score":1.1301228}]
  },

I can add debug output if required.

Any help?

--
View this message in context: http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3299729.html
Sent from the Solr - User mailing list archive at Nabble.com.

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 get iphone 4 results to
> show first.
>
> I tried
> ?q=iphone+4&start=0&wt=json&indent=on&fl=displayName,score&qt=dismax&fq=pro
> ductType:Device&debug=true&pf=displayName&ps=3
>
> proximity  pf and ps but still no use.
> {
>   "responseHeader":{
>     "status":0,
>     "QTime":62,
>     "params":{
>       "fl":"displayName,score",
>       "wt":"json",
>       "ps":"3",
>       "fq":"productType:Device",
>       "rows":"10",
>       "indent":"on",
>       "pf":"displayName",
>       "qt":"dismax",
>       "debug":"true",
>       "start":"0",
>       "q":"iphone 4"}},
>   "response":{"numFound":25,"start":0,"maxScore":1.1627537,"docs":[
>       {
>         "displayName":"Apple iPhone 3GS - 32 GB - Black",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 3GS - 8 GB - Black",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 4 - 16 GB - White",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 4 - 16 GB - Black",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 4 - 32 GB - White",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 4 - 32 GB - Black",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 3GS - 8 GB - Black (Refurb)",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 3GS (Refurb Cosmetic Blemish) - 8GB",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 4 - 32 GB - Black (Refurb)",
>         "score":1.1627537},
>       {
>         "displayName":"Apple iPhone 4 (Refurb Cosmetic Blemish) - 16GB -
> Black",
>         "score":1.1301228}]
>   },
>
> I can add debug output if required.
>
> Any help?
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3
> 299729p3299729.html Sent from the Solr - User mailing list archive at
> Nabble.com.

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 the Solr - User mailing list archive at Nabble.com.

hi
i dont understand why though.

here is my displayName filed type "text"
    <fieldType name="text" class="solr.TextField" positionIncrementGap="100">
      <analyzer type="index">
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt" ignoreCase="true" expand="true"/>
        <!-- Case insensitive stop word removal.
             enablePositionIncrements=true ensures that a 'gap' is left to
             allow for accurate phrase queries.
        -->
        <filter class="solr.StopFilterFactory"
                ignoreCase="true"
                words="stopwords.txt"
                enablePositionIncrements="true"
                />
        <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
      </analyzer>
      <analyzer type="query">
        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt" ignoreCase="true" expand="true"/>
        <filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt"/>
        <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
        <filter class="solr.LowerCaseFilterFactory"/>
        <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
      </analyzer>
    </fieldType>
why would search term not be "iphone 4" and only "iphone"

Synonyms.txt
iphone 4, itouch

thanks
abhay
Date: Wed, 31 Aug 2011 16:57:48 -0700
From: ml-node+[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: word proximity and queryoperator OR

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"
 







If you reply to this email, your message will be added to the discussion below:
http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3299919.html



To unsubscribe from word proximity and queryoperator OR, click here.
   

--
View this message in context: http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3300214.html
Sent from the Solr - User mailing list archive at Nabble.com.

I think you're searching for both tokens, but do what Markus said first,
add &debugQuery=on to your query and you'll see exactly what the
search is.

You are searching against your default text field because you have not
specified any field in your query, is that what you expect?

You could add something like OR "iphone 4"^5 which will boost
documents with iphone and 4 right next to each other (experiment
with the boost number). This can be done with (e)dismax easily with
the pf (phrase fields) parameter.

Also, take a look at the admin/analysis page. It'll help you figure
out what each of the various elements of your analysis chain are doing. It's
invaluable...

Best
Erick

On Wed, Aug 31, 2011 at 11:15 PM, abhayd <[EMAIL PROTECTED]> wrote:
>
> hi
> i dont understand why though.
>
> here is my displayName filed type "text"
>
>
>    <fieldType name="text" class="solr.TextField" positionIncrementGap="100">
>      <analyzer type="index">
>        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt" ignoreCase="true" expand="true"/>
>        <!-- Case insensitive stop word removal.
>             enablePositionIncrements=true ensures that a 'gap' is left to
>             allow for accurate phrase queries.
>        -->
>        <filter class="solr.StopFilterFactory"
>                ignoreCase="true"
>                words="stopwords.txt"
>                enablePositionIncrements="true"
>                />
>        <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
>        <filter class="solr.LowerCaseFilterFactory"/>
>        <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
>      </analyzer>
>      <analyzer type="query">
>        <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>        <filter class="solr.SynonymFilterFactory" synonyms="synonyms.txt" ignoreCase="true" expand="true"/>
>        <filter class="solr.StopFilterFactory" ignoreCase="true" words="stopwords.txt"/>
>        <filter class="solr.WordDelimiterFilterFactory" generateWordParts="1" generateNumberParts="1" catenateWords="1" catenateNumbers="1" catenateAll="0" splitOnCaseChange="1"/>
>        <filter class="solr.LowerCaseFilterFactory"/>
>        <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
>      </analyzer>
>    </fieldType>
>
>
> why would search term not be "iphone 4" and only "iphone"
>
> Synonyms.txt
> iphone 4, itouch
>
> thanks
> abhay
> Date: Wed, 31 Aug 2011 16:57:48 -0700
> From: ml-node+[EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: RE: word proximity and queryoperator OR
>
>
>
>        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"
>
>
>
>
>
>
>
>
>
>
>                If you reply to this email, your message will be added to the discussion below:
>                http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3299919.html
>
>
>
>                To unsubscribe from word proximity and queryoperator OR, click here.
>
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/word-proximity-and-queryoperator-OR-tp3299729p3300214.html
> Sent from the Solr - User mailing list archive at Nabble.com.

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 mailing list archive at Nabble.com.

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 specify any fields (no qf parameter). So looking
at the parsed query information should give you some insight...

Best
Erick

On Sun, Sep 4, 2011 at 8:41 AM, abhayd <[EMAIL PROTECTED]> wrote:
> 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 mailing list archive at Nabble.com.
>