rinov...@gmail.com]
Sent: Wednesday, April 01, 2015 5:33 PM
To: java-user@lucene.apache.org
Subject: Re: [EXTERNAL] Re: general question
Hello all,
I don't need to do the same, but the suggestions got me curious.
Why would you consider it more efficient to iterate on the child scorers,
r
dren()){
>>> System.out.println("relationship: " + child.relationship);
>>> }
>>>
>>> }
>>>
>>> -Original Message-
>>> From: Michael McCandless [mailto:luc...@mikemccandless.com]
>>> Sent: Monday, M
ct(int docID) throws IOException {
>>
>> for(ChildScorer child : scorer.getChildren()){
>> System.out.println("relationship: " + child.relationship);
>> }
>>
>> }
>>
>> -----Original Message-
>> From: Michael McCandless [mailto:l
" + child.relationship);
> }
>
> }
>
> -Original Message-
> From: Michael McCandless [mailto:luc...@mikemccandless.com]
> Sent: Monday, March 30, 2015 11:20 AM
> To: Lucene Users; tpfi...@sandia.go
> Subject: [EXTERNAL] Re: general question
>
> You could d
child : scorer.getChildren()){
System.out.println("relationship: " + child.relationship);
}
}
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Monday, March 30, 2015 11:20 AM
To: Lucene Users; tpfi...@sandia.go
Subject: [EXTERNAL] R
You could do this with a custom Collector which, for every hit visits
all child scorers asking each one whether it matched the current hit.
Your collector would have to somehow store this information away so
that once the search is done and you pull the top N hits, you know
which fields those hits
