lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] Updated: (LUCENE-2590) Enable access to the freq information in a Query's sub-scorers
Date Sun, 22 Aug 2010 18:55:16 GMT


Simon Willnauer updated LUCENE-2590:

    Attachment: LUCENE-2590.patch

Attaching a slightly new version of the patch incorporating roughly the idea of 3-distinct
methods. Yet, having 3 methods instead of one was kind of ugly to implement and I didn't want
to add switch case statements to visitSubScorer methods just to call a different method.
Anyway, I changed the 3  parameter methods to take a single argument holding all required
information. This is way more extensible and flexible since we don't need to change a method
signature just to add a new param. 
I am not sure about the 3 different callbacks but I thought I would leave it in the patch
for now.

Parent, Child and Scorer became generic arguments.


> Enable access to the freq information in a Query's sub-scorers
> --------------------------------------------------------------
>                 Key: LUCENE-2590
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>         Attachments: LUCENE-2590.patch, LUCENE-2590.patch, LUCENE-2590.patch
> The ability to gather more details than just the score, of how a given
> doc matches the current query, has come up a number of times on the
> user's lists.  (most recently in the thread "Query Match Count" by
> Ryan McV on java-user).
> EG if you have a simple TermQuery "foo", on each hit you'd like to
> know how many times "foo" occurred in that doc; or a BooleanQuery +foo
> +bar, being able to separately see the freq of foo and bar for the
> current hit.
> Lucene doesn't make this possible today, which is a shame because
> Lucene in fact does compute exactly this information; it's just not
> accessible from the Collector.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message