[
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
Here is an updated patch that allows you to put the configuration in the data
directory and have it reload for each IndexReader.
Assuming the component is initalized with:
<str name="config-file">elevate.xml</str>
If elevate.xml exists within the conf directory it will be loaded once at
startup. If it exists within the 'data' directory, it will be reloaded after
<commit/>
Check http://wiki.apache.org/solr/QueryElevationComponent for tentative docs.
This also refactored the '''getLatestFile'' logic out of
o.a.s.search.function.FileFloatSource and put it in a new class:
o.a.s.util.VersionedFile
> 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
>
>
> 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.
