[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554212
]
Koji Sekiguchi commented on SOLR-418:
-------------------------------------
I'm interested in this feature and have few comments:
1. I was bit confused "analyzer" in solrconfig.xml. I thought "fieldType" would
be straightforward to me.
2. Pardon me if I'm wrong, but does elevationCache need to be synchronized in
getElevationMap() as it is called from prepare()?
> 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, 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.
