[
https://issues.apache.org/jira/browse/SOLR-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228522#comment-13228522
]
Yonik Seeley commented on SOLR-3145:
------------------------------------
bq. SOLR-1889 was the correct change [...] Changing the queryparser default to
AND is very bad
+1 (but probably for different reasons than you ;-)
But Jan is talking about just changing the default for just an example GUI
(/browse), and not any query parsers. That's pretty minor - not a big deal
either way, but I do think that from a "finished product" perspective, more
people expect all of their query terms to appear in matching documents (and I
believe this is how google does it?)
> 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
>
> Attachments: SOLR-3145.patch
>
>
> 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
