lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-3145) Velocity /browse GUI should stick to AND as defaultOperator
Date Tue, 13 Mar 2012 13:07:37 GMT

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

Jan Høydahl commented on SOLR-3145:
-----------------------------------

Robert, we don't disagree on the fact that search is more difficult than a simple OR or AND.
People need to invest in designing a good search experience, taking these factors as well
as many other into consideration. There is no silver bullet to recall or relevancy, nor is
an advice to use "OR". I have been involved in more than 100 enterprise search installations
world wide and in perhaps 2 or three of them we chose "OR" as default. Most often it's a matter
of "AND" as default plus a lot of careful design in order to increase recall without sacrificing
too much precision. Another key point is that people expect AND-ish behavior from the large
public search engines, and are puzzled if they keep getting more results the more words they
enter in the search box.

Feel free to open new JIRAs for the other shortcomings you mentioned, like better Similarity
defaults - I'm a big fan of that as well!
                
> 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