[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560228#action_12560228
]
Ryan McKinley commented on SOLR-418:
------------------------------------
Thanks for looking at this - and fixing it up
bq. dropped the seemingly unrelated changes in SolrServlet (part of another
patch?)
not sure how that got in there.... it was part of an issue I had with resin
loading servlets before filters and SOLR-350 initialization.
> 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
> Assignee: Ryan McKinley
> Fix For: 1.3
>
> Attachments: SOLR-418-QueryBoosting.patch,
> SOLR-418-QueryBoosting.patch, SOLR-418-QueryBoosting.patch,
> SOLR-418-QueryBoosting.patch, 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.
