[
https://issues.apache.org/jira/browse/SOLR-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228404#comment-13228404
]
Jan Høydahl commented on SOLR-3145:
-----------------------------------
{quote}
bq. Another thing - ALL applications that want to do sorting should care about
the precision of their search.
Thats not searching, thats matching. I think we should default to good behavior
for search.
{quote}
Come again? Are you saying people don't build *search driven* applications
these days? If so, you're just missing out on a big trend in the market... Our
customers tend to request a seamless mix of advanced full-text search,
navigation and metadata filtering/sorting. Forcing people into either strict
metadata matching OR free-text search is artificial.
Anyway, this is a side track. This issue is about NOT changing the "/browse"
behaviour from 3.x to 4.x
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
