...@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,
rather than
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, rather than performing an independent Query on each field?
(assuming he indexes each {table,column} content in a different field)
Thanks,
Sanne
Indeed LUCENE-6229 is very related here ...
Failing Scorer.getChildren, I think you'd have to make your own query
wrappers that wrapped the whole tree (Query, Weight, Scorer) and then
kept track, using those wrappers?
Mike McCandless
http://blog.mikemccandless.com
On Tue, Mar 31, 2015 at 9:25
Mike,
Your suggestion seems related to LUCENE-6229
https://issues.apache.org/jira/browse/LUCENE-6229. My understanding is
that we shouldn't rely on Scorer.getChildren() as you won't always get all
child scorers (just the minimum needed to match) and their positions aren't
necessarily reliable.
I am attempting to loop through the ChildScorer of the scorer.getChildren()
method inside my collect() call, and it is empty.
Is there something else I should do or some setup that I am missing?
Thanks
@Override
public void collect(int docID) throws IOException {
for(ChildScorer
