You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Martijn van Groningen (JIRA)" <ji...@apache.org> on 2013/10/01 10:45:29 UTC
[jira] [Updated] (LUCENE-5225) ToParentBlockJoinQuery don't
accumulate the child doc ids and scores if ToParentBlockJoinCollector is
not used
[ https://issues.apache.org/jira/browse/LUCENE-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martijn van Groningen updated LUCENE-5225:
------------------------------------------
Fix Version/s: 4.6
5.0
> ToParentBlockJoinQuery don't accumulate the child doc ids and scores if ToParentBlockJoinCollector is not used
> --------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-5225
> URL: https://issues.apache.org/jira/browse/LUCENE-5225
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Martijn van Groningen
> Assignee: Martijn van Groningen
> Priority: Minor
> Fix For: 5.0, 4.6
>
> Attachments: LUCENE-5225.patch, LUCENE-5225.patch
>
>
> The BlockJoinScorer temporarily saves the child docids and scores in two arrays (pendingChildDocs/pendingChildScores) for the current block (parent/child docs) being processed. This is only need for ToParentBlockJoinCollector and in the case that this collector isn't used then these two arrays shouldn't be used as well.
> I've seen cases where only the ToParentBlockJoinQuery is used and there are many child docs (100k and up), in that case these two arrays are a waste of resources.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org