I'm curious... what do you mean by "It's not perfect (there is no such thing) but it works pretty well in most cases, and works great if you spend a little time figuring out the right length normalization factors." ? Can you plz elaborate a little more on what are the length normalization factors exactly and what makes them good or bad... it's a part of lucene that is really confusing me as I'm still a newbie :P
Thanks, Sebastien On Thu, Aug 28, 2008 at 8:56 AM, Grant Ingersoll <[EMAIL PROTECTED]>wrote: > > On Aug 27, 2008, at 7:34 PM, Shi Hui Liu wrote: > > Hi, >> >> I think I should clarify my question a little bit. I'm using BooleanQuery >> to combine TermQuery(A) and TermQuery(B). But I'm not satisfied with its >> scoring algorigthm. Is there other queries can boost up the documents with >> 50 of A and 50 of B on top of documents with 1000 of A and 1 of B? >> > > Is your query A + B meant to be A OR B or A AND B? That is, are both terms > required? You notation suggests they are, but the description suggests you > are getting documents that have only A in them, which suggests "OR". > > Have you looked at the explains? What about the scoring aren't you happy > with? It's not perfect (there is no such thing) but it works pretty well in > most cases, and works great if you spend a little time figuring out the > right length normalization factors. > > > And I'm looking at the source code and found lots of classes are not >> public and some important methods are protected. What's the reason? Why make >> them public and let users to customize the Query easily? >> > > Because there not meant to be overridden, but of course we are open to > specific suggestions on things that should be made public and often do this > when someone shows a valid reason. > > Cheers, > Grant > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
