lucene-dev mailing list archives

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


Jan Høydahl commented on SOLR-3145:

Another thing - ALL applications that want to do sorting should care about the precision of
their search. If there are 100 relevant docs for a given query, say {{q=sports car}}, and
your result set returns 1000 docs since you use q.op=OR, then you may very well get the best
sports cars on top, but try sorting by date, price, popularity or anything other than "score"
and your results are crap because you only paid attention to search recall, not to precision.
It's like a scale - gain one and you lose the other.
> Velocity /browse GUI should stick to AND as defaultOperator
> -----------------------------------------------------------
>                 Key: SOLR-3145
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message