I am not sure, BooleanQuery takes something that can score, e.g. being a Clause or a Query, the contract requires some sort of scoring functionality. We use DocIdSetQuery for some of the scoring capabilities such as constant score (with boosting), age decay, and using the new scoring api in 2.3. Maybe I am misunderstanding the point o the question.
Thanks -John On Wed, Jun 25, 2008 at 10:32 AM, Paul Elschot <[EMAIL PROTECTED]> wrote: > Op Wednesday 25 June 2008 18:45:16 schreef John Wang: > > Hi Paul: > > Regarding to your comment on adding required/prohibited to > > BooleanQuery: > > > > Based on the new api on DocIdSet and DocIdSetIterator > > abstractions, we also developed decorators such as > > AndDocIdSet,OrDocIdSet and NotDocIdSet, furthermore a DocIdSetQuery > > class that honors the Query api contracts. Given these tools, we are > > able to build a customized scored BooleanQuery-like query > > infrastructure. We'd be happy to contribute them. > > Another thing to be removed from near the end of my todo list? > Perhaps I could even take a vacation :) > > More seriously: would DocIdSetQuery be superfluous when > a DocIdSet could be added directly to a BooleanQuery? > > Could you elaborate a bit on the customized scoring? > > Regards, > Paul Elschot > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
