[ 
https://issues.apache.org/jira/browse/LUCENE-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837654#comment-13837654
 ] 

Stefan Pohl commented on LUCENE-4100:
-------------------------------------

Hi Aaron,
I can't say much about any possible complications Solr might add here, but if 
you can get your index building and submitting some test queries code compile 
with the SVN-revision mentioned above (some almost 4.0 revision), and you're 
fine with the current limitations mentioned above (DefaultSimilarity, flat 
queries = BooleanQuery of TermQueries) you can simply try it out. The patch 
should cleanly apply and be functional.
It also shouldn't be too hard to upgrade the code to newer Lucene versions that 
use BlockPostingsFormat (4.1) and the new pull-based codec API (LUCENE-5123).

Either way, it would be very interesting to hear of speedups with respect to 
MLT-like-queries.

> Maxscore - Efficient Scoring
> ----------------------------
>
>                 Key: LUCENE-4100
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4100
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/codecs, core/query/scoring, core/search
>    Affects Versions: 4.0-ALPHA
>            Reporter: Stefan Pohl
>              Labels: api-change, patch, performance
>             Fix For: 4.7
>
>         Attachments: contrib_maxscore.tgz, maxscore.patch
>
>
> At Berlin Buzzwords 2012, I will be presenting 'maxscore', an efficient 
> algorithm first published in the IR domain in 1995 by H. Turtle & J. Flood, 
> that I find deserves more attention among Lucene users (and developers).
> I implemented a proof of concept and did some performance measurements with 
> example queries and lucenebench, the package of Mike McCandless, resulting in 
> very significant speedups.
> This ticket is to get started the discussion on including the implementation 
> into Lucene's codebase. Because the technique requires awareness about it 
> from the Lucene user/developer, it seems best to become a contrib/module 
> package so that it consciously can be chosen to be used.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to