[
https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548337
]
Ryan McKinley commented on SOLR-418:
------------------------------------
To be clear, this respects filter queries. For:
http://localhost:8983/solr/boost?q=ZZZZ&debugQuery=true&fq=id:2
only id:2 is returned even though 1&3 are boosted.
I suppose we could do something to make the intrinsic query include other
fields. Perhaps
{code:xml}
<boost>
<query>
<param name="q">string</param>
<param name="fq">another</param>
</query>
<docs>
<doc id="1" />
<doc id="2" />
<doc id="3" />
</docs>
</boost>
{code}
or
{code:xml}
<query params="q=string&fq=another">
<doc id="1" />
</query>
{code}
*but* I think this gets more complicated then necessary. For the cases I can
think of where you would want different docs boosted, you could just register a
different handler with different boosted docs / invariants. This kind of
functionality only really makes sense with dismax style user queries rather
then standard lucene query syntax. That is "dog" rather then "name:dog^3
content:dog^1"
-----
re terminology. Maybe using the word "boost" will get too confusing. Perhaps
"elevate", "promote", "force top documents"?
rather then the 'QueryBoostingComponent', this could be the
DocumentElevationComponent
{code:xml}
<elevate>
<query phrase="XXXX">
<doc id="1"/>
</query>
<query text="YYYY">
<doc id="1" />
<doc id="2" />
</query>
</elevate>
{code}
The fastsearch glossary has a few terms that may be relevant?
*Absolute boosting*
{panel}
Absolute boosting enables a document to be consistently displayed at a given
position in the result set when a user searches with a specific query. It also
prevents individual documents from being displayed when a user searches with a
specific query.
{panel}
Under boosting, they have:
{panel}
Boosting may be applied in two ways:
* Query independent (document boosting). This is used to boost high quality
pages for all queries that match the document
* Query dependant (query boosting). In this case specific documents may be
boosted for given queries
{panel}
Their "Absolute boosting" description makes me wonder if we should add a flag
to "burry" or "hide" a document for a given query. maybe:
{code:xml}
<doc id="2" hide="true"/>
{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
>
>
> 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.
