Solr/Lucene Champion List Support?

[Furkan KAMACI <fu...@gmail.com>]

There is a term called champion list at information retrieval theory. Does
solr/lucene has an implementation of it? Here is some information:
http://en.wikipedia.org/wiki/Champion_list

Re: Solr/Lucene Champion List Support?

[Shawn Heisey <so...@elyograg.org>]

On 6/4/2013 8:07 AM, Furkan KAMACI wrote:
> There is a term called champion list at information retrieval theory. Does
> solr/lucene has an implementation of it? Here is some information:
> http://en.wikipedia.org/wiki/Champion_list

I think this is the closest thing we have to that concept:

http://wiki.apache.org/solr/QueryElevationComponent

There are also a great many ways to do document boosting both at index
time and at query time.

http://wiki.apache.org/solr/SolrRelevancyFAQ

Thanks,
Shawn

Re: Solr/Lucene Champion List Support?

[Jack Krupansky <ja...@basetechnology.com>]

It is merely a performance optimization. Lucene is already blazing fast at 
basic tf-idf query, so that form of "hack" is not needed.

-- Jack Krupansky

-----Original Message----- 
From: Furkan KAMACI
Sent: Tuesday, June 04, 2013 10:07 AM
To: solr-user@lucene.apache.org
Subject: Solr/Lucene Champion List Support?

There is a term called champion list at information retrieval theory. Does
solr/lucene has an implementation of it? Here is some information:
http://en.wikipedia.org/wiki/Champion_list 

Re: Solr/Lucene Champion List Support?

[Chris Hostetter <ho...@fucit.org>]

: There is a term called champion list at information retrieval theory. Does
: solr/lucene has an implementation of it? Here is some information:
: http://en.wikipedia.org/wiki/Champion_list

the most direct equivilent in Solr would be to configure static warming 
using the QuerySendListern in newSearcher and firstSearcher events for a 
query on these specific terms...


    <listener event="firstSearcher" class="solr.QuerySenderListener">
      <arr name="queries">
        <lst>
          <str name="q">static firstSearcher warming in solrconfig.xml</str>
        </lst>
      </arr>
    </listener>

..then it will precommpute the results so they will already be in the 
cache if/when a user requests them.


-Hoss