[
https://issues.apache.org/jira/browse/LUCENE-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832677#comment-13832677
]
Robert Muir commented on LUCENE-4100:
-------------------------------------
There is at least one step we made for the codec API (LUCENE-5123) that might
make it easier: the codec has the freedom to "pull" the data rather than push
it now, so it can more easily calculate interesting things that it wants.
Still, there remains some fairly major challenges in my eyes:
* how to safely implement the optimization for dynamic indexes: See Stefan's
note above. I do agree there are use cases for static indexes, the problem is:
its lucene, people will try to use it with dynamic indexes regardless.
* how to connect such optimizations in a fairly clean way to the scoring api.
This is perhaps the hardest part. There is a lot of separation between the
scoring API (e.g. pluggable similarity, Scorer, etc) and the codec API.
But i don't want to discourage anyone, just saying its probably even more
difficult from an API perspective than the stuff to support something
"different" like BooleanScorer.java.
> 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]
