lucene-dev mailing list archives

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

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

Uwe Schindler commented on SOLR-3145:
-------------------------------------

bq. Rather strong/blanket statement. It seems roughly true that adding non-trivial words to
a google search lowers the number of matches.

This "seems" to be true in lot's of cases. But if you search Google for "google number of
results" you will see pages from all over the internet discussing this topic. Even Google
states in its FAQ that the number of results is just a guess and depends on various factors
that appear quite random, there is no relationship in counts regarding adding/removing terms.
Even the same search returns largely different counts when you change pages (e.g. going from
page 1->2 completely changes the count). The reason for this is of course query preprocessing,
different search clusters and user-specific preferences. To get a more solr-like result, use
"wortwörtlich" (German) / "verbatim" (English) on the left sidebar.

Lot of people simply say: the google count is just arbitrary and useless for any metrics.
                
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message