Cedric, On Saturday 22 September 2007 11:45, melix wrote: > The problem was even harder when I had to add the match() method to the > BooleanQuery : this class is so complex, and uses so many protected or inner > classes (for optimization purposes, I must understand) that I would have to > copy a lot of the original source code just to add my method. As > documentation on how it works is really hard to find, I decided it would be > simpler if I wrote my own boolean queries (which is what I've done now). I > know it must be much less performant, but makes the tasks much easier.
As long as your scorers are (a combination of) normal target classes of BooleanScorer2 you should get the same efficiency. These target classes are ConjunctionScorer, DisjunctionSumScorer, ReqOptSumScorer and ReqExclScorer. These scorees can be used for "boolean" operators AND, OR, ANDoptional, and ANDNOT. For some cases of top level OR, BooleanScorer can also be a target scorer when scoring out of document order is allowed. Most of the complexity of BooleanScorer2 comes from mapping the + and - query operators for required and prohibited subqueries to these target scorers. Regards, Paul Elschot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
