[jira] Issue Comment Edited: (SOLR-418) Editorial Query Boosting Component

["Ryan McKinley (JIRA)" <ji...@apache.org>]

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

ryantxu edited comment on SOLR-418 at 12/3/07 3:40 PM:
-------------------------------------------------------------

I agree with changing the name from "boosts" to something else...  what is "one box"? (Google points me to their new search appliance ;)

re always putting the 'boosted' docs first...  I'm not *against* making this configurable, but is seems wrong.

If you want to force the sort to have the boosted docs first, isn't that:
{code:xml}
    <lst name="invariants">
      <str name="sort">score desc</str>
   </lst>
{code}

Is there a real use case to have 'sort=date desc' put the boosted docs first?

      was (Author: ryantxu):
    I agree with changing the name from "boosts" to something else...  what is "one box"? (Google points me to their new search appliance ;)

re always putting the 'boosted' docs first...  I'm not *against* making this configurable, but is seems wrong.

If you want to force the sort to have the boosted docs first, isn't that:
{code:xml}
    <lst name="invariants">
      <str name="sort">score</str>
   </lst>
{code}

Is there a real use case to have 'sort=date desc' put the boosted docs first?
  
> Editorial Query Boosting Component
> ----------------------------------
>
>                 Key: SOLR-418
>                 URL: https://issues.apache.org/jira/browse/SOLR-418
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Ryan McKinley
>             Fix For: 1.3
>
>         Attachments: SOLR-418-QueryBoosting.patch, SOLR-418-QueryBoosting.patch
>
>
> For a given query string, a human editor can say what documents should be important.  This is related to a lucene discussion:
> http://www.nabble.com/Forced-Top-Document-tf4682070.html#a13408965
> Ideally, the position could be determined explicitly by the editor - otherwise increasing the boost is probably sufficient.
> This patch uses the Search Component framework to inject custom document boosting into the standard SearchHandler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.