[jira] [Updated] (LUCENE-2684) it's not possible to access sub-query's freq information if BooleanScorer is use

["David Smiley (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley updated LUCENE-2684:
---------------------------------

    Fix Version/s:     (was: 4.7)
                   4.8

> it's not possible to access sub-query's freq information if BooleanScorer is use
> --------------------------------------------------------------------------------
>
>                 Key: LUCENE-2684
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2684
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>            Reporter: Michael McCandless
>             Fix For: 4.8
>
>
> LUCENE-2590 added an advanced feature, allowing an app to gather all sub-scorers for any Query.
> This is powerful because then, during collection, the app can get some details about how each sub-query "participated" in the overall match for the given document.
> However, I think this is completely broken if the BooleanQuery uses BooleanScorer, because that scorer is not doc-at-once.  Instead, it batch processes chunks of 2048 sequential docIDs per scorer.  This is a big performance gain, but it means that the sub scorers will all be positioned to the end of the 2048 doc chunk while the docs that matched within that chunk are collected.
> I don't think we can easily fix this... likely the "fix" is to make it easy(ier) to force BQ to use BooleanScorer2 (which is doc-at-once)?  It is actually possible to force this, today, by having your collector return false from acceptDocsOutOfOrder...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org