[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-418:
-------------------------------
Attachment: SOLR-418-QueryBoosting.patch
Updated patch for trunk. This also
1. renames the component 'QueryElevationComponent' and uses the term 'elevate'
rather then 'boost'
2. Implements 'exclude' function
{code:xml}
<query text="ipod">
<doc id="1" />
<doc id="MA147LL/A" exclude="true" />
</query>
{code}
> 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, 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.
