[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-418:
------------------------------
Attachment: SOLR-418-QueryBoosting.patch
Looks good Ryan!
I reviewed, and changed a few minor things (new patch attached)
- fixed a concurrency bug (access of map outside of sync can lead to concurrent
modification exception or other errors, even if that key/value pair will never
change)
- changed the example example.xml a little, and switched the /elevate handler
to load lazily
- updated code/configs to reflect SearchHandler move
- fixed (pre-existing) bugs in code moved to VersionedFile (multiple opens of
same file)
- dropped the seemingly unrelated changes in SolrServlet (part of another
patch?)
> 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, 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.
