Closed asfimport closed 11 years ago
Aleksey Aleev (migrated from JIRA)
Patch with proposed solution attached.
Michael McCandless (@mikemccand) (migrated from JIRA)
Could we just fix it so passing in Integer.MAX_VALUE for maxDocsPerGroup works? I.e., we'd need to do the min(numDocsInGroup, maxDocsPerGroup) when we create the collector for the group. And I think we don't need to create this separate Accumulator class...
Aleksey Aleev (migrated from JIRA)
Michael, thank you for replying! I agree with you about Integer.MAX_VALUE, it looks much better in this way. The reason why I introduced GroupDocsAccumulator class is that I wanted to reduce the size of getTopGroups(...) method and make it more readable. Could you please tell me you don't like introducing new class and creating an instance of it at all or you think that it's not clear what accumulate() method should do? Maybe it will be more clear if the loop by groups will remain in getTopGroups() and the loop's body will be extracted in accumulate() method? So we'll have:
for(int groupIDX=offset;groupIDX<sortedGroups.length;groupIDX++) {
groupDocsAccumulator.accumulate(groupIDX);
}
Please tell WDYT about it and I'll update the patch.
Michael McCandless (@mikemccand) (migrated from JIRA)
Hi Aleksey, reducing that method size would be nice! Can we just make it a new method (accumulate is good), instead of a new class? (And also the Integer.MAX_VALUE fix). I think this will be a good improvement...
Aleksey Aleev (migrated from JIRA)
Hi Michael! I've updated the patch with introducing a method instead of class and Integer.MAX_VALUE fix. Please have a look and tell what do you think about it. Thank you.
Michael McCandless (@mikemccand) (migrated from JIRA)
The Integer.MAX_VALUE change looks great!
But one thing I don't like about the accumulateGroups is there's now a separate (second) loop to sum up the totalGroupedHitCount.
Maybe accumulateGroups should do this itself, and then return TopGroups instead of GroupDocs<Integer>()?
Aleksey Aleev (migrated from JIRA)
The patch is updated. It looks better, thanks.
Michael McCandless (@mikemccand) (migrated from JIRA)
OK, I committed the last patch (plus some small unrelated cleanup to a pre-existing test case); thanks Aleksey!
Uwe Schindler (@uschindler) (migrated from JIRA)
Closed after release.
ToParentBlockJoinCollector#getTopGroups method takes several arguments:
and one of them is
maxDocsPerGroup
which specifies upper bound of child documents number returned within each group.ToParentBlockJoinCollector
collects and caches all child documents matched by givenToParentBlockJoinQuery
inOneGroup
objects during search so it is possible to createGroupDocs
with all matched child documents instead of part of them bounded bymaxDocsPerGroup
.When you specify
maxDocsPerGroup
new queues(I meanTopScoreDocCollector
/TopFieldCollector
) will be created for each group withmaxDocsPerGroup
objects created within each queue which could lead to redundant memory allocation in case of child documents number within group is less thanmaxDocsPerGroup
.I suppose that there are many cases where you need to get all child documents matched by query so it could be nice to have ability to get top groups with all matched child documents without unnecessary memory allocation.
Possible solution is to pass negative
maxDocsPerGroup
in case when you need to get all matched child documents within each group and checkmaxDocsPerGroup
value: if it is negative then we need to create queue with size of matched child documents number; otherwise create queue with size equals tomaxDocsPerGroup
.Migrated from LUCENE-4832 by Aleksey Aleev, 1 vote, resolved Mar 18 2013 Attachments: LUCENE-4832.patch (versions: 3)