On 11/15/06, Tom <[EMAIL PROTECTED]> wrote:
It looks like that for trimming, the places I want to modify are in ScorePriorityQueue and FieldSortedHitQueue. When trimming, I want to return the top item in the group that matches, whether by score or sort, not just the first one that goes through the HitCollector.
Wouldn't you actually need a priority queue per group?
But, unsurprisingly, trimming vs. not trimming is being ignored with regard to caching. How would I indicate that a query with trim=0 is not the same as trim=1? I do still want to cache.
One hack: implement a simple query that delegates to another query and encapsulates the trim value... that way hashCode/equals won't match unless the trim does. -Yonik
But obviously, my implementation won't work at the moment, since all queries will cache the value generated using the results generated by the value of trim on the initial query. Any suggestions for where to go poking around to fix this vs. caching? Thanks, Tom
