lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3145) Velocity /browse GUI should stick to AND as defaultOperator
Date Tue, 13 Mar 2012 12:55:38 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228361#comment-13228361
] 

Robert Muir commented on SOLR-3145:
-----------------------------------

{quote}
Robert, I don't get your comment - what does this have to do with stopwords or Similarity?
It sounds more like a general opinion that you like OR better than AND, the more hits the
better...
{quote}

Its not a general opinion. I dont care how many 'totalHits' are returned. I care about the
relevance of the top N.

And when good results are discarded simply because the query contained a useless word like
'his', thats bad news.

People are too quick to jump to AND without debugging the real problem. The problem is that
they see results that don't contain all of their query terms
ranked above results that do: this is a direct result of lucene's sqrt() tf normalization
function (which it tries to make up for with coord): as opposed 
to other alternatives that are less aggressive and are known to perform better.

By forcing everything to AND, it then means the ranking system extremely fragile in cases
like stopwords, but this is applying a hammer,
its not the right default.

                
> Velocity /browse GUI should stick to AND as defaultOperator
> -----------------------------------------------------------
>
>                 Key: SOLR-3145
>                 URL: https://issues.apache.org/jira/browse/SOLR-3145
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 4.0
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>             Fix For: 4.0
>
>
> After SOLR-1889 was committed, the DisMax "mm" parameter defaults to whatever set in
q.op. Since defaultOperator in schema.xml is OR, this means that DisMax now defaults to OR
(mm=0) instead of the old default (mm=100%). It should stick to AND as before.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message